PRINCE2 Foundation (v7) Syllabus — Learning Objectives by Learning Outcome

Use this syllabus as your coverage checklist. Drill immediately after each learning outcome section.

What’s covered

• Learning Outcome 1: Key concepts relating to projects and PRINCE2 (3%)
• Learning Outcome 2: PRINCE2 principles (8%)
• Learning Outcome 3: People in successful projects (14%)
• Learning Outcome 4: PRINCE2 practices (60%)
• Learning Outcome 5: PRINCE2 processes (15%)

Learning Outcome 1: Key concepts relating to projects and PRINCE2 (3%)

Projects, context, and PRINCE2 basics

• Define a project and distinguish projects from ongoing operations or business-as-usual work.
• Explain what PRINCE2 is and how it provides a structured, adaptable method for managing projects.
• Distinguish between outputs, outcomes, benefits, and dis-benefits and relate them to business objectives.
• Explain how project context (organizational, commercial, delivery approach, sustainability) influences how PRINCE2 is applied.
• Identify the PRINCE2 performance aspects (time, cost, scope, quality, risk, benefits) and explain how they are controlled.
• Distinguish management products from specialist products and explain why PRINCE2 focuses on products.
• Explain why PRINCE2 uses management stages and how stage boundaries support governance and decision making.

Learning Outcome 2: PRINCE2 principles (8%)

Principles: continued justification and learning

• Explain the principle of continued business justification and how it is maintained throughout a project.
• Identify when business justification should be checked and what actions are appropriate when it is no longer valid.
• Explain the principle of learn from experience and how lessons are captured and applied during a project.
• Distinguish between capturing lessons during delivery and reporting lessons at stage end or project end.
• Apply the learning principle to decide how recurring issues should influence the approach in the next stage.
• Recognize behaviors that violate continued justification or learning and choose corrections consistent with PRINCE2.

Principles: roles, stages, and exception

• Explain the principle of defined roles and responsibilities and the need to represent business, user, and supplier interests.
• Distinguish key responsibilities of the project board, project manager, and team manager in PRINCE2 governance.
• Explain the principle of manage by stages and why planning and control are organized around management stages.
• Explain the principle of manage by exception and how tolerances enable delegation and escalation.
• Distinguish project plan, stage plan, and exception plan and when each is used.
• Given a forecast outside tolerance, decide the appropriate escalation action and who should be informed.

Principles: product focus and tailoring

• Explain the principle of focus on products and the role of product descriptions and acceptance criteria.
• Apply product-based planning concepts to identify products, quality criteria, and dependencies at a high level.
• Explain the principle of tailor to suit the project and what aspects of PRINCE2 can be tailored.
• Identify factors that influence tailoring decisions such as risk, governance requirements, delivery approach, and organizational context.
• Recognize when tailoring undermines PRINCE2 (for example, removing essential controls or role clarity) and choose corrections.
• Choose appropriate tailoring decisions for a small/low-risk project versus a large/high-risk project.

Learning Outcome 3: People in successful projects (14%)

Stakeholders, communication, and co-creation

• Identify key stakeholder groups and describe their typical information needs in a PRINCE2 project.
• Explain co-creation and how stakeholders contribute to shaping products and outcomes during a project.
• Explain the purpose of a communication management approach and what it should cover (audiences, methods, frequency, responsibilities).
• Choose appropriate communication methods for distributed teams while maintaining transparency and control.
• Recognize stakeholder conflict and choose an engagement or facilitation action consistent with PRINCE2 roles.
• Identify when stakeholder concerns should be escalated to the project board and what information to provide.
• Explain how user feedback supports product acceptance and benefits realization.
• Decide what stakeholder information should be reviewed at stage boundaries to support continued justification.

Leadership and teamwork

• Distinguish leadership behaviors from management activities in the context of a PRINCE2 project.
• Identify behaviors that build effective teamwork and trust across business, user, and supplier interests.
• Recognize common sources of team conflict and choose responses that respect defined responsibilities.
• Explain the purpose of role descriptions and how they reduce ambiguity and improve collaboration.
• Distinguish between capability and competency and explain how each affects staffing and performance.
• Choose actions a project manager can take to support motivation and accountability within governance constraints.
• Recognize when responsibilities are unclear or not accepted and decide how to clarify or resolve the gap.
• Explain how effective decision making supports progress and reduces delays in a PRINCE2 project.

Change management and organizational boundaries

• Explain how change management supports adoption of project outputs and realization of benefits.
• Identify techniques for managing resistance to change and encouraging adoption of new ways of working.
• Explain what it means to lead across organizational boundaries and how to work with suppliers or partners.
• Distinguish governance responsibilities from delivery responsibilities when multiple organizations are involved.
• Choose actions to clarify decision rights and approval paths in a multi-organization project.
• Recognize how commercial arrangements can influence behavior, incentives, and project risks.
• Explain how sustainability considerations can influence stakeholder expectations and project decisions.
• Decide how to handle sensitive communications that require careful timing, audiences, or approvals.

Roles and responsibilities (people-focused)

• Explain the purpose of having a single point of accountability for the business case (Executive role).
• Distinguish Senior User and Senior Supplier responsibilities and how they represent different interests.
• Explain how project assurance supports governance by independently checking that the project remains viable and compliant.
• Explain how work packages support collaboration between the project manager and team manager.
• Recognize when someone is acting outside their accountability and choose a correction that restores role clarity.
• Explain the purpose of a change authority and how change approval can be delegated within tolerances.
• Identify how project support can assist with controls and records without taking accountability away from governance roles.
• Describe what effective project board decision making looks like and what inputs support those decisions.

Learning Outcome 4: PRINCE2 practices (60%)

Business Case practice: justification concepts

• Explain how business justification is maintained throughout the project using the Business Case.
• Distinguish outputs, outcomes, benefits, dis-benefits, and business objectives in the context of a Business Case.
• Identify typical components of a Business Case (reasons, options, benefits, costs, timescales, and risks).
• Explain the Executive accountability for ensuring continued business justification.
• Explain how benefits should be measurable and traced to products and outcomes.
• Identify when the Business Case should be reviewed (for example, at stage boundaries, exceptions, and closure).
• Explain how risk and uncertainty influence option selection and business case viability.
• Distinguish between initial investment appraisal and ongoing Business Case maintenance during delivery.
• Recognize scenarios where a project should be stopped due to loss of justification and choose appropriate actions.
• Choose actions to keep the Business Case current when key assumptions or forecasts change.

Business Case practice: management products and technique

• Identify which management products support the Business Case (for example, Project Brief, Business Case, PID, and Benefits Management Approach).
• Explain the purpose of the Benefits Management Approach and what information it should include.
• Distinguish expected benefits during the project from benefits realized after project closure.
• Explain how plans and product descriptions should trace to benefits and business objectives.
• Describe the business case management technique and how it is used to develop, check, maintain, and confirm justification.
• Decide what information is needed to update the Business Case after a significant issue or change request.
• Explain how sustainability considerations can be represented in justification, constraints, and tolerances.
• Distinguish the Business Case from the Project Brief in terms of timing, purpose, and content.
• Identify who approves the Business Case at key decision points and what evidence supports approval.
• Choose how to measure whether the project remains worth doing when forecasts or expected benefits change.

Organizing practice: governance structure and roles

• Explain the purpose of the organizing practice in defining accountability and decision making.
• Identify the three project interests (business, user, supplier) and why each must be represented.
• Describe responsibilities of the Project Board and its members (Executive, Senior User, Senior Supplier).
• Distinguish project assurance from project support and explain the value of each.
• Explain the roles of project manager and team manager and how they collaborate through work packages.
• Identify the purpose of a change authority and how change approval can be delegated.
• Distinguish user/customer perspectives from supplier/provider perspectives in governance decisions.
• Explain how user representation supports acceptance of products and quality expectations.
• Choose an appropriate governance structure for a small/low-risk project versus a large/high-risk project.
• Recognize role conflicts or gaps and decide how to clarify responsibilities and escalation paths.

Organizing practice: team structure, commercial, and technique

• Explain how the delivery approach (in-house, outsourced, agile/hybrid) influences team structure and responsibilities.
• Identify what role descriptions should contain and how they support effective working relationships.
• Explain the purpose of a change management approach and what it should cover (transition, adoption, and readiness to realize benefits).
• Distinguish functional, matrix, and projectized organizational structures and their impact on authority and escalation.
• Explain how work packages enable delegation to delivery teams while maintaining control and accountability.
• Distinguish team plans from stage plans and identify what information belongs in each.
• Describe an organizing technique to design the project management team structure and interfaces.
• Decide how to address missing stakeholder representation on the Project Board and the risks it creates.
• Explain how to manage governance across organizational boundaries when suppliers or partners are involved.
• Choose actions to ensure assurance activities remain independent and effective.

Plans practice: plan types, products, and horizons

• Explain the purpose of the plans practice and how planning supports delivery and control.
• Distinguish project plan, stage plan, team plan, and exception plan and when each is created or updated.
• Distinguish management stages from technical stages and explain why PRINCE2 uses management stages for control.
• Define product-based planning at a high level and explain how it supports a focus on products.
• Identify key elements of a plan such as products, activities, resources, estimates, dependencies, and tolerances.
• Distinguish product scope from activities and explain how each is represented in planning.
• Explain what a Product Description contains including composition, quality criteria, and method of acceptance.
• Explain how plans link to the Business Case and support benefits realization.
• Decide what level of planning detail is appropriate for near-term versus long-term work (rolling wave planning).
• Identify who approves plans and how plan approval supports governance decisions.

Plans practice: scheduling, tolerances, and controls

• Explain how dependencies are identified and used to sequence activities to deliver products.
• Distinguish estimating from forecasting and explain how each is used in PRINCE2 planning and control.
• Explain how tolerances are set in plans and how they are monitored during delivery.
• Decide when an exception plan is required and what triggers the need for it.
• Identify what should be included in a Work Package Description and how it supports progress control.
• Explain how sustainability considerations can affect planning decisions (constraints, resources, and tolerances).
• Choose planning techniques appropriate to the delivery approach while maintaining PRINCE2 governance and controls.
• Interpret a scenario to decide whether a deviation is within tolerance or requires escalation.
• Explain how quality activities are planned and integrated into schedules and work packages.
• Decide how to update plans and baselines when scope changes while maintaining control and traceability.

Quality practice: concepts, expectations, and planning

• Explain the purpose of the quality practice in ensuring products are fit for purpose.
• Distinguish quality, scope, and acceptance and how they relate in PRINCE2.
• Define user quality expectations and acceptance criteria and explain how they are agreed.
• Distinguish requirements, quality criteria, quality tolerances, and acceptance criteria.
• Explain the role of Product Descriptions in defining and communicating quality.
• Identify what a quality management approach should cover (standards, methods, responsibilities, and records).
• Distinguish quality planning, quality control, and quality assurance in the context of PRINCE2.
• Decide how to handle conflicting quality expectations between user and supplier interests.
• Recognize why reducing quality to meet time or cost is risky and what governance actions are appropriate.
• Choose actions to ensure quality criteria are measurable and evidence of acceptance can be produced.

Quality practice: control, registers, and technique

• Identify management products that support quality such as Product Descriptions, Quality Register, and Product Register.
• Explain the purpose of the Quality Register and what it should record.
• Distinguish the Product Register from other tracking records and explain how it supports transparency of product status.
• Describe the quality review technique and the main roles and steps involved.
• Decide when to use quality reviews versus testing and how evidence is captured and recorded.
• Recognize product defects or nonconformance and decide how they should be recorded and addressed through PRINCE2 controls.
• Explain how product acceptance is confirmed and who is accountable for acceptance decisions.
• Choose actions to ensure quality evidence is available to support stage-end decisions and continued justification.
• Interpret a scenario to select the most appropriate quality activity or control to apply.
• Explain how tailoring affects quality controls while maintaining required standards and user expectations.

Risk practice: concepts, appetite, and roles

• Explain the purpose of the risk practice in managing threats and opportunities.
• Define risk, threat, and opportunity and distinguish risks from issues.
• Explain risk appetite and risk tolerance and how they influence project decisions.
• Describe risk cause, event, and effect and write a clear risk statement.
• Distinguish risk owner and risk actionee responsibilities.
• Identify typical risk responses for threats and for opportunities and when each is appropriate.
• Explain the concept of a risk budget and how it supports planned risk responses.
• Recognize common decision biases in risk assessment and choose ways to reduce their impact.
• Choose a qualitative risk assessment approach appropriate to the project context and decision needs.
• Explain how sustainability and commercial constraints can change risk exposure or response choices.

Risk practice: procedure, register, and control

• Identify what a risk management approach should contain including roles, scales, timing, reporting, and thresholds.
• Explain the purpose of the Risk Register and what information it captures for each risk.
• Describe the main steps of a risk management procedure (identify, assess, plan, implement, and communicate).
• Decide when risks should be escalated based on tolerances and decision authority.
• Distinguish proactive risk management from reactive issue management and explain why both are needed.
• Choose how to monitor and report risk status throughout stages and to the Project Board.
• Interpret risk information to decide whether planned responses remain adequate as conditions change.
• Decide how risk management is integrated into stage planning and work packages.
• Explain how data and evidence can improve risk decisions and reduce uncertainty over time.
• Recognize when a response creates secondary risks and decide how to record and manage them.

Issues practice: concepts, baselines, and types

• Explain the purpose of the issues practice in controlling change and handling problems or concerns.
• Distinguish an issue from a risk and explain when a risk becomes an issue.
• Identify types of issues such as request for change, off-specification, problem/concern, and business opportunity.
• Explain what a baseline is and which management products commonly form baselines in PRINCE2.
• Distinguish change control from planning updates and explain how baselines support control.
• Explain the purpose of a change budget or issue tolerance in supporting delegated change authority.
• Recognize when an issue impacts continued business justification and requires escalation.
• Choose the correct initial classification for an issue based on a scenario.
• Explain how configuration and quality records support change control decisions.
• Identify information needed to assess issue impact on time, cost, scope, quality, risk, and benefits.

Issues practice: procedure, registers, and authority

• Identify what an issue management approach should contain including roles, procedures, authority, and records.
• Explain the purpose of the Issue Register and what it should record.
• Explain the purpose of an Issue Report and when it should be produced.
• Describe the issue and change control procedure from capture through decision and implementation.
• Decide who should approve different types of changes (Project Board, change authority, or project manager) based on authority and tolerances.
• Recognize when an exception situation requires an exception plan rather than a simple change approval.
• Choose actions to ensure approved changes are reflected in plans and baselines with appropriate traceability.
• Explain how product defects and off-specifications are handled through the issue process.
• Decide how to prioritize and schedule approved changes without undermining the stage plan or tolerances.
• Recognize how lessons from issues can be used to improve controls and prevent recurrence.

Progress practice: tolerances, controls, and reporting

• Explain the purpose of the progress practice in monitoring and controlling performance.
• Define tolerance and explain how tolerances enable manage by exception.
• Distinguish time-driven controls from event-driven controls and when each is appropriate.
• Identify control points (management stages and work packages) and explain how they support governance.
• Explain the purpose of a Highlight Report and what information it should provide.
• Explain the purpose of a Checkpoint Report and when it is used between the project manager and team manager.
• Explain the purpose of an End Stage Report and how it supports decisions to continue or change direction.
• Explain the purpose of an Exception Report and when it is produced.
• Given an information need, choose the management product that best provides evidence of progress or status.

Progress practice: forecasting, lessons, and escalation

• Distinguish progress measurement from forecasting and explain why forecasts drive escalation decisions.
• Decide what to do when a forecast indicates tolerances will be exceeded, including escalation and planning responses.
• Explain how lessons are captured during the project and reported at stage end and project end.
• Identify what should be included in an End Project Report and when it is produced.
• Explain how product status information and registers support transparency and governance.
• Recognize when controls are too heavy or too light and choose appropriate tailoring to maintain effective governance.
• Explain the purpose of a sustainability management approach and how it supports informed decisions and tradeoffs throughout the project.
• Decide how to keep progress information reliable and avoid gaming or misleading metrics.
• Explain how progress information supports continued business justification at stage boundaries.

Learning Outcome 5: PRINCE2 processes (15%)

Starting up a Project (SU)

• State the purpose of Starting up a Project and when it is performed in the PRINCE2 lifecycle.
• Identify the key objectives and typical outcomes of Starting up a Project (including appointing roles and preparing the Project Brief).
• Distinguish the project mandate from the Project Brief and explain how each is used to start a project.
• Identify which roles are primarily responsible for Starting up a Project activities and decisions.
• Identify the management products created or updated during Starting up a Project and why they matter.

Directing a Project (DP)

• State the purpose of Directing a Project and the Project Board accountability for providing direction.
• Identify the key decisions in Directing a Project (authorize initiation, authorize project, authorize stage/exception plans, confirm closure).
• Explain how manage by exception applies to Project Board direction and when the board should intervene.
• Distinguish Project Board responsibilities from Project Manager responsibilities for controlling the project.
• Identify key information and reports used by the Project Board to direct the project effectively.

Initiating a Project (IP)

• State the purpose of Initiating a Project and how it establishes a solid foundation for delivery.
• Identify the main components of the PID and how they support governance, control, and communication.
• Explain how management approaches for risk, issues, quality, and communication are established during initiation.
• Distinguish what is baselined during initiation and how baselines support subsequent control.
• Identify management products produced or updated during Initiating a Project (PID, Business Case, plans, approaches, and registers).

Controlling a Stage (CS)

• State the purpose of Controlling a Stage and how it enables the project manager to manage within agreed tolerances.
• Explain how work packages are authorized, monitored, and controlled during a stage.
• Explain how progress is monitored and reported during a stage and how corrective actions are taken.
• Decide what to do when a stage forecast indicates tolerances will be exceeded, including escalation and exception handling.
• Identify key management products used or updated during Controlling a Stage (for example, Work Packages, registers, and progress reports).

Managing Product Delivery (MP)

• State the purpose of Managing Product Delivery and the interface it manages between the project manager and delivery teams.
• Distinguish responsibilities of the team manager and project manager for accepting, executing, and delivering work packages.
• Explain how quality criteria and acceptance methods are applied during product delivery.
• Distinguish a Work Package from a Team Plan and explain when each is used.
• Identify management products produced or updated during Managing Product Delivery (work package status and checkpoint reporting).

Managing a Stage Boundary (SB)

• State the purpose of Managing a Stage Boundary and how it supports decisions to continue, change direction, or stop.
• Identify key outputs of Managing a Stage Boundary such as the next Stage Plan, End Stage Report, and updates to the Business Case and Project Plan.
• Explain how actual performance and forecasts inform re-planning and tolerance decisions at a stage boundary.
• Distinguish a stage boundary update from an exception situation that requires an exception plan.
• Identify who approves the next Stage Plan and what information they typically require to make that decision.

Closing a Project (CP)

• State the purpose of Closing a Project and the key checks required before closure.
• Distinguish planned closure from premature closure and identify typical triggers for each.
• Explain how outstanding issues and risks are handled at project closure.
• Identify management products produced at closure (End Project Report, Lessons Report) and their purpose.
• Decide what follow-on actions help ensure benefits are realized after the project is closed.