PRINCE2 Foundation: Principles, Themes, and Processes for Structured Project Management

PRINCE2 principles are the foundation — if a project does not apply all seven, it is not a PRINCE2 project. Continued Business Justification: the project must have a valid reason to continue throughout its life — the Business Case is maintained and reviewed at each stage. Learn from Experience: lessons from previous projects are sought, recorded, and acted upon at all levels. Defined Roles and Responsibilities: the project organisation must be understood, agreed, and clear — every decision has an accountable owner. Manage by Stages: the project is planned, monitored, and controlled one management stage at a time — end-stage reviews give the Project Board a go/no-go decision. Manage by Exception: the Project Board manages at a strategic level; the Project Manager manages day-to-day — exceptions are escalated when tolerances are forecast to be exceeded. Focus on Products: the project's outputs (products) and their quality criteria are defined before work begins. Tailor to Suit the Project Environment: PRINCE2 is adapted to the context — the method must be tailored, not followed rigidly.

Themes are aspects of project management that must be addressed continuously. Business Case: why are we doing this project? Justification must be maintained throughout (not just at the start). Organisation: who is responsible? The project organisation has four key roles: Project Board (accountable for the project — Senior User, Senior Supplier, Executive), Project Manager (day-to-day management), Team Manager (manages specialist teams), Project Assurance (independent quality assurance). Quality: what standard must products meet? The Project Product Description defines the overall output; individual Product Descriptions define quality criteria. Plans: how will we deliver? Three levels: Project Plan (high-level), Stage Plans (detailed for the current stage), Team Plans (optional, for complex specialist work). Risk: what uncertainties could affect the project? Registered in the Risk Register, managed using the PRINCE2 risk management procedure (Identify, Assess, Plan, Implement, Communicate). Change: how are issues and changes controlled? Change control procedure, Issue Register, Change Authority. Progress: where are we against the plan? Tolerances (time, cost, scope, quality, risk, benefit — the six aspects of performance), Highlight Reports, Checkpoint Reports, Exception Reports.

Processes describe the steps taken throughout the project lifecycle. Starting Up a Project (SU): before formal approval — appoint the project management team, create the Project Brief, plan the Initiation Stage. Directing a Project (DP): the Project Board's process — runs throughout — authorise Initiation, each Stage, project closure, and give ad-hoc direction. Initiating a Project (IP): create the Project Initiation Documentation (PID) — the detailed strategy for all themes, including baselines for Business Case, Plan, Risk Register. Managing a Stage Boundary (SB): at the end of each stage — report on stage performance, plan the next stage, update the Business Case and risk register, seek Project Board approval to continue. Controlling a Stage (CS): the Project Manager's process for day-to-day management — authorise work packages, receive Checkpoint Reports, review progress, take corrective actions, escalate exceptions. Managing Product Delivery (MP): Team Managers receive Work Packages, plan and deliver the specialist work, hand back completed Work Packages. Closing a Project (CP): formal close — hand over products, evaluate the project against the original PID, capture lessons, recommend closure to the Project Board.

PRINCE2 defines clear accountability. Project Board: three roles — Executive (accountable for the Business Case and project success — one person only), Senior User (represents users who will use the products), Senior Supplier (represents those who will design, build, and implement the products). The Project Board manages by exception — they do not attend daily meetings. Project Manager: reports to the Project Board, manages day-to-day, responsible for delivering the project to plan within tolerances. Project Assurance: independent — confirms the project is being managed correctly (separate from Project Manager — provides assurance TO the Project Board). Change Authority: can be delegated by the Project Board to approve minor changes. Key management products (documents): Business Case (why), Project Product Description (what we are delivering), Project Initiation Documentation (the how), Risk Register, Issue Register, Quality Register, Lessons Log, Highlight Report (Project Manager to Project Board — periodic), Exception Report (Project Manager to Project Board — when a tolerance is forecast to be exceeded), Checkpoint Report (Team Manager to Project Manager — periodic progress update).