7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
Key Takeaways
- PRINCE2 7 integrates 7 Processes across 4 Management Levels: Corporate/Programme, Directing, Managing, and Delivering.
- The project journey flows sequentially through Pre-Project (SU/DP), Initiation Stage (IP/CS/DP), Delivery Stages (CS/MP/SB/DP), and Final Stage (CS/MP/CP/DP).
- Key decision gates occur at Authorize Initiation, Authorize the Project, Authorize a Stage/Exception Plan, and Authorize Project Closure.
- Processes seamlessly weave together the 7 Principles, 7 Practices, and 7 Management Products, tailored to organizational context.
- PeopleCert PRINCE2 7 Foundation: 60 closed-book MCQs in 60 minutes; pass mark 36/60 (60%).
7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
Exam Focus: This synthesis section connects all seven PRINCE2 7 processes into a unified, end-to-end operational lifecycle. Candidates will learn how information, decisions, and management products flow across management levels from pre-project startup to post-project closure. This section provides the ultimate revision roadmap and exam walkthrough strategy.
The Complete PRINCE2 7 Process Lifecycle Architecture
PRINCE2 7 organizes project governance across four management levels and seven processes:
+-------------------------------------------------------------------------------------------------------------------+
| 1. CORPORATE / PROGRAMME MANAGEMENT / CUSTOMER |
| • Issues Project Mandate • Appoints Executive & PM • Receives Post-Project Benefits Reports |
+-------------------------------------------------------------------------------------------------------------------+
| Mandate ^ Post-Project Benefits
v |
+-------------------------------------------------------------------------------------------------------------------+
| 2. DIRECTING LEVEL (Project Board) - PROCESS: DIRECTING A PROJECT (DP) |
| |
| [Authorize Initiation] [Authorize Project] [Authorize Stage / Exception Plan] [Authorize Project Closure] |
+-------------------------------------------------------------------------------------------------------------------+
^ Notification ^ PID Baseline ^ Stage / Exception Plan ^ Closure Rec.
| Request | Request | Request | Request
+-------------------------------------------------------------------------------------------------------------------+
| 3. MANAGING LEVEL (Project Manager) - PROCESSES: SU, IP, CS, SB, CP |
| |
| PRE-PROJECT INITIATION STAGE DELIVERY MANAGEMENT STAGE(S) FINAL MANAGEMENT STAGE |
| +------------+ +---------------+ +-------------------+ +---------------+ +--------------------+ |
| | STARTING | | INITIATING | | CONTROLLING | | MANAGING A | | CONTROLLING | CLOSING |
| | UP A PROJ |--->| A PROJECT |------>| A STAGE (CS) |->| STAGE BOUNDARY|-->| A STAGE (CS)| A PROJ | |
| | (SU) | | (IP) | +-------------------+ | (SB) | +-------------| (CP) | |
| +------------+ +---------------+ ^ +---------------+ ^ +----+ |
+------------------------------------------------------|-------------------------------------------|----------------+
| Work Package / | Work Package /
v Checkpoint Reports v Checkpoint Rep.
+-------------------------------------------------------------------------------------------------------------------+
| 4. DELIVERING LEVEL (Team Manager / Delivery Team) - PROCESS: MANAGING PRODUCT DELIVERY (MP) |
| |
| +-------------------------------------------------------------------------------------------------------------+ |
| | MANAGING PRODUCT DELIVERY (MP): Accept Work Package --> Execute Work Package --> Deliver Work Package | |
| +-------------------------------------------------------------------------------------------------------------+ |
+-------------------------------------------------------------------------------------------------------------------+
Chronological Stage-by-Stage Process Walkthrough
Phase 1: Pre-Project (Starting Up a Project & Early Directing)
- Trigger: Corporate/Programme Management issues a Project Mandate.
- Process Executed: Starting Up a Project (SU) run by the Project Manager (supported by Executive).
- Key Output: Project Brief, Stage Plan for Initiation, and outline Business Case.
- Decision Gate 1 (DP): Project Board evaluates Project Brief and decides whether to Authorize Initiation.
Phase 2: Initiation Stage (Initiating a Project & Directing)
- Process Executed: Initiating a Project (IP) run by the Project Manager.
- Key Output: Complete Project Initiation Documentation (PID) including Project Plan, Business Case, 5 Management Approaches (Digital/Data, Commercial, Quality, Risk, Communication), and Stage Plan for Stage 2.
- Decision Gate 2 (DP): Project Board evaluates PID and decides whether to Authorize the Project and authorize Stage 2.
Phase 3: Delivery Stages (Controlling a Stage, Managing Product Delivery, Managing a Stage Boundary)
- Process Executed by PM: Controlling a Stage (CS)—issues Work Packages, monitors progress via Checkpoints, logs issues/risks, sends Highlight Reports to Project Board.
- Process Executed by TM: Managing Product Delivery (MP)—accepts Work Package, builds/tests products, submits Checkpoint Reports, delivers completed products.
- Stage End Trigger (PM): Near stage end, PM executes Managing a Stage Boundary (SB) to prepare End Stage Report, Next Stage Plan, and updated Business Case.
- Decision Gate 3 (DP): Project Board evaluates SB documents and decides whether to Authorize the Next Stage (or approve an Exception Plan).
Phase 4: Final Management Stage & Project Closure (CS, MP, Closing a Project, Directing Closure)
- Delivery Execution: PM executes CS and TM executes MP to complete final specialist products.
- Closure Execution: PM executes Closing a Project (CP)—secures product acceptance, completes handover, writes End Project Report and Lessons Report, updates Benefits Management Approach, and recommends closure.
- Decision Gate 4 (DP): Project Board evaluates closure recommendation in Directing a Project (DP), formally authorizes Project Closure, and releases project resources.
Master PRINCE2 7 Process Reference Matrix
| Process Name | Abbr. | Primary Role | Management Level | Trigger / Input | Primary Output / Decision |
|---|---|---|---|---|---|
| Starting Up a Project | SU | Project Manager | Managing | Project Mandate | Project Brief, Initiation Stage Plan |
| Directing a Project | DP | Project Board | Directing | Requests from PM | 4 Major Authorizations / Key Decisions |
| Initiating a Project | IP | Project Manager | Managing | Authorization to Initiate | PID, Overall Project Plan, Stage 2 Plan |
| Controlling a Stage | CS | Project Manager | Managing | Stage Authorization | Work Packages, Highlight Reports, Exception Reports |
| Managing Product Delivery | MP | Team Manager | Delivering | Work Package from PM | Team Plan, Checkpoint Reports, Accepted Products |
| Managing a Stage Boundary | SB | Project Manager | Managing | Approaching stage end / Exception request | End Stage Report, Next Stage Plan, Exception Plan |
| Closing a Project | CP | Project Manager | Managing | Final stage nearing end / Board direction | End Project Report, Lessons Report, Closure Recommendation |
Scenario-Based Exam Strategy & Trap Avoidance Guide
When tackling PRINCE2 7 Foundation exam questions, apply this 4-step decision algorithm:
+-----------------------------------------------------------------------------+
| EXAM QUESTION DECISION ALGORITHM |
| |
| STEP 1: Identify the Management Level (Directing, Managing, Delivering). |
| STEP 2: Pinpoint the Current Lifecycle Stage (Pre-proj, Initiation, |
| Delivery, Final Stage). |
| STEP 3: Check Role Authority (Board authorizes; PM manages/recommends; |
| TM delivers). |
| STEP 4: Match Document to Purpose (e.g. Highlight = PM->Board; |
| Checkpoint = TM->PM). |
+-----------------------------------------------------------------------------+
Top 5 PRINCE2 7 Exam Traps to Avoid:
- Confusing Process Owners: Do not select Project Manager for Directing a Project decisions (DP is strictly Project Board). Do not select Project Board for creating Work Packages (CS is PM).
- Misplacing Stage Boundary Execution: SB is executed in intermediate delivery stages, NOT the final stage. The final stage uses CP.
- Premature Action vs. Escalation: If an issue threatens stage tolerance, the PM MUST create an Exception Report. The PM NEVER expands tolerances independently.
- Confusing Product Delivery Levels: Specialist products are ONLY created in Managing Product Delivery (MP). They are never built in CS, SB, or DP.
- Closure Authority: The PM recommends closure in CP, but ONLY the Project Board authorizes project closure in DP.
Official PRINCE2 7 Foundation Exam Format (PeopleCert)
Confirm logistics from the PeopleCert exam specification before booking:
| Item | Official Foundation (Version 7) |
|---|---|
| Questions | 60 multiple-choice (standard, missing-word, list, and exceptional negative stems) |
| Duration | 60 minutes (75 minutes if the exam language is not your native/working language — 25% extra time) |
| Materials | Closed book — the official manual is for study only and is not permitted in the exam |
| Pass mark | 36/60 (60%) |
| Thinking level | Bloom's levels 1–2 (recall and understanding) |
| Prerequisite | None for Foundation; Foundation is a prerequisite for Practitioner |
Syllabus emphasis: PeopleCert weights the Foundation paper heavily toward the practices (~60% of marks), with People (~14%), Processes (~15%), Principles (~8%), and Key concepts (~3%). Study time should mirror that weighting—especially Issues, Organizing, Plans, Quality, Risk, Business Case, and Progress.
Final PRINCE2 7 Foundation Exam Preparation Checklist
Before taking your exam, ensure you can confidently answer YES to all of the following core concepts:
- Can you list all 7 Processes, 7 Principles, 7 Practices, and 7 Roles in PRINCE2 7?
- Do you know which process belongs to which management level?
- Can you state the exact inputs, outputs, and triggers for SU, DP, IP, CS, MP, SB, and CP?
- Do you understand the difference between Checkpoint, Highlight, End Stage, and End Project Reports?
- Can you trace how an Exception Report leads to an Exception Plan via SB?
- Do you know what happens during planned vs. premature project closure?
- Can you explain how People and Tailoring permeate all process workflows in PRINCE2 7?
Which sequence correctly reflects the chronological flow of PRINCE2 7 processes for a standard multi-stage project?
If a Team Manager identifies that a technical problem will cause a Work Package to exceed its cost tolerance, what action should the Team Manager take first?
Which PRINCE2 process runs continuously alongside all other processes throughout the entire project lifecycle, from pre-project startup to final closure?
You've completed this section
Continue exploring other exams