In the context of PRINCE2 7 and the Plans practice, the Work Package Description serves as the fundamental vehicle for delegating work from the Project Manager to the Team Manager. It acts as a formal agreement between the managing layer (Managing a Stage process) and the delivery layer (Managing P…In the context of PRINCE2 7 and the Plans practice, the Work Package Description serves as the fundamental vehicle for delegating work from the Project Manager to the Team Manager. It acts as a formal agreement between the managing layer (Managing a Stage process) and the delivery layer (Managing Product Delivery process), ensuring that no work commences without specific authorization.
Its primary purpose is to define exactly what needs to be delivered, the constraints involved, and the reporting requirements. It contains or references one or more Product Descriptions, detailing the quality criteria and standards required. The Work Package allows the Project Manager to maintain control without micromanaging, as it establishes the boundaries—specifically tolerances for time, cost, and scope—within which the Team Manager can operate autonomously.
Key components of a Work Package include:
1. Joint Agreements: Estimates for effort, cost, and dates agreed upon by both the Project Manager and Team Manager.
2. Techniques and Standards: Specific development methods or quality standards that must be applied.
3. Interfaces: Details on human or technical interfaces (e.g., who must be consulted during development).
4. Reporting Arrangements: The frequency and format of Checkpoint Reports.
5. Problem Handling: Procedures for escalating issues if tolerances are forecast to be breached.
From a planning perspective, the Work Package is the trigger for the Team Manager to create a Team Plan (optional in PRINCE2 but recommended). It represents the lowest level of work definition in the project's planning hierarchy. By defining the work clearly in this document, the project ensures that the products delivered align with the Stage Plan and Project Plan, while clearly delineating accountability for delivery.
PRINCE2 Practitioner v7: Master Guide to the Work Package Description
What is a Work Package Description? In PRINCE2, the Work Package is the primary mechanism used by the Project Manager to assign work to a Team Manager or a team member. It represents a formal agreement and authorization to deliver one or more products within specific constraints. While the Product Description defines what the product is and its quality criteria, the Work Package Description wraps that product (or set of products) in management instructions, detailing how the work should be executed, reported, and delivered.
Why is it Important? Without a formal Work Package, there is a high risk of scope creep, misunderstanding of deadlines, and lack of clarity regarding reporting lines. It is crucial because: 1. It acts as a contract between the Project Manager and the Team Manager. 2. It ensures the team understands the constraints (Time, Cost, Quality, Scope, Benefit, Risk) relevant to their specific task. 3. It defines exactly how the Team Manager should report progress to the Project Manager (e.g., via Checkpoint Reports).
How it Works The Work Package follows a specific lifecycle between the Controlling a Stage and Managing Product Delivery processes: 1. Creation: The Project Manager assembles the Work Package, including relevant Product Descriptions. 2. Agreement: The Project Manager and Team Manager discuss and agree on the Work Package. It is not simply dictated; it must be realistic and achievable by the team. 3. Authorization: The Team Manager accepts the Work Package, triggering the start of the work. 4. Execution & Reporting: The team builds the products, and the Team Manager sends Checkpoint Reports as defined in the Work Package. 5. Handover: Once completed and quality-checked, the Work Package is returned to the Project Manager.
How to Answer Questions on Work Package Description In the Practitioner exam, questions often focus on the Plans practice or the Controlling a Stage process. You may be asked to assess whether a Work Package is being used correctly or if specific information included in it is appropriate.
Exam Tips: Answering Questions on Work Package Description 1. Differentiate from Product Description: If the question asks about the quality criteria, tolerances for the product attributes, or what is being built, it refers to the Product Description. If the question asks about reporting requirements, problem handling, interfaces, or authorization, it refers to the Work Package.
2. Look for the 'Contract': Remember that a Work Package is a bilateral agreement. If a scenario describes a Project Manager imposing a deadline without consulting the Team Manager, the Work Package practice is being violated.
3. Hierarchy of Plans: The Work Package is the lowest level of detail in the planning hierarchy (Project Plan -> Stage Plan -> Team Plan). However, the Work Package itself is not a plan; it is an instruction that results in the Team Manager creating a Team Plan.
4. Tolerances: Team Managers only have tolerances if they are defined in the Work Package. If an exam scenario asks about a Team Manager exceeding a limit, check if that limit was explicitly stated in the Work Package Description.