Study guide

12.2 Managing Product Delivery

PRINCE2 Practitioner Version 7

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Exam Strategy & Open-Book Technique

2 PRINCE2 7 Method Overview

2.1 The PRINCE2 7 Method 2.2 What Changed in PRINCE2 7 2.3 Performance Targets, Tolerances & Project Context

3 PRINCE2 Principles (1–4)

3.1 Continued Business Justification 3.2 Learn from Experience 3.3 Defined Roles, Responsibilities & Relationships 3.4 Manage by Stages

4 PRINCE2 Principles (5–7) & Applying Principles

4.1 Manage by Exception 4.2 Focus on Products 4.3 Tailor to Suit the Project 4.4 Applying Principles in Context

5 People Management in Projects

5.1 Organisational & Project Ecosystems 5.2 Leadership in Projects 5.3 Team Culture & Diversity 5.4 Communication, Stakeholder Engagement & Change Management

6 Practices Overview & Business Case

6.1 The Seven Practices & Tailoring 6.2 Business Case: Desirability, Viability & Achievability 6.3 Business Case Lifecycle & Management Products 6.4 Business Case Application & Tailoring Scenarios

7 Practices: Organising & Plans

7.1 Organising: Roles & Accountability 7.2 Organising: 5-Step Ecosystem Technique 7.3 Plans: Three Levels & Product-Based Planning 7.4 Plans: Techniques, Tolerances & Tailoring

8 Practices: Quality & Risk

8.1 Quality: Planning, Control & Assurance 8.2 Quality Techniques & Management Products 8.3 Risk: Threats & Opportunities 8.4 Risk 5-Step Technique & Application

9 Practices: Issues

9.1 Issues Practice: Issue vs Change & Categories 9.2 Issues 5-Step Technique & Supporting Techniques 9.3 Change Control, Configuration & Priority/Effort Assessment

10 Practices: Progress, Sustainability & Application

10.1 Progress: Controls, Tolerances & Reports 10.2 Sustainability as the 7th Performance Target 10.3 Tailoring the Practices 10.4 Practices Application Scenarios (BL4)

11 Processes: Model, Starting, Directing & Initiating

11.1 The Seven Processes & Process Model 11.2 Starting Up a Project 11.3 Directing a Project 11.4 Initiating a Project

12 Processes: Controlling a Stage & Product Delivery

12.1 Controlling a Stage 12.2 Managing Product Delivery 12.3 Stage Control & Exception Scenarios (BL4) 12.4 Work Packages & Reporting Cycle

13 Processes: Stage Boundary, Closing & Tailoring

13.1 Managing a Stage Boundary 13.2 Closing a Project 13.3 Tailoring the Processes 13.4 Process Application Scenarios (BL4)

14 Tailoring, Management Products & Exam Technique

14.1 Tailoring to Project Environment, Scale & Agile 14.2 Management Products & the v7 Project Log 14.3 Final Exam Technique, Full Scenarios & Common Traps

12.2 Managing Product Delivery

Key Takeaways Explain This Topic AI

Managing Product Delivery (MP) is performed by the Team Manager and controls the link between the Project Manager and the teams producing specialist products.

The Work Package is the formal agreement between PM and Team Manager; it carries Product Descriptions, tolerances, quality methods, reporting frequency, and constraints.

MP has four activities in v7: accept a Work Package, execute a Work Package, evaluate a Work Package, and notify Work Package completion (v6 combined the last two as "deliver a Work Package").

The Team Manager reports progress to the PM through Checkpoint Reports at the frequency set in the Work Package.

Last updated: August 2026

Managing Product Delivery (MP) is the process performed by the Team Manager . It sits between the Project Manager's Controlling a Stage and the specialist teams who actually build the products, and it is the only PRINCE2 process whose owner is not the PM or the Project Board. This separation is deliberate: it preserves the PM's focus on the stage as a whole and gives the Team Manager clear authority over how specialist work is done.

Purpose

The purpose of MP is to ensure that products are created and delivered to the right quality, on time, and within the tolerances defined in the Work Package. It controls the link between the PM and the teams, ensures that quality is built in rather than inspected in at the end, and provides the reporting line that lets the PM monitor progress without micromanaging the team.

A useful way to remember MP's role is to contrast it with CS. Controlling a Stage is about the stage — tolerances, status, exceptions, board reporting. Managing Product Delivery is about the products — building them, quality-checking them, and handing them back. The two processes run in parallel and are joined by the Work Package and the Checkpoint Report.

The four activities of Managing Product Delivery

PRINCE2 7 structures MP into four activities that follow the natural life of a Work Package. Note the change from PRINCE2 6, which had three: v6's deliver a Work Package was split into evaluate a Work Package and notify Work Package completion .

Activity Team Manager action Output

Accept a Work Package Confirm that the Work Package is understood and achievable; negotiate any constraints with the PM; agree the reporting frequency and quality methods Accepted Work Package, team plan

Execute a Work Package Plan the work in detail, develop the products, perform quality checks against the Product Descriptions, monitor progress against team-level tolerances Specialist products, Quality Register entries, Checkpoint Reports

Evaluate a Work Package Review the work against the Work Package description and the Project Log records (issues, risks, quality, products, lessons); report progress to the PM Checkpoint Report, updated Project Log records

Notify Work Package completion Confirm product approvals, update the team plan, and brief the PM on status, performance, and any outstanding issues or risks Completion notification to the PM, updated quality and product registers

The first activity, accept a Work Package , is more than a formality. The Team Manager should check that the Product Descriptions are clear, that the quality methods are workable, that the tolerances are realistic given the team's capacity, and that the reporting frequency is achievable. If anything is unworkable, the Team Manager negotiates with the PM before accepting — once accepted, the Work Package is the agreement that binds both sides.

Execute a Work Package is where the specialist work happens. The Team Manager plans the work (often producing a team plan that sits beneath the Stage Plan), develops the products, and — critically — performs the quality checks defined in each Product Description. Quality in PRINCE2 is built in through quality methods specified up front (inspections, tests, reviews) rather than added at the end. The Team Manager also produces Checkpoint Reports to the PM at the frequency set in the Work Package.

Evaluate a Work Package and notify Work Package completion together form the hand-back (v6 called this single activity deliver a Work Package ). The Team Manager obtains formal acceptance of the products against the Product Descriptions — this is the moment the products become the PM's responsibility again. The completed Work Package is returned to the PM, who receives it under Controlling a Stage and integrates the products into the stage.

What a Work Package contains

The Work Package is the central management product in MP. It is the agreement between the PM and the Team Manager that defines what will be produced and under what conditions. A Work Package typically contains:

  • Work Package contents Description
  • Product Description(s) Define each product's purpose, composition, quality criteria, and quality methods

Date, effort, and cost tolerances The limits within which the Team Manager may operate without referring back to the PM

  • Quality methods The inspections, tests, or reviews that will be applied, and who is responsible
  • Reporting frequency How often the Team Manager will produce Checkpoint Reports to the PM
  • Constraints Any fixed dates, dependencies, tools, standards, or interfaces that must be observed
  • Configuration management requirements How the products will be identified, version-controlled, and handed over
  • Approval method How acceptance will be obtained and by whom

The tolerances in the Work Package are a delegation of the stage tolerance. The Project Board sets the stage tolerance; the PM carves a slice of it out for each Work Package. If a Team Manager forecasts that a Work Package tolerance will be breached, the Team Manager raises it as an Issue to the PM (typically an off-specification or a concern), and the PM then decides whether to handle it within the stage or escalate. The Team Manager does not raise an Exception Report directly to the Project Board — that is the PM's act.

Reporting: the Checkpoint Report

The Checkpoint Report is the Team Manager's time-driven report to the PM, produced at the frequency set in the Work Package (for example, weekly or at the end of each sprint). It summarises work completed, work planned for the next period, issues and risks affecting the Work Package, and the tolerance position. The PM consumes Checkpoint Reports during the assess progress activity of Controlling a Stage and uses them to update the Stage Plan and the Highlight Report.

A common exam trap is to confuse the Checkpoint Report with the Highlight Report. Remember the direction and the sender: Checkpoint Report = Team Manager → PM ; Highlight Report = PM → Project Board . Both are time-driven. Both are about status. But they sit at different levels of the management hierarchy, and only the PM owns the board-facing report.

Work Package acceptance

Acceptance is the moment a product is signed off against its Product Description. The Work Package defines who accepts — it might be the PM, a user representative, or a named quality reviewer. Until acceptance, the product remains the Team Manager's responsibility. After acceptance, the PM owns it and integrates it into the stage. If a product fails its quality criteria, the Team Manager reworks it under execute a Work Package ; the PM does not step in to do the rework, because the PM is not the specialist. This boundary is one of the reasons PRINCE2 separates MP from CS so firmly.