Overview
A Work Package is a set of instructions issued to a Team Manager to complete an area of work for the project. Work Packages are created during CS1 Authorising a Work Package by the Project Manager with input from the Team Manager and team members. Once created the Work Package is accepted and agreed in MP1 Accepting a Work Package where dates and other details are negotiated.
Work Packages are created and used in the process PL Planning and are part of Product Based Planning. Product Descriptions are an integral part of a Work Package. The Work Package can be as formal or informal, as required depending on the work required. In cases where a 3rd party is involved the Work Package should always be documented and formally agreed. A Work Package may be used as an assessment tool for appraisal and for this reason could form the basis of a Job Description(s) or contract and must have clear quality and sign-off controls.
The Work Package should include the following:
- Dates
- Team/person responsible
- Product Description(s)
- Interfaces
- Quality expectations
- Sign off requirements.
A Work Package should not cover more than one stage, if it does it should be broken down and made into more than one Work Package. It allows the Project Manager to exert control over product delivery (MP Managing Product Delivery) and underpins the PRINCE2 philosophy that "work cannot be undertaken without the Project Manager authorisation".
Tips
- Ensure the Work Package is clearly defined and understood by those carrying out the work.
- Make sure that any standards are agreed.
Notes
- Information about one or more required products collated by the Project Manager
- Formally passes responsibility for work or delivery to a Team Manager or team member
- Varies in content and formality
- A means for formal performance assessment
- If the Work Package is for a 3rd party a written and signed agreement is a good idea
- Should cover:
- Issued from the process CS1 Authorising a Work Package.
Case studies and examples
Related links
| 
