4.5 Practice Drills and Readiness Markers
Key Takeaways
- Readiness means you can recite the SU → DP → IP → CS/MP → SB → CP sequence and the trigger and product for each process from memory.
- Drill the trigger-to-product chain: mandate → Project Brief → PID → Work Packages → End Stage Report → End Project Report.
- Drill role ownership: board acts only in DP; Team Manager only in MP; everything else is Project Manager.
- Drill the report directions: Checkpoint up to PM, Highlight up to board, Exception up to board.
- A process is mastered when you can place any scenario into the right process without seeing the process named.
4.5 Drills That Build Process Fluency
The processes are the most diagram-friendly part of PRINCE2, so drill them visually and by recall, not by rereading. Four drills cover almost everything Foundation tests.
Drill 1 — Sequence recall. From a blank page, write SU → DP → IP → CS / MP → SB → CP and annotate which run once (SU, IP, CP), which repeats per stage (CS, MP, SB), and which spans the whole project (DP). If you cannot do this cold, you are not ready.
Drill 2 — Trigger-to-product chain. Recite, in order, the management product each trigger creates:
| Trigger | Process | Headline product |
|---|---|---|
| Project mandate | SU | Project Brief, outline Business Case |
| Authority to initiate | IP | PID, detailed Business Case, Project Plan |
| Authority to deliver | CS | Work Packages, Highlight Reports |
| Work Package authorized | MP | Checkpoint Reports, specialist products |
| Stage nearing end | SB | End Stage Report, next Stage Plan |
| Tolerance forecast breach | SB | Exception Plan |
| Final stage | CP | End Project Report |
Drill 3 — Role ownership. Sort a shuffled list of activities by owner: Project Board (authorize initiation, authorize the project, authorize a stage, give ad hoc direction, authorize closure), Team Manager (accept, execute, deliver a Work Package), Project Manager (everything else).
Readiness Markers and Self-Check
Drill 4 — Blind scenario placement. Take mixed scenario stems with the process names stripped out and place each into the correct process and activity. This is the truest test, because the real exam rarely names the process for you.
Use these readiness markers to decide whether the processes domain is exam-ready:
| Marker | What mastery looks like |
|---|---|
| Sequence recall | Write SU → DP → IP → CS/MP → SB → CP and label run-once vs repeating from memory. |
| Trigger mapping | Name the product each trigger produces without notes. |
| Role ownership | Assign any activity to board, Project Manager, or Team Manager correctly. |
| Report direction | State who sends Checkpoint, Highlight, Exception, End Stage, and End Project reports and to whom. |
| Scenario placement | Drop an unlabeled scenario into the right process and activity. |
| Retention | Repeat a mixed set after a one-day break with stable accuracy. |
Final self-check questions
Ask yourself: Which processes run exactly once? (SU, IP, CP.) Which process has no products of its own? (DP.) Which process is owned by the Team Manager? (MP.) What does the board do when an Exception Report arrives? (Decides in DP; may request an Exception Plan produced via SB.) Where is the PID created? (IP.) If any answer is shaky, return to Drill 2 or 3 before sitting the exam. The processes domain rewards crisp recall of triggers, products, and role ownership more than any other part of the syllabus.
A Spaced-Repetition Plan for the Processes
Because the processes are recall-heavy, spaced repetition beats massed rereading. A workable three-pass plan:
- Pass one (build the map). Draw the full process model once with every trigger arrow and management product labelled. Say each purpose aloud in one sentence — for example, 'Starting up a Project confirms the project is worthwhile.' This converts the diagram from something you recognize into something you can reproduce.
- Pass two (drill the joins). Focus on the handoffs, where exam traps live: SU→DP, DP→IP, IP→DP→CS, CS↔MP, CS→SB→DP, and CP→DP. For each join, name the product that crosses it. Most wrong answers misplace a product at a join, so over-practising joins yields outsized score gains.
- Pass three (blind mixed sets). Answer mixed, unlabelled scenario questions under time, then log every miss by the cue you missed — wrong role, wrong lifecycle position, wrong report direction, or wrong product.
Two-minute daily warm-up
Keep a recall card with five prompts and answer them from memory each study day:
- Name the seven processes in order. (SU, DP, IP, CS, MP, SB, CP.)
- Which process owns the PID? (IP.)
- Which report goes Team Manager to Project Manager? (Checkpoint.)
- Which process plans the next stage? (SB.)
- What confirms the project product is accepted? (Closure, recorded in the End Project Report from CP.)
When all five come instantly and you can place unlabelled scenarios correctly after a day's gap, the processes domain is exam-ready. Because this domain is so mechanical, it is also the domain where a few hours of disciplined drilling produces the most certain marks on test day — treat it as your highest-return revision target.
One last integration drill
To confirm you can integrate processes with the rest of the syllabus, narrate a full project in under a minute: a mandate arrives and SU confirms it is worthwhile; the board authorizes initiation in DP; IP builds the PID and management approaches; the board authorizes the project in DP; CS runs the first stage while MP delivers products and reports via Checkpoint Reports; SB closes the stage with an End Stage Report and plans the next; the board authorizes each stage in DP; and finally CP confirms acceptance and produces the End Project Report for the board to authorize closure.
If you can tell that story cleanly, naming the trigger and product at every join, you have mastered the processes domain.
Which three processes run exactly once during a PRINCE2 project?
A Checkpoint Report and a Highlight Report differ in their direction of flow. Which pairing is correct?
When the Project Board receives an Exception Report, what is its typical response within the process model?