Lesson 11: Managing Product Delivery Process
What does this process do? Can you explain the main outputs? Who’s responsible for the process?
Based on AXELOS PRINCE2® material. Reproduced under licence from AXELOS. All rights reserved.
Note: PRINCE2 2017 edition is now called PRINCE2 6th edition.
- 00:10 – The Managing Product Delivery Process, which is also referred to as the MP process
- 00:16 – The purpose of this MP process is to control the link between the Project Manager and the team managers
- 00:22 – So, control how work is handed out to the teams and agreeing the requirements for acceptance, execution and delivery
- 00:31 – The MP process is where the teams work and it’s where the products get created by the team members
- 00:38 – So, the Project Manager will hand out work to the team managers
- 00:42 – And they should review this work together and make sure that they have the same understanding of what needs to be done
- 00:49 – Therefore, it’s good practice if the Project Manager takes their time in doing this
- 00:55 – Now let’s take a quick look at the objectives of the MP process
- 00:59 – And the first objective is to ensure that work is allocated to the team
- 01:04 – So, this is authorized by the Project Manager and agreed
- 01:08 – The second objective is to ensure that the team members are clear about what has to be delivered and the expected effort
- 01:16 – For example, the expected effort in time and cost
- 01:20 – So a quick question here, which document describes what needs to be delivered?
- 01:26 – These are the product descriptions, so the requirements documents
- 01:30 – The third objective is to ensure that the planned products are delivered to the expected specifications and within tolerance
- 01:38 – So, products meet the quality expectations and pass the quality test
- 01:44 – The fourth objective, to ensure that accurate progress information is provided to the Project Manager at an agreed frequency
- 01:52 – So therefore, the Project Manager can send regular checkpoint reports to the Project Manager to inform them of the progress
- 02:00 – The MP process also has its own activities and these activities interact with three activities from the controlling stage process
- 02:09 – So a tip here, it’s a good idea to view these MP activities from the point of view of the team manager and the team
- 02:18 – So first, a quick reminder of the controlling stage activities that interact with the MP process
- 02:25 – We have already seen these when we discussed the controlling stage process
- 02:29 – We begin with Authorize a Work Package
- 02:32 – And this is where the Project Manager selects work to be done
- 02:36 – And this work is then accepted by the team or the team manager
- 02:41 – The MP activity is called Accept a Work Package
- 02:47 – So both roles, Project Manager and the team manager, should be clear on what has to be done
- 02:52 – And how the team manager will report progress to the Project Manager
- 02:57 – The team then will start to create the products
- 03:00 – We could also refer to this as Execute the Products or Execute a Work Package
- 03:06 – The team will report their progress to the Project Manager using the checkpoint reports
- 03:12 – Once the products are created and tested, then the team will notify the Project Manager that the products are complete
- 03:19 – But the Project Manager here will mainly be interested in that the products have passed the quality checks
- 03:27 – If the products are done and quality checked, then the team manager can deliver the products to the Project Manager
- 03:34 – And PRINCE2 calls this Deliver a Work Package
- 03:39 – So this cycle repeats until all the work has been done for the team in that stage
- 03:45 – Remember again that the Project Manager can be dealing with a number of teams
- 03:51 – And each team can have their own specialty
- 03:55 – Next, take a look at the inputs and outputs for the MP process
- 04:01 – The main input is the work package, so this contains the product descriptions, tolerances and a bit of other information
- 04:08 – The main outputs are the regular checkpoint reports, updates to quality register as the tests are done
- 04:16 – Updates to the configuration item records as the stages of the products will change
- 04:21 – For example, from to-do to done
- 04:23 – And of course, the products themselves, so it’s what the team created
- 04:27 – So these are the main products from a user’s point of view
- 04:32 – So now you have a good idea on how the MP process works
- 04:35 – And this is where the products are delivered
- 04:38 – It’s also why we say that the MP process is in the delivery layer
- 04:44 – A reminder again of the purpose of the MP process
- 04:47 – It’s to control the link between the Project Manager and the team manager
- 04:52 – Control how work is handed out to be done
- 04:56 – And agree the requirements for acceptance, execution and delivery
- 05:02 – That’s it for the MP process
Let’s say you’re the Team Manager working on a Work Package that is supposed to be done in two weeks. While working on the product, you realize that this Work Package needs many changes in the solution and takes about three months. What should you do? What are the possible consequences?
Here you can submit your questions related to the content of the course. (For other questions, use the support system). The trainer's reply will be email to you in 48 hours.
This lesson is part of the first 30% of the course, which is available for free, even without registration.
You can purchase the course to access all lessons, additional material, and coaching:
More info and purchase options