In PRINCE2, progress is not measured by how busy teams are, but by how reliably products are delivered. The Managing Product Delivery (MP) process sits at the center of this philosophy. It is where strategy meets execution—where expectations set by the Project Manager are translated into tangible, quality-assured outputs by delivery teams.

MP is not about micromanagement. It is about trust, clarity, and control—backed by simple templates and meaningful KPIs that keep delivery honest.

1. The Role of Managing Product Delivery

Managing Product Delivery defines the interface between the Project Manager and the Team Manager. Its purpose is straightforward:

• Accept work packages
• Execute the work
• Deliver completed products that meet agreed quality criteria

This process ensures that delivery happens in a controlled manner, without constant escalation or ambiguity. The Project Manager sets what is needed and when; the Team Manager decides how the work gets done.

2. Core Activities in MP

The MP process revolves around three key activities:

1. Accept a Work Package

Before any work begins, the Team Manager confirms that:

• Requirements are clear
• Quality criteria are understood
• Constraints and tolerances are realistic
• Required resources are available

This checkpoint prevents teams from starting work on incomplete or poorly defined expectations—a common cause of rework.

1. Execute a Work Package

Here, the delivery team creates the product while:

• Managing day-to-day progress
• Monitoring quality against agreed criteria
• Handling issues within tolerance

The focus is disciplined execution, not excessive reporting.

1. Deliver a Work Package

Once complete, the product is handed back with evidence:

• Quality checks completed
• Acceptance criteria met
• Any deviations documented

Only finished, approved products move forward—no half-done deliverables disguised as progress.