PRINCE2 processes
The process model
PRINCE2 has seven processes: starting up a project (SU), directing a project (DP), initiating a project (IP), controlling a stage (CS), managing product delivery (MP), managing a stage boundary (SB) and closing a project (CP). DP runs throughout and is the project board's process: it authorises initiation, the project, each stage and closure, and gives ad hoc direction. A project mandate triggers SU; SU produces the project brief, outline business case, project approach, daily log and lessons log; IP produces the PID, the management approaches and the benefits management approach; delivery stages then cycle through CS and MP, with SB at the end of each stage except the final one; CP closes the project.
Products by process
- SU: project brief, outline business case, daily and lessons logs.
- IP: PID, benefits management approach, project controls.
- CS: work packages, checkpoint reports, exception reports, updated stage plan.
- SB: end stage report, next stage plan.
- CP: end project report, lessons report, closure notification.
Traps
Confusing the end stage report (SB) with the end project report (CP); placing exception reports in SB; treating the project mandate as an SU output (it is the pre-project trigger); assuming SB runs at the end of the final stage when CP does; and thinking DP does the day-to-day managing - it directs. MP is used for every work package, not once per stage.
Worked example
'The project board reviews an exception report and approves corrective action.' CS raised the exception and DP authorised the response, so the answer is controlling a stage. Rule of thumb: identify the process by its trigger and the products it creates, not by who does the work.