Seven PRINCE2 Processes: What each process does and the outputs it produces

# Overview PRINCE2 (PRojects IN Controlled Environments) is a process-driven project management approach that divides work into stages. Each of the seven PRINCE2 processes defines specific inputs, activities, and outputs so project roles and decision points are explicit.

# The seven processes, at a glance

• Starting up a Project (SU): a pre-project check that the project is worth doing. Input: Project Mandate. Outputs include a project brief, an outline business case, and an Initiation Stage Plan. Activities include appointing the Project Board and Project Manager and forming the project management team.

• Initiating a Project (IP): detailed planning to confirm the business case and set controls. Main output: Project Initiation Document (PID). Activities include creating Risk, Quality, Configuration, and Communication Management Strategies, confirming the business case, and establishing project controls and files.

• Controlling a Stage (CS): day-to-day monitoring and control performed by the Project Manager. It governs how work packages are authorized and received. Activities include authorizing work packages, assessing progress, capturing and examining issues, reviewing stage status, reporting highlights, taking corrective action, escalating issues, and receiving completed work packages.

• Managing Stage Boundaries (SB): provides the Project Board with information and decision points at the end of each stage. Activities include planning the next stage, updating the project plan, risk register, and business case, reporting stage end, producing exception plans if tolerances were exceeded, and seeking approval to start the next stage.

• Closing a Project (CP): actions required to end the project. Activities include decommissioning the project, identifying follow-on actions, checking that PID objectives were met, and updating the Issue Register.

# How the processes fit together PRINCE2 uses these processes in sequence and iteratively across stages. Starting up a Project produces the short set of outputs needed to decide whether to initiate. Initiating a Project produces the PID and management strategies used by the Project Manager to run Controlling a Stage and Managing Product Delivery. Managing Stage Boundaries creates the decision point for the Project Board in Directing a Project. Closing a Project formalizes project completion activities.

# Practical implications for teams

• Document-driven checks: specific documents (Project Mandate, PID, plans, registers) serve as inputs and outputs to ensure continuity between stages.
• Explicit exception handling: if a stage exceeds tolerance, an exception plan and stage boundary procedures guide next steps.

# Bottom line