In the context of PRINCE2 7, a Stage Plan is a detailed management product created to facilitate day-to-day control over a specific management stage. While the overarching Project Plan provides a high-level roadmap and the Business Case justifies the investment, the Stage Plan offers the granular d…In the context of PRINCE2 7, a Stage Plan is a detailed management product created to facilitate day-to-day control over a specific management stage. While the overarching Project Plan provides a high-level roadmap and the Business Case justifies the investment, the Stage Plan offers the granular detail required for execution and monitoring. It is typically produced by the Project Manager near the end of the current stage during the 'Managing a Stage Boundary' process, serving as a prerequisite for the Project Board to authorize the next stage.
Within the Plans Practice, the Stage Plan is distinct because it operates on a shorter planning horizon, allowing for greater accuracy in estimating time, costs, and resources compared to the Project Plan. It breaks down the stage deliverables into activities and products, forming the basis for the Work Packages assigned to Team Managers. The plan must include details on quality management activities, risk responses, specific resource requirements, and the schedule for the stage.
Crucially, the Stage Plan acts as the 'contract' between the Project Manager and the Project Board. The Board approves this plan and sets specific tolerances (limits on time, cost, scope, quality, risk, benefits, and sustainability). If the Project Manager forecasts that the stage will remain within these tolerances, execution continues. However, if tolerances are forecast to be exceeded, the Stage Plan is effectively invalidated, triggering an Exception Report. If the Board wishes to proceed, the Stage Plan is then replaced by an Exception Plan. This structure ensures that the project is managed in manageable 'bites,' preventing loss of control over long durations.
Concept Guide: Stage Plan (PRINCE2 Practitioner v7)
What is a Stage Plan? In PRINCE2 v7, a Stage Plan is a detailed plan used as the basis for project management control throughout a management stage. While the Project Plan provides a high-level overview of the entire project, the Stage Plan provides the specific, granular detail required for the Project Manager to manage day-to-day progress. It is mandatory for every management stage.
Why is it Important? Planning the entirety of a project in microscopic detail from day one is often impossible due to the 'planning horizon'—the point where it becomes difficult to predict the future with accuracy. The Stage Plan solves this by applying rolling wave planning. It allows the project to proceed with a high-level Project Plan, while the immediate next stage is planned in high detail. It provides the basis for the Project Board to authorize the stage and for the Project Manager to issue Work Packages.
How it Works The Stage Plan is distinct from the Project Plan in terms of detail and timescale. It is usually produced in the Managing a Stage Boundary process (planning for the next stage) or the Initiating a Project process (planning for the first delivery stage). The creation follows the standard PRINCE2 approach to planning: 1. Design the plan: Determine format and tools. 2. Define and analyze products: Use Product-Based Planning (Product Flow Diagrams, Product Descriptions) to define exactly what will be built during this stage. 3. Identify activities and dependencies: What needs to be done to create those products. 4. Prepare estimates: Time, cost, and resources specifically for this stage. 5. Prepare the schedule: Assigning specific dates. 6. Document the plan: Including specific tolerances for the stage.
Exam Tips: Answering Questions on Stage Plan In the Practitioner exam, you will need to distinguish the Stage Plan from the Project Plan and Team Plans. Use these tips: 1. Check the Process Context: If the scenario is in Controlling a Stage, the Stage Plan is the baseline being measured against. If the scenario is in Managing a Stage Boundary, the Project Manager is creating a Stage Plan for the next stage to submit for approval. 2. Look for 'Adequate Detail': A common exam question asks if a plan is suitable. A valid Stage Plan must be detailed enough to act as a basis for day-to-day control and to create Work Packages, but it does not need the minute technical minutiae found in a Team Plan. 3. Tolerance Breaches: If a question states that a stage is forecast to exceed its tolerances, the answer is usually that the Stage Plan is no longer valid and must be replaced by an Exception Plan (which is created to the same level of detail as a Stage Plan). 4. Product Focus: Questions often test the link between plans and quality. Remember that the Stage Plan includes the quality management activities (reviews, tests) specific to the products delivered in that stage.