4.3 Scenario Practice for 7 PRINCE2 Processes

4.3 Reading a Process Scenario

Process questions almost always embed three cues. First, who is acting — the Project Board (DP), the Project Manager (SU, IP, CS, SB, CP), or the Team Manager (MP). Second, where in the lifecycle the project is — pre-project, initiation, a delivery stage, a stage boundary, or closure. Third, what just happened — the trigger, such as a mandate arriving, a Work Package completing, a tolerance forecast to be exceeded, or a stage nearing its end.

Use a four-step read for every process scenario:

1. Name the role in the stem.
2. Locate the lifecycle position.
3. Identify the trigger that has just arrived.
4. Choose the process and management product that the trigger demands.

Worked example: tolerance under threat

A Project Manager forecasts that the current stage will finish three weeks late, breaching the agreed stage time tolerance. What happens? The role is the Project Manager, the position is mid-delivery-stage, and the trigger is a forecast tolerance breach. Within Controlling a Stage, the Project Manager first tries take corrective action; if that cannot bring the stage back inside tolerance, the activity becomes escalate issues and risks, producing an Exception Report to the Project Board.

The board, acting in Directing a Project, may then request an Exception Plan, which the Project Manager prepares in Managing a Stage Boundary.

More Worked Patterns

Pattern: a completed Work Package returns. A Team Manager finishes building a product and quality-checks it. The Team Manager, in Managing Product Delivery, delivers the Work Package. The Project Manager, in Controlling a Stage, receives a completed Work Package and updates records. Do not confuse the two: building and quality-checking is MP; receiving back and reviewing is CS.

Pattern: the board wants regular updates. The board has asked to be kept informed without attending meetings. The Project Manager satisfies this through the report highlights activity in CS, sending a Highlight Report at the frequency the board set in the Communication Management Approach. The Team Manager equivalent — reporting up to the Project Manager — is the Checkpoint Report in MP.

Pattern: premature closure. A Business Case collapses mid-project and the board decides to stop. The project does not simply halt; the board directs the Project Manager to invoke Closing a Project so products are accounted for, lessons captured, and an End Project Report produced. Orderly closure is a process, not an absence of process.

Distinguishing the Two Levels of Exception

A subtle but frequently tested area is the difference between a Work Package exception and a stage exception. They are escalated through different routes.

If a Team Manager forecasts that a Work Package's agreed tolerances will be exceeded, the escalation is team to Project Manager: the Team Manager raises an issue to the Project Manager within Managing Product Delivery, and the Project Manager handles it within Controlling a Stage (capture and examine issues and risks, then take corrective action). This stays inside the stage and does not automatically reach the board.

If the stage tolerance is forecast to be exceeded, the Project Manager cannot resolve it within delegated authority. The escalation now goes Project Manager to Project Board via an Exception Report (CS), and the board responds in Directing a Project. So the same word — 'exception' — points to two different processes depending on whose tolerance is at risk.

A closure-flavoured scenario

Consider: the final delivery stage is almost complete and all products have been accepted by the users. The Project Manager is not in Managing a Stage Boundary, because there is no next stage to plan. The correct process is Closing a Project — confirm acceptance, hand over products to operations, evaluate the project, and produce the End Project Report for the board to authorize closure in DP. If the same scenario were one stage earlier, SB would be correct instead. The discriminating cue is always is there a next stage?

Reading speed tip

Under exam time pressure, lock onto the verb and the role in the first sentence. 'A Team Manager...' almost always means MP. 'The Project Board...' almost always means DP. 'The Project Manager forecasts a tolerance breach...' almost always means CS escalation. Training this reflex turns four-option scenarios into one-step eliminations.

Finally, watch for scenarios that describe a handoff between processes rather than a single process. A stem may describe the Project Manager authorizing a Work Package and the team beginning work — this spans the CS activity authorize a Work Package and the MP activity accept a Work Package. When two processes are clearly in play, the question is usually asking which role acts next, so pick the answer that names the receiving role and its activity, not the one that has already happened.