11.4 Final Review and Exam-Day Strategy
Key Takeaways
- Forty questions in sixty minutes gives 90 seconds each — enough time for a first pass plus a review of flagged items.
- Answer every question: there is no negative marking, so a blank answer and a wrong answer cost the same.
- For list questions, eliminate the statements you know are wrong, then pick the pair that contains neither.
- Read negative questions twice — the word NOT inverts what you are looking for and is the commonest careless error.
- The highest-yield revision is the purpose statements: seven practices, seven processes, eleven roles and the named workshops.
11.4 Final Review and Exam-Day Strategy
Quick summary: 40 questions, 60 minutes, 90 seconds each, 24 to pass. Answer everything — there is no negative marking. Two passes: first for questions you know, second for the flagged remainder.
The highest-yield revision list
If you have one evening left, revise these in this order.
1. Purpose statements — practices
| Practice | Purpose phrase |
|---|---|
| Business case | Judging whether the project is desirable, viable and achievable |
| Organization | Defining the project's responsibilities |
| Plans | Estimating how much work is to be delivered and when |
| Quality | Ensuring the users' requirements and expectations are met |
| Risk | Identifying, assessing and controlling uncertainty |
| Issues | Controlling changes to the project's baseline |
| Progress | Comparing what has been delivered with what was planned; controlling deviations causing an exception |
2. Purpose statements — processes
| Process | Purpose phrase |
|---|---|
| Starting up a project | Is there a viable and worthwhile project? |
| Directing a project | Overall control while delegating day-to-day management |
| Initiating a project | Establishing solid foundations |
| Controlling a stage | Taking care the stage remains within tolerances |
| Managing product delivery | Controlling the link between project manager and team |
| Managing a stage boundary | Ensuring the board can decide on the next steps |
| Closing a project | A fixed point at which acceptance is confirmed |
3. The workshops
| Workshop | Distinctive fact |
|---|---|
| Project canvas workshop | User groups defined and prioritized |
| Project initiation workshop | Vision, objectives, goals; detailed project canvas |
| Project kickoff workshop | Team introduction fosters familiarity and connections |
| Team planning workshop | Team OKRs defined |
| Team retrospective workshop | Team shares key accomplishments of its iteration |
| Release planning workshop | Which features land in which release |
| Progress review workshop | Progress inspected, next steps agreed |
| Project closure workshop | Guidelines for ongoing benefits realization |
| Project retrospective | Project-level lessons for the organization |
| Agile enablement workshop | How agile will be used; critical agile artifacts |
4. Lists to have cold
- Seven performance targets: benefits, cost, time, quality, scope, sustainability, risk
- Five integrated elements: principles, people, practices, processes, project context
- Agile Onion, outside in: processes, practices, principles, values, mindset
- Four Manifesto values: individuals and interactions; working software; customer collaboration; responding to change
- Four named agile approaches: Scrum, Kanban, Lean, Lean Startup
- Three transformation success factors: agile maturity, psychological safety, agile sustainability
- Eleven roles: project executive, chief product owner, senior supplier, project assurance, agile coach, project manager, project support, product owner, team coach, developer, tester
- MoSCoW: Must have, Should have, Could have, Won't have this time
5. Single-fact recalls
- Empowerment — the mindset characteristic promoting autonomy and self-management
- Being agile = mindset; doing agile = processes
- Servant leadership — putting team members' needs above your own
- Persona — identifies the specific benefits a solution delivers to users
- Delegation poker — collaborative method for defining decision-making within teams
- Technical debt — eventual consequence of poor design or development
- Stakeholder — anyone affected by the change initiative
- Project support — reports directly to the project manager
- Chief product owner — aligns project and delivery product backlogs
- Capture issues and risks — the CS activity where uncertainties are logged
- Documenting the plan — the planning activity where the release map is updated
- Product owner — consulted to agree priority when trading or swapping
- AI — analyses historical data and real-time metrics for predictive insights
- Continuous agile development and operations — focused on ensuring the product is deployable
- User surveys and retrospectives — actionable insight during transition to operations
Strategy for the sixty minutes
Pace
Ninety seconds per question. Realistically, most recall questions take 30 to 40 seconds, which banks time for the harder ones.
Two-pass approach:
- First pass (about 35 minutes). Answer everything you know immediately. If a question needs more than about 60 seconds, put down your best guess, flag it, and move on.
- Second pass (about 20 minutes). Return to the flagged questions with the pressure off — and often with a later question having reminded you of something.
- Final check (about 5 minutes). Confirm every question has an answer.
Answer everything
There is no negative marking. A blank costs exactly what a wrong answer costs. Never leave one.
Even a blind guess is worth 25%; an educated guess after eliminating one option is worth 33%, and after eliminating two, 50%.
Handling each question style
Standard. Read the stem, form your answer before reading the options, then find it. This protects you against a plausible distractor reshaping your thinking.
Missing word. Read the whole sentence with each candidate word inserted. These usually test a purpose statement, so the phrases in the tables above are your defence.
List. Four statements, four options each pairing two. The efficient method is elimination: find one statement you are certain is wrong, and cross out both options containing it. That usually leaves two options, and one more judgement decides it. Remember list questions are never negative.
Negative. Read the stem twice. Underline the NOT mentally. The commonest careless error on the whole paper is answering a negative question as though it were positive — you find a true statement, it feels right, and it is exactly wrong. When you hit one, ask "which three are true?" and choose the remaining one.
Distractor patterns to expect
- The right answer for a neighbouring practice. A quality question with an option describing the business case. Ask which practice does this option actually belong to?
- A reversed definition. Being/doing agile is the classic.
- A Version 1 answer. The five targets, the hexagon, "50 questions, 55%".
- A true statement that does not answer the question. Very common. Test it against the stem, not against your general knowledge.
- An absolute. Options containing "always", "never", "removes the need for" are usually wrong, because PRINCE2 Agile is a tailoring framework and tailoring is contextual.
Before the day
- Confirm you are booked on Version 2. Everything in this guide assumes it.
- Test your setup if you are sitting online proctored — camera, microphone, connection, and a clear desk. Have photo ID ready.
- Log in early. Expect identity verification and a room scan before the timer starts.
- Request extra time at booking if the exam language is not your native or working language: 25%, giving 75 minutes. It cannot be requested during the exam.
- Sleep. This is a recall paper, and recall is the cognitive function sleep deprivation damages first.
On the day
You will get a provisional result as soon as you finish. Twenty-four marks is the bar — that is 16 questions you can afford to get wrong. You do not need to know everything, and you should not spend three minutes on a question you cannot crack while four easy marks sit unread at the end of the paper.
With ten minutes remaining, a candidate has six flagged questions and two they have not read. What is the best use of the time?
A list-style question presents four statements and asks which TWO are correct. What is the most efficient approach?
Which option-writing pattern is usually a signal of an incorrect answer in this exam?
You've completed this section
Continue exploring other exams