In the context of the PRINCE2 7 Controlling a Stage process, the 'Review stage status' activity acts as the Project Manager's continuous pulse-check of the project's health. It is not a singular event but a recurring cycle of monitoring and assessment designed to ensure the stage remains within agr…In the context of the PRINCE2 7 Controlling a Stage process, the 'Review stage status' activity acts as the Project Manager's continuous pulse-check of the project's health. It is not a singular event but a recurring cycle of monitoring and assessment designed to ensure the stage remains within agreed tolerances for time, cost, quality, scope, sustainability, benefits, and risk.
The primary objective is to maintain an accurate, up-to-date picture of progress. To achieve this, the Project Manager gathers data from various sources, predominantly Checkpoint Reports submitted by Team Managers regarding Work Package progress. The Project Manager also reviews the Quality Register to verify product approvals, assesses the Risk Register for changing threats, and consults the Issue Register to track open concerns.
Upon gathering this data, the Project Manager updates the Stage Plan with actuals. Crucially, this activity moves beyond recording history; it focuses heavily on forecasting. The Project Manager must calculate whether the remaining work can be completed within the stage tolerances. If a deviation beyond tolerance is forecast, it triggers the 'Escalate issues and risks' activity. Furthermore, PRINCE2 7 emphasizes the human aspect here; the Project Manager evaluates team dynamics and relationships to ensure continued productivity.
Ultimately, 'Review stage status' provides the raw analysis required for the 'Report highlights' activity. It ensures that any communication sent to the Project Board via Highlight Reports is based on evidence and realistic forecasts, enabling effective Management by Exception.
Review Stage Status - PRINCE2 Practitioner v7 Guide
What is 'Review Stage Status'? In the PRINCE2 Controlling a Stage process, the Project Manager must maintain a clear, continuous picture of progress. 'Review Stage Status' is the recurring activity where the Project Manager gathers progress information from Team Managers, assesses the health of the stage, and updates the project records. It is the 'heartbeat' of the Project Manager's day-to-day control.
Why is it Important? Without this activity, the Project Manager is 'flying blind'. It is critical because: 1. It provides the mechanism to compare Actuals (what has happened) against the Baseline (the Stage Plan). 2. It allows for the early detection of issues, ensuring Management by Exception can be applied if tolerances are threatened. 3. It ensures the Business Case remains viable by constantly checking risks and benefits.
How it Works This activity is a continuous cycle, often triggered by the receipt of a Checkpoint Report from a Team Manager or a scheduled review point (e.g., every Monday morning). The workflow involves: 1. Review Progress: The PM analyzes Checkpoint Reports to update the Stage Plan with actual start/finish dates and costs. 2. Assess Quality: The PM checks the Quality Register to ensure products are not just 'done', but 'quality approved'. 3. Monitor Uncertainty: The PM reviews the Risk Register and Issue Register to see if any risks have changed or if new issues affect the stage. 4. Forecast: The PM calculates if the remaining work can be completed within the agreed Stage Tolerances.
Exam Tips: Answering Questions on Review Stage Status When answering Practitioner questions, apply the following logic: 1. Input vs. Output: Remember that Checkpoint Reports are an input to this activity. If the question asks what the PM does after receiving a Checkpoint Report, it is 'Review Stage Status'. Conversely, the Highlight Report is an output of the subsequent activity 'Report Highlights'. You must review status before you can report it. 2. The Tolerance Trigger: If a scenario describes the Project Manager identifying that the stage is likely to exceed its budget or time limit, this realization happens during 'Review Stage Status'. The action immediately following this realization is to go to Escalate Issues and Risks. 3. Don't Confuse with Team Manager Duties: If the scenario describes checking the progress of a specific team member or technical detail within a Work Package, that is the Team Manager's role (Managing Product Delivery). 'Review Stage Status' is the Project Manager taking a high-level view of the whole stage. 4. Product Status: In v7, emphasis is placed on product-based planning. If the question mentions updating the Product Status Account or checking product handover status, this occurs within this activity.