In the context of the PRINCE2 7 'Controlling a Stage' process, the activity 'Receive Completed Work Packages' acts as the formal checkpoint where the Project Manager reassumes control of products from the Team Manager. This activity ensures that the handshake between project management and product …In the context of the PRINCE2 7 'Controlling a Stage' process, the activity 'Receive Completed Work Packages' acts as the formal checkpoint where the Project Manager reassumes control of products from the Team Manager. This activity ensures that the handshake between project management and product delivery is governed by quality and verification rather than assumptions.
The process is triggered when the Team Manager notifies the Project Manager that the work defined in a Work Package is finished. However, the Project Manager does not simply accept this notification at face value. Instead, they must perform rigorous checks to confirm the work is truly complete and fit for purpose.
The primary focus is on the **Quality Register**. The Project Manager must verify that all quality management activities—such as testing, inspections, or reviews—specified in the Work Package have been executed. They must confirm that the products have been approved by the designated authorities and that the quality records are complete. In PRINCE2, a product is effectively non-existent until it passes its quality criteria.
Once quality is verified, administrative housekeeping is essential. The **Configuration Item Records** are updated to change the status of the products to 'baselined,' ensuring version control is maintained. Additionally, the **Stage Plan** is updated with the actual progress and completion dates. This updated data is vital for the subsequent activity, 'Review the Stage Status,' allowing the Project Manager to determine if the stage is proceeding within agreed tolerances.
Ultimately, this activity prevents '99% complete' syndrome. By enforcing strict acceptance criteria, the Project Manager ensures that the project only progresses based on verified, quality-assured deliverables.
Guide: Receive Completed Work Packages (PRINCE2 Practitioner v7)
What is 'Receive Completed Work Packages'? This activity is part of the Controlling a Stage process. It represents the formal handshake between the Team Manager and the Project Manager. Once a team has finished the work defined in a Work Package and completed all necessary quality checks, they return ownership of the products to the Project Manager. This activity ensures that the work is truly complete and approved before the team is released to other duties.
Why is it important? This step prevents 'phantom completion' where work is marked done but still requires fixes. It is critical for: 1. Quality Assurance: Ensuring the Quality Register confirms that all products have passed their tests. 2. Asset Management: Ensuring Configuration Item Records are updated so the current status of the product is known (baselined). 3. Control: Allowing the Project Manager to update the Stage Plan with actuals to monitor progress.
How it works The activity is triggered when the Team Manager submits the products. The Project Manager then: 1. Checks the Quality Register to verify that the reviewers have signed off on the products. 2. Checks that the Configuration Item Records are updated (often verifying the Product Status Account). 3. Updates the Stage Plan to show the Work Package is completed.
How to Answer Practitioner Exam Questions In the exam, you will likely be presented with a scenario where a Team Manager claims work is finished. You may be asked to determine the appropriate next step or identify a missing action. 1. Look for the Trigger: The scenario will mention a notification from the Team Manager or the delivery of a product. 2. Identify the Documents: The correct answer often involves checking the Quality Register or updating the Stage Plan. 3. Verify Roles: Ensure the Project Manager is the one performing the acceptance (not the Project Board).
Exam Tips: Answering Questions on Receive Completed Work Packages Tip 1: Check, don't Do. The Project Manager usually verifies the quality check was done (by looking at the register); they do not necessarily perform the quality inspection themselves at this stage. Tip 2: The Configuration Link. If a question asks how the PM confirms the product is safe or baselined, look for answers involving the Product Status Account or Configuration Item Records. Tip 3: The Boundary. Do not confuse this with Managing a Stage Boundary. This activity happens during the stage execution whenever a Work Package is finished. It is operational control, not a replanning event.