A Work Package Description is a crucial document within the PRINCE2 7 Plans practice that provides detailed information about specific work that needs to be completed during a project. It serves as the primary means of communication between the Project Manager and Team Manager, establishing clear e…A Work Package Description is a crucial document within the PRINCE2 7 Plans practice that provides detailed information about specific work that needs to be completed during a project. It serves as the primary means of communication between the Project Manager and Team Manager, establishing clear expectations for deliverable production.
The Work Package Description contains several essential elements that define what work must be accomplished. It includes a description of the work required, specifying the products to be delivered along with their quality requirements and tolerances. The document outlines the techniques, processes, and procedures to be used during execution.
Key components of a Work Package Description include the work package identifier, date of agreement, team manager details, and product descriptions for all products to be created. It also specifies constraints such as time limits, cost boundaries, and any dependencies on other work packages or external factors.
The description establishes reporting arrangements, indicating how progress will be communicated back to the Project Manager, including checkpoint report frequency and any specific issues that require escalation. It defines approval methods for completed products and identifies any handover requirements.
Work Package Descriptions support the manage by stages principle by breaking down stage work into manageable portions that can be assigned, monitored, and controlled effectively. They enable proper delegation while maintaining accountability and providing clear boundaries for team activities.
The document also addresses risk management considerations relevant to the work being undertaken, ensuring team members understand potential challenges and how to respond appropriately.
By clearly defining expectations, constraints, and reporting requirements, the Work Package Description ensures alignment between project management and delivery teams, reduces misunderstandings, and provides a basis for monitoring progress and quality throughout the work execution period.
Work Package Description - Complete Guide
What is a Work Package Description?
A Work Package Description is a formal document used in PRINCE2 to define and communicate what work needs to be delivered by a Team Manager or team member. It represents the interface between the Project Manager and the Team Manager, providing all the information needed to create, review, and approve the required products.
Why is the Work Package Description Important?
The Work Package Description is crucial because it:
• Clarifies expectations - Ensures everyone understands what needs to be delivered, when, and to what standard • Enables delegation - Allows the Project Manager to assign work with confidence that requirements are clearly communicated • Supports control - Provides a baseline against which progress and quality can be measured • Facilitates accountability - Creates a clear agreement between the Project Manager and Team Manager • Ensures quality - Specifies the quality requirements and methods for checking deliverables
How Does It Work?
The Work Package Description is created during the Managing a Stage Boundary or Controlling a Stage process. The Project Manager prepares it and authorizes work by passing it to the Team Manager through the Authorize Work Package activity.
The Team Manager uses the Work Package Description to plan their work, execute it during the Managing Product Delivery process, and report back on progress using Checkpoint Reports.
Key Contents of a Work Package Description:
• Work Package Description identifier - Unique reference • Date, time, and effort constraints - Deadlines and resource limits • Product Description(s) - What needs to be created • Techniques, processes, and procedures - How work should be done • Interfaces - Dependencies with other teams or work packages • Joint agreements - Tolerance levels, reporting arrangements • Approval method - How completed products will be approved
Exam Tips: Answering Questions on Work Package Description
1. Remember the relationship - The Work Package Description flows from Project Manager to Team Manager, and is part of the Plans practice
2. Focus on the purpose - It defines what work is required and the agreement between Project Manager and Team Manager
3. Know the process context - Work Packages are authorized in Controlling a Stage and executed in Managing Product Delivery
4. Understand tolerances - Work Package tolerances allow the Team Manager to manage day-to-day work within agreed limits
5. Link to Checkpoint Reports - The Team Manager reports progress against the Work Package through Checkpoint Reports
6. Remember it is product-based - The Work Package always references Product Descriptions
7. Watch for common traps - The Work Package is NOT created by the Team Manager; it is created by the Project Manager
8. Consider external suppliers - When work is contracted out, the Work Package may form part of the formal contract