Study guide
2.4 Principle 4: Manage by Stages
PRINCE2 7 Foundation Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Key Concepts, Framework & Integrated Elements
1.1 PRINCE2 7 Method Overview & Project Context 1.2 Seven Performance Aspects & Delivery Approaches 1.3 Outputs, Outcomes, Benefits & Value Creation 1.4 Management Products vs Specialist Products 1.5 PRINCE2 Governance, Tailoring & Distinct Features
2 Chapter 2: The Seven PRINCE2 7 Principles
2.1 Principle 1: Continued Business Justification 2.2 Principle 2: Learn from Experience 2.3 Principle 3: Define Roles, Responsibilities and Relationships 2.4 Principle 4: Manage by Stages 2.5 Principle 5: Manage by Exception 2.6 Principle 6: Focus on Products 2.7 Principle 7: Tailor to Suit the Project
3 Chapter 3: The People Element in PRINCE2 7
3.1 Capable People & Organizational Culture 3.2 Project Teams & Team Dynamics 3.3 Leading Project Teams 3.4 Communication & Stakeholder Engagement 3.5 Organizational Change Management (OCM)
4 Chapter 4: The PRINCE2 7 Practices - Strategy, Organization & Planning
4.1 Business Case Practice 4.2 Organizing Practice & Project Management Team 4.3 Commercial & Stakeholder Aspects of Organizing 4.4 Plans Practice & Levels of Plans 4.5 Product-Based Planning Technique 4.6 Quality Practice & Quality Control
5 Chapter 5: The PRINCE2 7 Practices - Risk, Change & Progress Control
5.1 Risk Practice & Risk Management Approach 5.2 Issues Practice & Issue Management Approach 5.3 Change Control & Configuration Management 5.4 Progress Practice & Control Mechanisms 5.5 Management Reports & Logs/Registers 5.6 Sustainability & Digital Integration in Practices
6 Chapter 6: The PRINCE2 7 Processes - Pre-Project & Initiation
6.1 Overview of PRINCE2 7 Process Model & Flow 6.2 Starting Up a Project (SU) Process 6.3 Directing a Project (DP) Process 6.4 Initiating a Project (IP) Process 6.5 Assembling the Project Initiation Documentation (PID)
7 Chapter 7: The PRINCE2 7 Processes - Delivery, Boundary & Closure
7.1 Controlling a Stage (CS) Process 7.2 Managing Product Delivery (MP) Process 7.3 Managing a Stage Boundary (SB) Process 7.4 Closing a Project (CP) Process 7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
2.4 Principle 4: Manage by Stages
Key Takeaways Explain This Topic AI
A PRINCE2 project is planned, monitored, and controlled on a stage-by-stage basis through discrete management stages.
PRINCE2 requires a minimum of two management stages: an Initiation Stage (for detailed planning/PID preparation) and at least one Subsequent Management Stage.
Management stages provide formal review points (stage boundaries) where the Project Board evaluates project performance, business justification, and risk before committing funds to the next stage.
The length and number of management stages depend on project risk, technical complexity, decision gates, organizational standards, and delivery approach.
Management stages differ from technical stages: management stages are decision and control boundaries, while technical stages represent skill sets or work phases.
Last updated: July 2026
2.4 Principle 4: Manage by Stages
High-level strategic plans covering multi-year horizons are inherently inaccurate. Attempting to plan a complex, 18-month project in granular detail on Day 1 is an exercise in futility because market conditions, technical realities, and stakeholder priorities change. Conversely, managing a project without intermediate control points creates a dangerous "black hole" where leadership loses visibility until the deadline arrives.
PRINCE2 Principle 4: Manage by Stages resolves this dilemma by breaking the project into discrete, manageable periods called Management Stages .
PRINCE2 Principle Rule: A PRINCE2 project is planned, monitored, and controlled on a stage-by-stage basis.
The Concept of Stage-Based Control
PRINCE2 mandates that project planning and authority are committed one management stage at a time. The Project Board authorizes the Project Manager to proceed only for the duration of the upcoming management stage .
At the end of each management stage (a stage boundary ), the project team must present actual performance results and an updated forward plan. The Project Board reviews whether the project remains viable before releasing funds and resources for the next stage. +-----------------------------------------------------------------------------------+
- | STAGE-BASED COMMITMENT LIFECYCLE |
- +-----------------------------------------------------------------------------------+
- | [Pre-Project] -> [Stage 1: Initiation] -> [GATE 1] -> [Stage 2: Build] -> [GATE 2]|
- | (Detailed PID) (Approve) (Specialist Work) (Approve) |
- +-----------------------------------------------------------------------------------+
- The Minimum Two-Stage Requirement
Exam Rule: A PRINCE2 project must have a minimum of two management stages :
The Initiation Stage: The initial management stage during which the project team prepares the Project Initiation Documentation (PID), detailed Business Case, Risk Register, and management approaches. No major specialist product construction occurs here.
At Least One Delivery Stage (Subsequent Stage): Management stage(s) during which the specialist products of the project are created, tested, and handed over.
A project with only one management stage cannot be a PRINCE2 project, because there would be no distinct initiation phase and no stage boundary decision gates.
Management Stages vs. Technical Stages
A critical distinction on the Foundation exam is the difference between Management Stages and Technical Stages :
Feature Management Stages Technical Stages
Primary Purpose Commitment of funds, governance, business justification review, and decision-making Grouping of technical activities, skill sets, or work methodologies
Driven By Project Board authority, risk levels, decision gates Engineering practices, architectural phases (e.g., Design, Build, Test)
Boundaries Defined By Formal reviews using Managing a Stage Boundary process Technical completion milestones (e.g., code freeze, blueprint approval)
Crossing Alignment Cannot cross. Management stages are sequential and distinct. Can cross. A technical phase (e.g., testing) can span across two management stages. TECHNICAL STAGES: [----- Requirements & Design -----] [---------- Build & Integration ----------] [--- Test ---]
| |
MANAGEMENT STAGES: [---- Stage 1: Initiation ----] [---- Stage 2: Core Build ----] [---- Stage 3: Rollout ----]
- ^ ^
- Stage Boundary Stage Boundary
As illustrated above, technical activities can span management boundaries, but management stage boundaries represent hard commitment gates for the Project Board.
Factors Determining Stage Length and Number
How does a Project Manager determine how many management stages a project should have? The decision depends on balancing five factors:
Planning Horizon: How far into the future can the Project Manager accurately forecast costs and schedules? (Typically 2 to 6 months).
Project Risk: High-risk projects require shorter management stages to allow more frequent Project Board reviews and control gates.
Key Decision Gates: Aligning stage boundaries with major capital investment decisions or external vendor milestone payments.
Organizational Standards: Corporate policies that require quarterly financial reviews or governance checkpoints.
Delivery Approach (Agile vs. Predictive): In an agile environment, several sprints or iterations may be grouped into a single PRINCE2 management stage to provide governance while allowing flexible sprint execution.
Governance Mechanics at Stage Boundaries
When a management stage nears completion, the Project Manager initiates the Managing a Stage Boundary process:
End Stage Report: Formally documents actual performance against the stage plan targets (time, cost, quality, scope, benefits, sustainability).
Lessons Report: Highlights new lessons captured during the stage.
Updated Business Case & Risk Register: Reflects current project realities.
Next Stage Plan: Details the exact activities, schedules, and budgets for the upcoming stage.
The Project Board evaluates these artifacts during the Directing a Project process and chooses one of three decisions:
Authorize the next Stage Plan (Project proceeds).
Request an Exception Plan / Re-plan (If forecasts exceed tolerances or plans are inadequate).
Terminate the project prematurely (If business justification has lapsed).
Summary Comparison: Management Stages across Project Scales
Project Scale Number of Stages Typical Stage Duration Stage Boundary Formalities
Small / Low Risk 2 Stages (Initiation + 1 Delivery) 1 - 3 Months Concise End Stage Report, brief Project Board meeting or email signoff.
Medium / Moderate Risk 3 - 5 Stages 3 - 6 Months Formal End Stage Report, updated PID, presentation to Project Board.
Large / Complex / High Risk 6+ Stages 2 - 4 Months Rigorous stage reviews, independent Project Assurance audits, gateway reviews.