Initial Thoughts on Work Packages and Documents
OK! At risk of stopping you reading immediately…If i’m honest when working with smaller organisations or less established organisations where there is a looser structure (and often overlaps in responsibility, capability, and capacity), it is very rare that I create a full document like the template we’v provided for work package. HOWEVER! it is within other places and that is what I will explain here. Once you’re more familiar you you will understand this more and develop your own approaches depending on the organisations you work with and your personal skill sets too.
An example of this would be when there documents tend to transform into instruction emails that can be cascaded through other managers delivering their service level agreement (and even when this agreement is verbal). Although, in other institutions, or if you are working on IT projects or more complex delivery with multiple work products, these documents are absolutely vital to ensuring the consistency of work products, expectations, and mitigating risk from any handovers or staff turnover. Someone can pick this up again and then get back on track. Very similar to the way we suggest students to always look back at the brief to make sure thy have not gone on a tangent and produced something that is way more radical, creative and fun…
Product Description
The product description is a key document in itself. It is a kind of mission statement and vision for what the product is going to be (you will notice that we say products a lot, and that is also because of the PRINCE2 training methodology which leans heavily on this, and very successfully).
EXPAND
Manger and Delivery Team
This is the name of the line manager of the team that will be delivering, as well as the person writing the brief so that both are aware of the reporting and request mechanism.
You might also include contact information like email addresses, contact numbers, or refer to another stakeholder document.
Procedures, Materials, Techniques
This section outlines any specific procedures, materials, techniques, or processes that should be adopted to deliver the work package.
Constraints and Limitations
This outlines and acknowledges the constraints and limitations of the delivery. This is closely related to the project scope and tolerances, but is specific to the work package and work products that come from this.
Processes to request changes
This is the process to request changes, if there are any levels of governance that the team need to know
Monitoring and Controlling Stages
This
Levels of Approval and Signatures
This section is for the acknowledgement of the people responsible for the work product.
No responses yet