14.3 Final Exam Technique, Full Scenarios & Common Traps

The Exam at a Glance

The PRINCE2 Practitioner exam is an open-book, 70-mark, 150-minute assessment. The pass mark is 60%, which means you need 42 of 70 marks. Do not carry the retired v6 numbers into the exam room: there is no 68 questions / 55% standard anymore.

You are allowed the official PRINCE2 7 manual (print or digital, depending on the delivery platform). No other materials. This makes how you use the manual as important as what you remember — the exam is not a memory test, but you will not have time to read passages. You will have time to look up a specific practice, process, or management product.

Seven-Step Exam Strategy

1. Tab the Manual Before the Exam

Tab three dimensions:

• By practice — Business Case, Organising, Plans, Quality, Risk, Issues, Progress, Sustainability, People.
• By process — Starting Up, Directing, Initiating, Controlling a Stage, Managing Product Delivery, Managing a Stage Boundary, Closing, Tailoring.
• By management product — PID, Project Plan, Stage Plan, Work Package, Project Log, Highlight Report, Checkpoint Report, End Stage Report, End Project Report, Exception Report.

The goal is to flip to the right page in under 15 seconds. If you are slower than that, you will burn time you cannot spare.

2. Read Additional Information First

Each scenario comes with an Additional Information section that lists project personnel, roles, and context. Read it before the questions. Note who the Project Executive is, who the Senior User and Senior Supplier are, whether there is a Team Manager, and any commercial context (supplier, programme, standalone). Many items hinge on whose role is this? — if you have not noted the cast, you will misattribute actions.

3. Evaluate the 'Because' Clause in Classic Items

The classic item format is: Is the statement X correct? Yes/No, because [reason]. The scoring is typically 1 mark for Yes/No and 1 mark for a correct justification. A wrong because makes the whole answer wrong — even if the Yes/No sounds defensible. Read the because first; if it is false or cites the wrong practice/process, eliminate the whole option regardless of how the Yes/No reads.

4. Solve Confident Matching Items First

Matching items typically offer 3 marks and a list of options that can be reused or left unused. Solve the items you are confident about first; this narrows the remaining options. Do not assume each option is used exactly once — the format explicitly allows reuse and omissions.

5. Time: About 2.1 Minutes per Mark

150 minutes for 70 marks is roughly 2.1 minutes per mark. Build a buffer: aim to be through the paper with 10–15 minutes left for review and to return to hard items. If an item is taking more than 4 minutes, flag it and move on — a 1-mark item is not worth 6 minutes.

6. Watch for v6 Vocabulary Traps

Examiners and distractors still trade on v6 vocabulary. Be alert for:

If a scenario or option uses v6 vocabulary without acknowledging the v7 change, treat it as a warning sign — not automatically wrong, but a likely distractor.

7. Watch for True-but-Wrong Options

A true-but-wrong option is a statement that is factually correct in PRINCE2 but does not answer this scenario. Example: The Project Manager should update the Project Plan. That is generally true, but if the scenario asks what the Project Board should do when a stage tolerance is breached, the correct answer is give exception direction, not the PM updates the Project Plan. Always ask: does this option answer the specific question asked, in this specific scenario?

Common Traps Table

Full Worked Scenario 1 — Risk Materialising into an Off-Specification

Scenario. A project is in stage 3 of 5. The Project Plan shows the project is on budget and on time. During the stage, a key supplier announces a four-week delay on a component that is critical to the next work package. The Team Manager reports the delay via a Checkpoint Report. The Project Manager assesses the impact and forecasts that the stage will breach its time tolerance by two weeks.

Question. Identify every practice, process, role, and management product involved in the correct PRINCE2 response, in order.

Worked answer.

1. Risk practice — the delay was a risk that has now materialised. The PM records the materialised risk and its impact in the Project Log (the consolidated log that now holds risk entries).
2. Issues practice — because the component will not meet its specification, the team raises an off-specification (a type of issue). The off-specification is captured in the Project Log and assessed through the Issue and Change management approach.
3. Progress practice — the PM forecasts a stage tolerance breach. Under manage by exception, the PM must notify the board.
4. Controlling a Stage process — the PM raises an Exception Report (a report) to the Project Board, describing the problem, the impact, and options.
5. Directing a Project process — the Project Board reviews the Exception Report and gives exception direction (a decision). The board may choose to change the stage, reduce scope, or request an Exception Plan.
6. Business Case practice — the four-week delay may affect the project's continued justification. The board re-checks the Business Case (a baseline, maintained in the PID) before deciding.
7. Managing a Stage Boundary process — if the board requests an Exception Plan, the PM prepares one and presents it for approval, alongside an updated Project Plan and Business Case.

Notice the chain: a single event touches four practices (Risk, Issues, Progress, Business Case), three processes (Controlling a Stage, Directing a Project, Managing a Stage Boundary), three roles (Team Manager, Project Manager, Project Board), and four management products (Project Log, Checkpoint Report, Exception Report, Business Case / Project Plan). This is exactly the kind of integration the Practitioner exam tests.

Full Worked Scenario 2 — Tailoring an Agile Project at Stage End

Scenario. A project is delivering a customer-facing app using agile delivery inside PRINCE2 governance. The team works in two-week iterations. Stage 2 contains six iterations and is nearing its end. The Project Manager has been sending Highlight Reports every iteration. The Project Board asks whether a formal End Stage Report is still needed given the frequent reporting, and whether the next Stage Plan can simply be the iteration backlog.

Question. Is the board's suggestion valid tailoring? Evaluate using PRINCE2 7 tailoring rules.

Worked answer.

• The suggestion to drop the End Stage Report is invalid. The End Stage Report's purpose is to pack up the stage's results, update the Business Case and Project Plan, and give the board the information it needs to authorise the next stage. Frequent Highlight Reports do not replace that consolidated re-justification point. Valid tailoring would make the End Stage Report lighter (for example, a one-page summary referencing iteration outcomes) but would not remove it.
• The suggestion to use the iteration backlog as the Stage Plan is partly valid but incomplete. A Stage Plan must show what will be delivered, when, at what cost, and with what risks — and it must set tolerances. An iteration backlog shows what the team intends to build, but it does not by itself carry tolerances or the full plan content. Valid tailoring would express the Stage Plan as a release plan containing the backlog plus tolerances, dependencies, and a budget — not replace it with a bare backlog.
• The Highlight Reports every iteration are valid tailoring — more frequent reporting is a proportionate scaling of the Highlight Report for an agile context.

The principle: agile tailoring changes form and frequency, not purpose. Stage control, Business Case re-justification, and tolerance setting all still happen — they just wear agile clothes.

Final Pre-Exam Checklist

• Manual tabbed by practice, process, and management product.
• v7 numbers memorised: 70 marks, 150 minutes, 42 to pass (60%).
• v6 trap vocabulary mapped (themes→practices, Change→Issues, 68/55%→70/60%, 26→15 products).
• Project Log consolidation memorised (daily log, lessons, issues, quality, risks).
• Product→created in→owned by map reviewed.
• Because clause discipline: evaluate justification before Yes/No.
• Time buffer: aim to finish with 10–15 minutes for review.
• At least two full integrative scenarios practised end to end.

If you can chain practices, processes, roles, and management products through a scenario the way the two worked examples above do, you are ready for the integrative items that carry the most marks. Good luck.