# Managing Product Delivery Process

> Chapter 16 of the Courseiva PEOPLECERT-PRINCE2-FOUNDATION curriculum — https://courseiva.com/learn/peoplecert-prince2-foundation/managing-product-delivery-process

**Official objective:** 3.6 — Explain the purpose, objectives, and key activities of the managing product delivery process, including the role of the team manager.

## Introduction

Managing Product Delivery Process is the PRINCE2 process that controls the relationship between the project manager and the people actually building the products. It matters because it ensures that work is properly authorised, progress is visible, and completed products meet the agreed quality criteria before they are handed over — without micromanaging the team.

## The Catering Order Analogy

15 minutes before a wedding reception, the head chef receives a laminated card from the events coordinator. The card lists exactly three dishes, their quantities, the dietary flags (nut-free, halal, vegetarian), and the exact plating temperature. The chef does not redesign the menu, source new ingredients, or negotiate with the bride. She takes the specification, gathers her team, assigns tasks (two chefs on the salmon, one on the salad station), and sets a timeline: all plates finished by 19:00. The kitchen works. At 18:45, the head chef checks the salmon — it is perfectly cooked. At 19:00, the waiters collect the finished plates. The chef signs a completion slip and hands it to the events coordinator. She has done exactly what the coordinator needed, at the quality specified, within the budget of ingredients already purchased. Every dish leaving her kitchen matches the specification card exactly — no substitutions, no surprises. She did not plan the wedding menu (that was the couple and coordinator), and she did not serve the food (that was the waiters). She managed the production of the agreed outputs to the required standard, and she reported progress to the coordinator. That is the Managing Product Delivery Process in a nutshell.

This maps directly to PRINCE2 because the team manager (the chef) receives a work package (the specification card) from the project manager (the events coordinator). The team manager builds the product (the dishes) while monitoring quality and time, then delivers the completed product back to the project manager for integration into the whole project.

## Core explanation

Managing Product Delivery Process (often shortened to MP) is one of the seven processes in PRINCE2. Its job is to bridge the gap between the project manager, who plans the work, and the team that does the hands-on building. In IT projects, this might be developers writing code, testers running checks, or infrastructure engineers setting up servers. Without MP, the project manager would either have to micromanage every detail (which doesn't scale) or lose sight of what the team is actually doing.

The process starts when the project manager hands the team manager a work package. A work package is a formal, written authorisation to create one or more products. It contains the product description (what to build), the quality criteria (how good it must be), the budget and time allowed, and any constraints like security rules or legal requirements. The team manager accepts the work package only if they are confident the team can deliver it within the agreed constraints. If not, they raise an issue with the project manager.

Once accepted, the team manager does four key activities:

- Accept a Work Package: The team manager reviews the work package with their team, confirms they understand it, and formally agrees to deliver. This step creates a contract-like agreement inside the project.
- Execute a Work Package: The team builds the product. The team manager coordinates the work, monitors progress against the plan, and manages day-to-day problems. If something goes wrong (a key team member gets sick, a supplier misses a delivery), the team manager escalates it to the project manager.
- Check Work Package Progress: The team manager regularly reports to the project manager using checkpoints. A checkpoint is a progress report — typically written — that says what has been completed, what is next, and whether there are any issues. In PRINCE2, checkpoint reports are sent at intervals agreed in the work package, often weekly.
- Deliver a Work Package: When the product is finished, the team manager gets it reviewed for quality. The reviewers (often people from outside the team) check it against the quality criteria from the work package. If it passes, the team manager hands the completed product back to the project manager. This formal handover is called delivering the work package.

Why does MP exist? Before PRINCE2, many projects had a messy handover between planning and doing. The project manager would throw requirements over the wall, and the team would build something, but nobody tracked whether it matched. MP creates a clear paper trail. Every work package has a unique identifier, and each delivery is signed off. This helps in audits (someone can prove the product was built to spec) and in governance (the project board can see exactly what work is underway).

MP replaces informal, verbal task assignment. In a small start-up, a founder might walk over to a developer and say, 'build the login page'. In PRINCE2, that same instruction goes through a work package. It sounds bureaucratic, but it prevents misunderstandings. The developer knows exactly what 'done' means, because the quality criteria are written down. The project manager knows exactly when to expect it, because the deadline is in the package.

The role of the team manager is critical here. In PRINCE2, the team manager is not always a single person — it can be a role filled by a team lead, a vendor, or even an external company. The team manager's job is to be the single point of contact for the project manager. They translate the work package into detailed tasks for the team, but they do not need to know every technical detail. They just need to manage the work and report progress.

A common beginner confusion: the team manager is the same as the project manager. They are not. The project manager owns the overall project plan, manages stakeholders, and reports to the project board. The team manager owns only the work inside their work package. They report up to the project manager. In a small project, one person might wear both hats, but the roles are distinct.

MP is also the process where quality control happens. The product description in the work package includes quality methods — for example, 'code must pass 90% of unit tests' or 'document must be reviewed by two peer reviewers'. The team manager is responsible for making sure those quality checks happen before delivery. If the product fails quality, it goes back for rework. The team manager does not decide to lower the quality bar; they must raise a formal issue to the project manager if the criteria cannot be met.

Finally, MP handles the transfer of completed products to the project manager, who then integrates them into the overall project. The process closes when the project manager confirms acceptance. At that point, the team manager is released from the work package and can start the next one.

## Real-world context

Meet Priya, a team manager at a medium-sized software company called CloudSync. The company is building a new dashboard for customers to track their monthly subscription usage. The project manager, Alex, has identified that the dashboard needs three products: a database table to store usage data, an API endpoint to serve the data, and a front-end page to display it. Alex packages each of these into work packages and hands the first one — the database table — to Priya.

Priya opens the work package. It contains:

- A product description specifying the table columns (customer ID, usage in GB, month, timestamp)
- Quality criteria: the table must pass 100% of schema validation tests and must handle 10,000 rows per second
- A budget of 40 hours of database engineer time
- A deadline of 5 working days from acceptance
- Constraints: the table must comply with GDPR (General Data Protection Regulation) rules for data retention

Priya meets with her team of two database engineers. They review the specification and realise that one quality criterion — 10,000 rows per second — might be tricky because the current development database is slow. Priya decides this is a manageable risk, so she accepts the work package formally by signing the project manager's tracking tool. This is the 'Accept a Work Package' step.

Now Priya executes the work. She breaks the 40 hours into tasks: 10 hours for schema design, 15 hours for building the table and indexes, 10 hours for performance testing, and 5 hours for documentation. She assigns tasks to her engineers. Every morning, she checks their progress. On day three, one engineer reports that the performance test is failing at 8,000 rows per second. Priya asks the engineer to try a different indexing strategy. If that fails, she will escalate to Alex as a risk — but it works, and the test passes.

On day four, Priya prepares a checkpoint report for Alex. The report states: 'Database table build is 80% complete. Schema validated. Performance testing passed at 10,500 rows per second. Documentation is in progress. No issues to escalate.' This is the 'Check Work Package Progress' step.

On day five, the table is finished. Priya schedules a quality review with a senior architect from a different team (to get an independent view). The architect confirms the schema looks correct and the performance test results are valid. Priya then formally delivers the completed work package to Alex. She uploads the schema file and the test results to the project repository and sends Alex a notification. This is the 'Deliver a Work Package' step.

Alex reviews the delivery, confirms it meets the quality criteria, and accepts it. Priya's team is now free to start the next work package — the API endpoint. In a real project, Priya might have five work packages running simultaneously. MP gives her a structured way to manage them without chaos.

What Priya actually does day-to-day:

- Reads work packages carefully before accepting them
- Plans the team's tasks in short sprints (often using a simple to-do list or a digital board)
- Holds 15-minute stand-up meetings each morning to check progress
- Writes checkpoint reports — usually a few paragraphs — at the end of each week
- Escalates issues early, before they become crises
- Arranges quality reviews with independent reviewers
- Closes the work package formally and documents lessons learned

## Exam focus

The PRINCE2 Foundation exam will test your understanding of Managing Product Delivery Process in several predictable ways. You need to memorise the purpose, objectives, and activities precisely, because the exam loves to swap words and see if you catch the difference.

First, the exam will ask: 'What is the purpose of the Managing Product Delivery Process?' The correct answer is always: 'To control the link between the project manager and the team managers, by placing formal requirements on accepting, executing, and delivering work packages.' Any answer that says 'to plan the work' or 'to manage the whole project' is wrong. The purpose is about the link and the handover — not about doing the work itself.

Second, the exam will test the four activities. They love to list three of them and one made-up activity (like 'Design the work package' or 'Approve the budget'). The four real activities are:

- Accept a Work Package
- Execute a Work Package
- Check Work Package Progress
- Deliver a Work Package

Memorise them in order. The exam might ask, 'Which activity comes after executing the work package?' The answer is 'Check Work Package Progress' — but they might trap you with 'Deliver a Work Package' as the next step. In reality, you check progress during execution and then deliver at the end.

Third, the exam will test who does what. The team manager accepts the work package, not the project manager. The project manager creates and authorises the work package. The team manager does not create it. Trap: the exam might say, 'The team manager creates the work package for their team.' That is false. The project manager creates it, and the team manager accepts it.

Fourth, the exam tests what a work package contains. Key items: product description, quality criteria, budget, time constraints, and reporting arrangements. Trap: the exam includes 'detailed technical design' as a work package component. That is not true. The work package describes what to build (the product description) but not how to build it (the technical design). The team decides the how.

Fifth, exam questions about checkpoint reports. A checkpoint report is sent by the team manager to the project manager. It covers progress since the last report, next steps, and issues. The report has no set format in PRINCE2 — the project manager defines it. The exam will try to say checkpoint reports go to the project board. They do not. They go to the project manager. The project board gets highlight reports from the project manager.

Sixth, the exam tests the relationship between Managing Product Delivery Process and the Directing a Project Process. Directing a Project authorises the project. Managing Product Delivery happens at the team level. They are not the same. Trap: 'The team manager reports to the project board.' Wrong. The team manager reports to the project manager.

Seventh, the exam will ask about the role of the team manager. Key fact: the team manager can be a person, a group, or even an external supplier. They are the single point of contact for the project manager. They manage the team's work but do not necessarily have technical expertise. Trap: 'The team manager must be a technical expert.' False. They are a manager, not an architect.

Eighth, the exam tests the 'tolerances' concept. Each work package has tolerances — acceptable deviations in time, cost, scope, or quality. If the team manager expects to exceed a tolerance, they must escalate to the project manager. The exam likes to ask, 'What happens if a team manager thinks they will exceed the tolerance?' Answer: They escalate immediately. They do not try to fix it themselves without telling the project manager.

Ninth, the exam will ask about the quality review step. The team manager ensures the product is reviewed against the quality criteria before delivery. The reviewer is often someone independent. Trap: 'The team manager approves their own product.' False. An independent reviewer or the project manager does the approval.

Tenth, the exam tests the end of the process. Managing Product Delivery ends when the work package is delivered and accepted. The project manager then uses the product in the next stage. The process does not include 'starting a new work package' — that is the project manager's job in the Managing a Stage Boundary Process.

## Step by step

1. **Accept a Work Package** — The project manager provides the work package to the team manager. The team manager reviews it with their team to confirm they understand the product description, quality criteria, budget, and deadline. If acceptable, they formally accept it. If not, they raise an issue. This step creates a clear contract for the work.
2. **Execute a Work Package** — The team manager coordinates the team to build the product. They break the work into smaller tasks, assign them to team members, and manage day-to-day issues. They ensure the work stays within tolerances and that quality checks happen during production.
3. **Check Work Package Progress** — The team manager regularly sends checkpoint reports to the project manager. These reports detail what has been completed, what is planned next, and any issues or risks. The frequency of reporting is agreed in the work package. This keeps the project manager informed without needing daily meetings.
4. **Deliver a Work Package** — When the product is finished, the team manager arranges a quality review. An independent reviewer checks the product against the quality criteria. If it passes, the team manager formally hands the completed product and any documentation to the project manager. The project manager then accepts it, and the work package is closed.
5. **Report Lessons Learned** — After delivering the work package, the team manager shares any lessons from the experience — what went well, what went wrong, and what could be improved. This feeds into the project's lessons log and helps future work packages run more smoothly.

## Comparisons

### Managing Product Delivery Process (MP) vs Directing a Project Process (DP)

**Managing Product Delivery Process (MP):**
- Controls the link between project manager and team manager
- Operates at the team level for building products
- Activities include accept, execute, check, and deliver work packages

**Directing a Project Process (DP):**
- Controls the link between project board and project manager
- Operates at the strategic level for the whole project
- Activities include authorise initiation, authorise stages, and give ad hoc direction

### Work Package vs Project Plan

**Work Package:**
- Covers one product or a small group of products
- Created by the project manager for one team
- Contains product description, quality criteria, budget, time, and reporting

**Project Plan:**
- Covers the entire project from start to finish
- Created by the project manager for the project board
- Contains stages, milestones, overall budget, and resource plans

### Team Manager vs Project Manager

**Team Manager:**
- Manages one or more work packages
- Reports to the project manager via checkpoint reports
- Focuses on day-to-day product delivery and team coordination

**Project Manager:**
- Manages the whole project including multiple work packages
- Reports to the project board via highlight reports
- Focuses on overall project governance, risk, and stakeholder management

### Checkpoint Report vs Highlight Report

**Checkpoint Report:**
- Sent from team manager to project manager
- Covers progress on a specific work package
- Frequency agreed in the work package (often weekly)

**Highlight Report:**
- Sent from project manager to project board
- Covers overall project progress across all work packages
- Frequency typically monthly or at stage boundaries

## Common misconceptions

- **Misconception:** The team manager is the same role as the project manager in PRINCE2. **Reality:** The team manager reports to the project manager and manages only the work inside a work package. The project manager manages the project as a whole and reports to the project board. (In small organisations, one person sometimes does both jobs, so beginners assume the roles are identical. PRINCE2 separates them clearly.)
- **Misconception:** The team manager decides what products to build in a work package. **Reality:** The project manager defines the product description and quality criteria in the work package. The team manager only decides how to build it. (Beginners confuse delegation of how with delegation of what. The work package is an instruction, not a blank cheque.)
- **Misconception:** Checkpoint reports are sent to the project board. **Reality:** Checkpoint reports go from the team manager to the project manager. The project board receives highlight reports from the project manager, which summarise multiple checkpoint reports. (The PRINCE2 reporting hierarchy is unfamiliar. Beginners assume that all reports go to the top, but the process has a chain.)
- **Misconception:** The team manager must be a technical expert to manage the work. **Reality:** The team manager is a management role — they coordinate, track progress, and escalate issues. They do not need deep technical skills; they need delegation and communication skills. (People equate 'manager of technical work' with 'most senior technical person'. PRINCE2 separates management from technical execution.)
- **Misconception:** Managing Product Delivery Process includes planning future stages of the project. **Reality:** Planning future stages is done in the Managing a Stage Boundary Process. MP only manages the current work package. (Beginners think that because a process has 'managing' in the name, it handles all management. PRINCE2 splits management into distinct processes.)

## Key takeaways

- Managing Product Delivery Process controls the link between the project manager and the team manager through formal work packages.
- A work package is a written authorisation that contains the product description, quality criteria, budget, time constraints, and reporting arrangements.
- The four activities of MP are: Accept a Work Package, Execute a Work Package, Check Work Package Progress, and Deliver a Work Package.
- The team manager accepts the work package from the project manager and is the single point of contact for that work.
- Checkpoint reports are progress updates sent by the team manager to the project manager, not to the project board.
- If the team manager expects to break a work package tolerance (time, cost, scope, or quality), they must escalate immediately to the project manager.
- Quality reviews on the completed product must be done by someone independent of the team, not by the team manager.
- MP ends when the work package is formally delivered and accepted by the project manager.

## FAQ

**Who creates the work package in PRINCE2?**

The project manager creates and authorises the work package. The team manager accepts it. The team manager does not create it.

**Can the team manager change the quality criteria in a work package?**

No. If the team manager believes the criteria cannot be met, they must escalate to the project manager, who decides whether to change them.

**What happens if the team manager runs out of budget before the product is finished?**

They must escalate to the project manager immediately. The work package has a tolerance; exceeding it requires a formal issue and decision.

**Does the team manager report to the project board?**

No. The team manager reports to the project manager via checkpoint reports. The project manager reports to the project board via highlight reports.

**Is Managing Product Delivery Process the same as project execution?**

No. MP is only one part of execution — it manages the handover of work packages. The whole project execution involves multiple processes, including Managing a Stage Boundary and Directing a Project.

**What is the difference between a checkpoint report and a highlight report?**

A checkpoint report goes from the team manager to the project manager. A highlight report goes from the project manager to the project board. The highlight report summarises multiple checkpoint reports.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/peoplecert-prince2-foundation/managing-product-delivery-process