7.2 Managing Product Delivery (MP) Process

7.2 Managing Product Delivery (MP) Process

Exam Focus: Managing Product Delivery (MP) is the only PRINCE2 process that takes place at the Delivery Level of the project management structure. It bridges the gap between project management governance and technical execution. Candidates must master the three core activities of MP, understand the Team Manager's responsibilities, and recognize how Work Packages ensure controlled, quality-focused product creation.

---

Purpose and Context of Managing Product Delivery

The purpose of Managing Product Delivery (MP) is to control the link between the Project Manager and the Team Manager(s) by placing formal requirements on accepting, executing, and delivering project work.

While the Project Manager manages stage progress using Controlling a Stage (CS), the Team Manager executes MP to ensure that specialist products are created to the required quality, within agreed timeframes and costs, as defined in the authorized Work Package.

+-----------------------------------------------------------------------------+
|                   CONTROLLING A STAGE (Project Manager)                     |
|             Authorizes WP  |  Monitors Status  | Accepts Product            |
+-----------------------------------------------------------------------------+
                                 |           ^
             Work Package Details|           | Checkpoint Reports &
             & Tolerances        v           | Completed Products
+-----------------------------------------------------------------------------+
|               MANAGING PRODUCT DELIVERY (Team Manager / Team)               |
|                                                                             |
|   +-------------------+   +-------------------+   +-------------------+     |
|   |  ACCEPT WORK PKG  |-->|  EXECUTE WORK PKG |-->|  DELIVER WORK PKG |     |
|   +-------------------+   +-------------------+   +-------------------+     |
|   • Agree Team Plan       • Create Products       • Quality Sign-off        |
|   • Confirm Tolerances    • Quality Checks        • Handover to PM          |
|   • Set Checkpoint Sched  • Checkpoint Rep.       • WP Completion Notice    |
+-----------------------------------------------------------------------------+

---

Key Objectives of the MP Process

The MP process ensures that:

1. Work is Agreed Before Execution: Work on products is allocated and accepted only after clear agreement on scope, constraints, and quality standards.
2. Clear Boundaries for Delivery: The Team Manager understands exactly what products must be produced, their quality criteria, assigned resources, and Work Package tolerances.
3. Quality Verification: Planned products are developed, inspected, and approved in accordance with Product Descriptions and Quality Management Approaches.
4. Progress Visibility: The Project Manager receives regular, accurate progress reports (Checkpoint Reports) at agreed intervals.
5. Formal Handover: Completed products obtain formal sign-off before being passed back to the Project Manager.

---

The Three Core Activities of Managing Product Delivery

MP is structured around three sequential activities performed by the Team Manager:

+-----------------------+     +-----------------------+     +-----------------------+
| ACCEPT A WORK PACKAGE | --> | EXECUTE A WORK PACKAGE| --> | DELIVER A WORK PACKAGE|
+-----------------------+     +-----------------------+     +-----------------------+

1. Accept a Work Package

Before starting technical work, the Team Manager must review the Work Package received from the Project Manager and agree to its terms:

• Review Requirements: Inspect Product Descriptions, quality criteria, acceptance methods, development interfaces, and constraints.
• Develop Team Plan: Create an internal Team Plan (or adopt agile sprint/iteration plans) demonstrating how the work will be completed within requested parameters.
• Negotiate & Confirm: Confirm with the Project Manager that the schedule, resources, reporting frequency, and Work Package tolerances are realistic and achievable.
• Formal Agreement: Formally accept the Work Package to authorize the delivery team to commence work.

2. Execute a Work Package

The delivery team actively creates the specialist products while maintaining strict quality and progress controls:

• Product Development: Build the specialist products according to technical specifications and engineering standards.
• Quality Inspections: Execute quality checks (e.g., peer reviews, automated testing, audits) as specified in Product Descriptions and log results in the Quality Register.
• Progress Reporting: Compile and submit periodic Checkpoint Reports to the Project Manager at the frequency agreed in the Work Package.
• Issue & Risk Monitoring: Identify delivery-level risks or issues. If a Work Package tolerance is forecast to be breached, notify the Project Manager immediately.

3. Deliver a Work Package

When all products in the Work Package are completed, the Team Manager conducts formal delivery verification:

• Verify Quality Approval: Confirm that all quality checks are completed and that formal approval signatures have been secured.
• Obtain Acceptance: Ensure that products pass specified acceptance tests.
• Notify Project Manager: Hand over the completed products (or update asset repositories) and submit a formal completion notification to the Project Manager.

---

Team Plans and Agile Integration in MP

The Role of Team Plans

A Team Plan is produced by the Team Manager during the Accept a Work Package activity. It provides a detailed breakdown of how the team will deliver the Work Package.

• Governance Distinction: Team Plans are optional from the Project Board's perspective but are essential for internal team management. The PM may review Team Plans to gain confidence, but the Project Board approves Stage Plans, not Team Plans.
• Agile Integration: In an agile context, the Team Plan can take the form of a Kanban board, Scrum release plan, or Sprint backlog. PRINCE2 7 explicitly accommodates agile delivery frameworks by allowing Team Managers to execute MP using iterative, incremental delivery techniques.

---

Comparison: Controlling a Stage (CS) vs. Managing Product Delivery (MP)

---

Roles and Responsibilities in MP

• Project Manager: Authorizes Work Packages, reviews Checkpoint Reports, accepts completed products, and maintains overall stage control.
• Team Manager: Executes the MP process—negotiates and accepts Work Packages, creates Team Plans, supervises specialist product creation, conducts quality checks, submits Checkpoint Reports, and formally delivers products.
• Specialist Team Members: Perform technical design, build, and test activities; participate in quality reviews.
• Project Assurance: Inspects quality activities at the delivery level to ensure compliance with the Quality Management Approach.

---

Exam Tips & High-Yield Pitfalls

• Who executes MP? The Team Manager. If no Team Manager is formally appointed, the Project Manager retains responsibility for allocating work, but the person executing the delivery work carries out MP responsibilities.
• Where does specialist work happen? ALL specialist product creation occurs within Managing Product Delivery. No specialist products are built directly in CS, SB, DP, or IP.
• Team Plan vs. Stage Plan: Stage Plans are written by the Project Manager and approved by the Project Board. Team Plans are created by the Team Manager and agreed with the Project Manager.
• When is a Work Package delivered? A Work Package is only delivered after ALL products contained within it have passed their quality checks and received formal approval as defined in the Product Descriptions.