In PRINCE2 – how and why do we authorize a work package?
Work Packages are a way for the Project Manager to group work activities together and assign work to a team or Team Manager to produce one or more products.
Authorize a Work Package
It is essential that a specialist team does not carry out work unless it has been authorised by the project manager, and PRINCE2 uses the work package as the authority for that function to be executed.
A brand new work package will incorporate as a minimum one product description but usually, it is going to include quite a few.

The project manager might give out work packages one at a time or many all at once, based on the information laid down within the approved stage plan.
The stage plan for the existing stage needs to be checked to know what products are to be created, the cost and effort for the work, along with any tolerances which are included.
The project initiation documentation should also be checked to ensure that the project controls are suitable to a given work package (for instance checkpoint report arrangements), and how the products are to be handled or escalated. The configuration management strategy should be checked for how this needs to occur.
Work Package contents
The work package really should be checked prior to giving out to make sure it is actually complete and accurate.
Every single work package must incorporate the product descriptions for each product to be developed, any unique approaches, processes or procedures to be utilised, and any arrangements that must be made for configuration management.
The work package must also detail any constraints which include how challenges are component handled and escalated. It consists of individuals from developments and operational management that require to be involved using the work package, and certainly, a clear description of the function to be completed such as any constraints.
The work package is in impact a contract of understanding among the project manager plus a specialist team.
The work package must then be reviewed with the team manager and to make sure that they have accepted it. Configuration Item Records need to be updated to reflect that the work package products are now ‘work in progress’, and the quality register updated with the planned quality management activities.
Project assurance really should be consulted to make sure that the quality review approach is acceptable. The risk and issue registers need to be inspected and updated if needed to reflect the current risk and issue status.
