PRINCE2 Foundation Basics Course
Five lessons that build PRINCE2 Foundation skills: principles, themes, processes, roles, management products, risk, change, and project closure.
What you will learn
- Name the seven PRINCE2 principles and the seven themes.
- Distinguish Starting Up a Project from Initiating a Project.
- Explain stage control, product delivery, and stage boundaries.
- Match project roles and management products to their purposes.
- Apply risk, change, progress, and closure concepts in exam scenarios.
Before you start
- Basic project management vocabulary.
- Familiarity with project teams and deliverables.
- About 75 minutes of study plus regular practice.
Lesson 1 PRINCE2 Principles and Themes Overview
PRINCE2 is a process-based method for managing projects. It is built on seven principles: continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to suit the project environment. The method also uses seven themes: business case, organization, quality, plans, risk, change, and progress. The principles must always be present, while themes and processes are tailored to the project. Start by learning the principle names and what each theme controls, because the Foundation exam tests these terms directly.
Principles vs themes: principles are always applied, while themes are tailored to the project. Use this test in exams: if a statement removes a principle, it is wrong; if it adapts a theme or process, it is usually right.
Example
Manage by exception means the project board acts mainly when tolerances are exceeded. The business case theme records why the project is worth doing.
Worked example: A small project simplifies the risk management approach.
This tailors the risk theme and is allowed; it does not remove the principle of manage by exception.
Lesson 2 Starting Up and Initiating a Project
Starting Up a Project prepares the project brief, outline business case, and the first stage plan. It also captures lessons and selects the project approach. Initiating a Project then produces the project initiation documentation, management strategies, registers, and the project plan. The project board uses the PID to decide whether to authorize the project. Learn which activities belong to start-up versus initiation: start-up prepares the brief, while initiation refines plans and creates the full management controls.
Startup vs initiation: Starting Up prepares the project brief and approach; Initiating produces the PID, strategies, and registers. Remember that the project board authorizes initiation first, then authorizes the project after reviewing the PID.
Example
Start-up produces the project brief; initiation produces the PID. The project board authorizes the project only after reviewing the PID.
Worked example: The project brief is complete but the PID is not.
The project is between Starting Up and Initiating, so the next step is to authorize initiation.
Lesson 3 Managing Stages and Product Delivery
Projects are managed by stages. Controlling a Stage authorizes work packages, monitors progress, reviews issues and risks, and reports highlights. Managing Product Delivery covers the team manager side: accepting work packages, doing the work, and delivering completed products. Managing a Stage Boundary reviews the current stage, updates the business case and registers, plans the next stage, and can request an exception plan when tolerances are at risk. Understanding who does what in each process is a common PRINCE2 exam topic.
Who does what: the Project Manager authorizes work packages and monitors the stage; the Team Manager accepts the work package, does the work, and delivers the completed products. Issue and risk reviews happen continuously in Controlling a Stage.
Example
A checkpoint report informs the project manager about work package progress; a highlight report updates the project board.
Worked example: A team manager finishes a product.
They deliver it to the Project Manager, who checks it against the work package and quality expectations before accepting it.
Lesson 4 Roles and Management Products
PRINCE2 defines clear roles: the Executive owns the business case, the Senior User represents users, and the Senior Supplier represents suppliers. The Project Manager runs the day-to-day work, while the Team Manager delivers work packages. Project Assurance checks progress independently, and Project Support handles administration. Management products include the business case, PID, risk register, issue register, quality register, lessons log, work packages, highlight reports, end stage reports, and exception plans. Match each product to its purpose and you will answer many Foundation questions correctly.
Role-to-product matching: the Executive owns the business case, the Project Manager owns the project plan and registers, and the Project Board approves key documents. Match each management product to its purpose before memorizing lists.
Example
The Executive owns the business case; the Team Manager delivers a work package; Project Assurance provides independent checks.
Worked example: Who approves the project plan?
The Project Board reviews and approves it, while the Project Manager prepares and updates it.
Lesson 5 Risk, Change, Progress and Closure
The risk theme manages threats and opportunities with responses such as avoid, reduce, fallback, transfer, share, and accept for threats, plus exploit and enhance for opportunities. The change theme controls requests for change, off-specifications, and problems through the issue register and change authority. The progress theme compares actuals with tolerances and uses checkpoint, highlight, and end stage reports. Closing a Project verifies acceptance, reviews benefits, captures lessons, and recommends closure. On the exam, read each scenario, identify the process or product, and eliminate options that belong to another theme.
Theme distinction: risks are uncertain future events; issues are current problems, change requests, or off-specifications. During closure, verify acceptance, evaluate benefits, capture lessons, and recommend closure to the Project Board.
Example
An exception plan replaces the current plan when tolerances are forecast to be breached; Closing a Project recommends closure after acceptance.
Worked example: A vendor may be late, but delivery is still on track.
This is a risk to record and manage; if the delay actually happens, it becomes an issue in the issue register.