7 Processes

PRINCE2's 7 Processes describe a sequence of activities that a project must undertake from inception to closure. Each process has a defined set of recommended activities, with inputs and outputs that flow between processes. The processes are not always sequential — for example, Managing a Stage Boundary can trigger Directing a Project, which in turn authorises the next stage controlled by Controlling a Stage.

The Project Board and Project Manager have distinct but complementary roles across the processes. The Project Board directs and makes key decisions; the Project Manager manages day-to-day delivery.

Key Points

• Starting Up a Project (SU): Pre-project activities — is this worth initiating?
• Directing a Project (DP): Project Board activities throughout — governance and decisions
• Initiating a Project (IP): Establishing the PID and firm foundations
• Controlling a Stage (CS): Day-to-day management by the Project Manager
• Managing Product Delivery (MPD): Team Manager's process for delivering work packages
• Managing a Stage Boundary (SB): End-of-stage activities and planning for next stage
• Closing a Project (CP): Formal project closure and handover
• DP runs throughout — Project Board is always available to direct

Key Terms & Definitions

Work Package

A set of information about one or more required products given by a Project Manager to a Team Manager.

Stage Plan

A plan for the current management stage, used for day-to-day control.

Highlight Report

A time-driven report from the Project Manager to the Project Board on stage progress.

End Stage Report

A report that reviews stage performance, the project status, and options for the future of the project.

End Project Report

A report confirming handover of all products and identifying any outstanding risks or issues.

Benefits Management Approach

A document defining how and when benefits will be measured, who is responsible, and what processes are needed.