PRINCE2 Agile 2016
Previous Section   Next Section

A.26 Work package

A.26.1 Purpose

A work package is a set of information about one or more required products collated by the project manager to pass responsibility for work or delivery formally to a team manager or team member.

A.26.2 Composition

Although the content may vary greatly according to the relationship between the project manager and the recipient of the work package, it should cover:

  • Date The date of the agreement between the project manager and the team manager/person authorized
  • Team manager or person authorized The name of the team manager or individual with whom the agreement has been made
  • Work package description A description of the work to be done
  • Techniques, processes and procedures Any techniques, tools, standards, processes or procedures to be used in the creation of the specialist products
  • Development interfaces Interfaces that must be maintained while developing the products. These may be people providing information or those who need to receive information
  • Operations and maintenance interfaces Identification of any specialist products with which the product(s) in the work package will have to interface during their operational life. These may be other products to be produced by the project, existing products, or those to be produced by other projects (for example, if the project is part of a programme)
  • Configuration management requirements A statement of any arrangements that must be made by the producer for: version control of the products in the work package; obtaining copies of other products or their product descriptions; submission of the product to configuration management; any storage or security requirements; and who, if anyone, needs to be advised of changes in the status of the work package
  • Joint agreements Details of the agreements on effort, cost, start and end dates, and key milestones for the work package
  • Tolerances Details of the tolerances for the work package (the tolerances will be for time and cost but may also include scope and risk)
  • Constraints Any constraints (apart from the tolerances) on the work, people to be involved, timings, charges, rules to be followed (for example, security and safety) etc.
  • Reporting arrangements The expected frequency and content of checkpoint reports
  • Problem handling and escalation This refers to the procedure for raising issues and risks
  • Extracts or references Any extracts or references to related documents, specifically:
    • Stage plan extract This will be the relevant section of the stage plan for the current management stage or will be a pointer to it
    • Product description(s) This would normally be an attachment of the product description(s) for the products identified in the work package (note that the product description contains the quality methods to be used)
  • Approval method The person, role or group who will approve the completed products within the work package, and how the project manager is to be advised of completion of the products and work package.

There should be space on the work package to record both its initial authorization and its acceptance and return as a completed work package. This can be enhanced to include an assessment of the work and go towards performance appraisal.

Projects with common controls across all work packages may simply cross-reference the controls defined in the project plan or stage plan.

Previous Section   Next Section