Controlling a Stage Process

The primary purpose of reviewing stage status in PRINCE2 7 is to confirm whether the current management stage remains viable and can achieve its defined objectives within approved tolerances.

This is the correct answer because:
- Stage status reviews are fundamentally about assessing ongoing viability of the current stage
- The focus is on whether the stage can still achieve its objectives
- Operating within approved tolerances is a key PRINCE2 principle that determines if the stage can continue without escalation
- This aligns with the 'Manage by exception' principle, where continuation depends on staying within agreed boundaries

Why the other answers are incorrect:

The second option focuses too narrowly on resource consumption rates and baseline schedules. While these are important metrics to monitor, they are components of the broader viability assessment rather than the primary purpose. A stage could consume resources at the anticipated rate but still not be viable due to other factors like changed business priorities or emerging risks.

The third option incorrectly suggests the review is about deciding whether to proceed to the next stage boundary. This confuses stage status reviews with end stage assessments. Stage status reviews occur during a stage to monitor ongoing viability, not to authorize moving to the next stage - that's the purpose of the 'Managing a Stage Boundary' process.

The fourth option presents a checklist approach focusing on risks, issues, stakeholder satisfaction, and governance. While these are important considerations, they are elements that feed into the viability assessment rather than representing the primary purpose. The review isn't about confirming all risks are addressed, but rather about determining if the stage can still achieve its objectives despite the current situation.

The primary function of a stage status review in PRINCE2 7 is to determine if the stage's planned products are complete and forecasted performance remains within approved tolerances.

This is correct because stage status reviews are specifically designed to assess whether the current management stage can proceed to its planned boundary by evaluating two critical aspects:

1. Product completion - verifying that the planned products for the stage have been delivered
2. Tolerance adherence - confirming that forecasted performance (time, cost, scope, quality, risk, and benefit) remains within the tolerances approved by the Project Board

These reviews enable the Project Manager to determine if the stage can successfully close and transition to the next stage, or if escalation to the Project Board is required due to tolerance deviations.

The other options are incorrect because:

The second option incorrectly focuses on comparing current resource utilization against original initiation estimates, which is not the primary focus of a stage boundary review. PRINCE2 emphasizes tolerance management against approved stage-level tolerances, not historical comparisons to initiation baselines.

The third option incorrectly emphasizes baseline documentation updates and stakeholder communications as the primary function. While these are important project activities, they are not the core purpose of a stage status review, which focuses on product completion and tolerance status.

The fourth option incorrectly emphasizes user acceptance criteria and continuous improvement indicators. While quality is important, the stage status review specifically focuses on planned product completion and tolerance adherence, not detailed acceptance criteria or team performance improvement metrics.

The correct answer is Work Package.

A Work Package is the formal document that serves as an agreement between the Project Manager and the Team Manager (or team member) defining the work to be completed. It is the means by which the Project Manager delegates work to be done and provides authorization for the Team Manager to proceed. The Work Package contains all the necessary information about what needs to be delivered, including product descriptions, quality requirements, tolerances, constraints, and reporting arrangements.

Why the other answers are incorrect:

Product Description defines the characteristics, quality criteria, and acceptance criteria for a specific product, but it is not an agreement between Project Manager and Team Manager - it is a component that may be included within a Work Package.

Stage Plan is a detailed plan for the current management stage, created by the Project Manager and approved by the Project Board. It is not an agreement with Team Managers about specific work packages, but rather a higher-level plan showing how the entire stage will be delivered.

Team Plan is an optional plan that may be created by the Team Manager to show how they will deliver the work allocated to them. While it relates to work assignment, it is not the formal agreement document between Project Manager and Team Manager - the Work Package serves that purpose. The Team Plan is created by the Team Manager after receiving the Work Package.