PRINCE2 7 Practitioner
PRINCE2 7 Practitioner Cheat Sheet
PRINCE2 7 Practitioner Tests Applied Framework Judgment — Not Just Recall
Practitioner tests whether you can apply PRINCE2 7 to complex scenarios, adapt it to context, and recognize correct vs. incorrect application.
Check Your Readiness →
Among the harder certs
Avg: Approximately 60–65%
Pass: 750 / 1000
Most candidates understand PRINCE2 7 Practitioner concepts — and still fail. This exam tests how you apply knowledge under pressure.
Core Framework
PRINCE2 7 Practitioner: Application and Adaptation
Practitioner builds on Foundation by testing applied judgment. Scenarios present project situations and ask whether actions are appropriate, which role should act, and how PRINCE2 would be correctly applied. The exam is open book — the PRINCE2 7 manual is available but question complexity means you can't look everything up.
-
01
Principles Application
— Recognize correct and incorrect application of all 7 principles
-
02
Theme Integration
— Apply all 7 themes appropriately to project scenarios
-
03
Process Navigation
— Select the right process and activities for given situations
-
04
Role Application
— Assign correct responsibilities to project roles
-
05
Tailoring
— Adapt PRINCE2 appropriately to project context and complexity
Scenario Traps
Wrong instinct vs correct approach
The project is approaching the end of a stage and costs are within tolerance
✕ Wrong instinct
Proceed to the next stage without formal authorization
✓ Correct approach
End Stage Assessment is mandatory — the PM must present the End Stage Report to the Project Board for authorization to proceed. Staying within tolerance doesn't bypass the stage authorization requirement.
A stakeholder requests a change to a product after it has been baselined
✕ Wrong instinct
Implement the change since the stakeholder has authority
✓ Correct approach
All changes to baselined products go through Change Control — raise an Issue Report, assess impact, present as a Request for Change to the Project Board for approval
A small project wants to use PRINCE2 but has very limited management resources
✕ Wrong instinct
Skip optional management products to reduce overhead
✓ Correct approach
Tailor PRINCE2 appropriately — combine roles where possible, simplify management products. Tailoring is PRINCE2-compliant; skipping principles is not.
Quick Rules
Know these cold
-
▸
Open book exam — internalize the framework; don't rely on looking everything up
-
▸
All 7 principles are mandatory; themes and processes can be tailored
-
▸
Tolerance exceeded → Exception Report → Exception Plan (not change control)
-
▸
Change request → Issue Report → Request for Change → Project Board decision
-
▸
End Stage Assessment is mandatory before proceeding to the next stage
-
▸
Tailoring adapts the method to context — more complexity does not mean more management products
-
▸
Escalation hierarchy: Team Manager → PM → Project Board — don't skip levels
Self Check
Can you answer these without checking your notes?
In this scenario: "The project is approaching the end of a stage and costs are within tolerance" — what should you do first?
End Stage Assessment is mandatory — the PM must present the End Stage Report to the Project Board for authorization to proceed. Staying within tolerance doesn't bypass the stage authorization requirement.
In this scenario: "A stakeholder requests a change to a product after it has been baselined" — what should you do first?
All changes to baselined products go through Change Control — raise an Issue Report, assess impact, present as a Request for Change to the Project Board for approval
In this scenario: "A small project wants to use PRINCE2 but has very limited management resources" — what should you do first?
Tailor PRINCE2 appropriately — combine roles where possible, simplify management products. Tailoring is PRINCE2-compliant; skipping principles is not.
Failure Patterns
Common Exam Mistakes — What candidates get wrong
Looking up every answer in the manual during the exam
The Practitioner exam is open book, but most questions require judgment, not fact recall. Spending time looking up basic concepts wastes time on applied judgment questions — you must internalize the framework.
Applying PRINCE2 rigidly when tailoring is required
PRINCE2 7 explicitly requires tailoring to the project context. Candidates who apply standard roles and products verbatim to scenarios that call for adaptation fail tailoring questions.
Misidentifying management product ownership
Project Brief: created by the Executive. PID: owned by the Project Manager. Work Package: created by PM, accepted by Team Manager. Stage Plan: created by PM. Candidates confuse who creates vs. who approves vs. who owns each product.
Confusing exception management with change control
Exception management handles when tolerances are exceeded (Exception Report → Exception Plan). Change control handles requests to change project products (Issue Report → Request for Change). Different processes triggered by different events.
Misidentifying the correct escalation path
Escalation in PRINCE2 follows the management hierarchy: Team Manager → Project Manager → Project Board → Corporate/Programme Management. Bypassing levels is incorrect — each level manages within its tolerances.
PRINCE2 Practitioner tests applied judgment, not framework recall. Test whether you can apply PRINCE2 correctly to real scenarios.