PRINCE2 Foundation — PRINCE2 Project Management Foundation (Version 7) Exam Blueprint

How to Use This Exam Blueprint

Use this checklist as a final-review map for the PeopleCert PRINCE2 Project Management Foundation (Version 7) exam, code PRINCE2 Foundation. It is organized around the practical knowledge a candidate should be able to recognize, connect, and apply in short project scenarios.

For each area, ask:

• Can I explain the PRINCE2 concept in plain language?
• Can I identify where it fits in the method?
• Can I choose the next sensible action in a scenario?
• Can I distinguish similar terms, roles, artifacts, and decision points?
• Can I apply the idea across predictive, agile, hybrid, supplier, customer, and organizational contexts?

Because exact exam weighting is not provided here, treat the sections below as readiness areas rather than a weighted scoring model.

Topic-Area Readiness Table

PRINCE2 Method Structure Checklist

Core Integration

Check that you can explain how these elements work together:

• Principles guide whether PRINCE2 is being used correctly.
• People considerations shape stakeholder engagement, collaboration, communication, and change.
• Practices describe recurring management concerns such as risk, quality, plans, and business case.
• Processes describe the project lifecycle and decision flow.
• Management products/artifacts provide evidence, control, and communication.
• Tailoring adapts the method to the project without removing essential governance.

“Can You Do This?” Prompts

• Given a scenario, identify whether the issue is about a principle, practice, process, role, or artifact.
• Explain why PRINCE2 is product-focused rather than activity-focused.
• Distinguish a project decision from a delivery-team decision.
• Identify whether a problem should be handled within tolerance or escalated.
• Explain why the business case is reviewed repeatedly, not just created at the start.
• Recognize why tailoring is required, not optional decoration.

Principles Readiness Checklist

Principle Traps

• Do not confuse continued business justification with “the project had a good reason at the start.”
• Do not treat lessons as only a closing activity.
• Do not confuse roles with job titles; one person may hold multiple roles if appropriate, but accountability must stay clear.
• Do not ignore stage boundaries; they are major control and decision points.
• Do not escalate every issue; escalate when authority or tolerance is exceeded.
• Do not define success only by completing activities; PRINCE2 emphasizes products, acceptance, and value.
• Do not tailor by deleting controls that the project still needs.

People Readiness Checklist

PRINCE2 Foundation candidates should be ready for questions where the technically correct process action is not enough; the people context matters.

People Scenario Checks

Ask yourself what PRINCE2 response fits best:

Business Case Practice Checklist

The business case is central to PRINCE2 decision-making. Be ready to connect it to project start-up, initiation, stage boundaries, exception handling, and closure.

Key Review Points

• Purpose of the business case: justify investment and continued commitment.
• Difference between outputs, outcomes, benefits, and disbenefits.
• Why benefits may be realized during or after the project.
• How risk, cost, time, scope, quality, benefits, and sustainability considerations can affect justification.
• Why the project board needs reliable business justification before authorizing major commitments.
• How the business case is updated when forecasts or assumptions change.
• What happens when the business case is no longer viable.

Output, Outcome, Benefit, Disbenefit

Can You Do This?

• Identify whether a scenario describes an output, outcome, benefit, or disbenefit.
• Explain why an attractive product may still not justify the project.
• Decide whether new information should trigger a business case update.
• Recognize when a project should be stopped or escalated because justification is lost.
• Connect benefits ownership to the right governance role rather than assigning it only to the delivery team.

Organizing Practice Checklist

Role Readiness Table

Responsibility Checks

• Who owns the business case?
• Who represents users and benefit realization interests?
• Who represents supplier capability and technical integrity?
• Who manages the project day to day?
• Who delivers a work package?
• Who accepts completed work?
• Who authorizes initiation, stages, exceptions, and closure?
• Who should be informed versus who must approve?

Plans Practice Checklist

PRINCE2 planning is closely tied to product focus, stages, tolerances, and control.

Plan Types and Readiness

Product-Based Planning Checks

• Define the final project product clearly.
• Break down required products before listing activities.
• Create or interpret product descriptions.
• Identify quality criteria and acceptance criteria.
• Understand product dependencies and sequence.
• Link plans to estimates, resources, risks, and controls.
• Keep plans consistent with the business case and tolerances.

Planning Scenario Cues

Quality Practice Checklist

Quality questions often test whether you understand product focus and acceptance.

Quality Terms to Review

Can You Do This?

• Distinguish quality planning from quality control.
• Explain why acceptance criteria should be defined early.
• Identify when a product description is incomplete.
• Recognize that “finished work” is not necessarily “accepted work.”
• Select a suitable response when quality criteria are not met.
• Connect quality failures to issues, risks, plans, and business justification.

Risk Practice Checklist

Risk readiness requires both terminology and judgment.

Risk Concepts

• A risk is an uncertain event or set of events that would affect objectives if it occurred.
• Risks can be threats or opportunities.
• A risk should have a cause, event, and effect.
• Risk responses should be proportionate to exposure and project context.
• Risks may require escalation if they threaten tolerance or business justification.
• Risks should be owned, monitored, and reviewed.

Risk Response Readiness

Can You Do This?

• Write a risk in cause-event-effect form.
• Distinguish a risk from an issue that has already happened.
• Identify who should own a risk.
• Choose a response that matches threat or opportunity.
• Recognize when a risk should be escalated.
• Explain how risk affects the business case and plans.

Issues Practice Checklist

Issues are events or matters that require management attention now.

Issue Types

Issue Handling Checks

• Capture and assess the issue.
• Determine impact on plans, products, quality, risk, benefits, and business case.
• Check authority and tolerances.
• Decide whether it can be handled by the project manager or must be escalated.
• Update relevant records.
• Communicate decisions to affected stakeholders.
• Keep baselines controlled.

Common Issue Traps

• Treating every issue as a risk.
• Approving changes without checking impact.
• Ignoring off-specifications because the team is “nearly done.”
• Escalating minor issues that are within delegated authority.
• Failing to update plans and business case after approved changes.

Progress Practice Checklist

Progress is about control: measuring actual status against plan, forecast, tolerance, and business justification.

Key Progress Concepts

Tolerance Decision Checks

Process Readiness Checklist

PRINCE2 Process Map

Starting Up a Project

You should be able to:

• Explain why PRINCE2 does not fully initiate every idea automatically.
• Identify the purpose of the project brief.
• Recognize the need for an outline business case.
• Understand initial role appointments.
• Identify when lessons from previous work should be considered.
• Know why the initiation stage needs a plan before being authorized.

Directing a Project

You should be able to:

• Identify project board decision points.
• Distinguish directing from day-to-day managing.
• Recognize when the board authorizes initiation, project continuation, stage progression, exception response, or closure.
• Explain why board decisions rely on accurate reports and updated business justification.
• Identify when escalation above the project board may be required.

Initiating a Project

You should be able to:

• Explain why initiation creates a controlled foundation.
• Identify the purpose of project initiation documentation.
• Connect management approaches to risk, quality, communication, change, and control.
• Recognize when the business case is refined.
• Understand how project controls and tolerances are established.
• Distinguish initiation work from specialist product delivery.

Controlling a Stage

You should be able to:

• Identify the project manager’s day-to-day control activities.
• Explain how work packages are authorized and monitored.
• Recognize when issues and risks are reviewed.
• Know when highlight reports are used.
• Identify when an exception report is required.
• Explain why the project manager manages within stage tolerances.

Managing Product Delivery

You should be able to:

• Explain the relationship between project manager and team manager/team.
• Identify why a team must understand and accept a work package.
• Recognize checkpoint reporting.
• Connect product delivery to quality checks.
• Identify when completed products are returned or approved.
• Distinguish delivery management from project governance.

Managing a Stage Boundary

You should be able to:

• Explain why stage boundaries are formal control points.
• Identify what is reviewed at the end of a stage.
• Recognize updates to plans, risks, issues, lessons, and business case.
• Know why the next stage plan is prepared before authorization.
• Understand how exception planning can replace normal boundary planning when directed.

Closing a Project

You should be able to:

• Explain why projects need controlled closure.
• Confirm whether products have been accepted.
• Identify handover and follow-on action needs.
• Recognize final reporting and lessons capture.
• Connect closure to benefits review and future accountability.
• Distinguish premature closure from planned closure.

Management Products and Artifact Checklist

You do not need to memorize artifacts as isolated documents. Know why each exists, who uses it, and when it changes.

Scenario and Decision-Point Checks

What Should Happen Next?

Escalation Judgment

    flowchart TD
	    A[New event, forecast, issue, or risk] --> B{Has it already happened?}
	    B -->|No, uncertain| C[Manage as risk]
	    B -->|Yes or requires action now| D[Manage as issue]
	    C --> E{Within delegated tolerance and authority?}
	    D --> E
	    E -->|Yes| F[Project manager or team handles and updates records]
	    E -->|No| G[Escalate to the appropriate higher authority]
	    G --> H{Does it affect business justification?}
	    H -->|Yes| I[Review business case and decision options]
	    H -->|No| J[Seek direction or approval for response]

Performance Targets and Control Checklist

Be ready to recognize how project performance targets interact. PRINCE2 scenarios often include trade-offs.

Trade-Off Prompts

• If scope increases, what happens to cost, time, quality, benefits, and risk?
• If time is fixed, what must be controlled or negotiated?
• If quality is reduced, does the product still meet acceptance criteria?
• If costs rise, does the business case still justify the project?
• If sustainability requirements change, which plans, risks, issues, suppliers, or acceptance criteria are affected?
• If benefits decrease, who needs to know and decide?

Tailoring Checklist

Tailoring means applying PRINCE2 appropriately to the project context. It does not mean ignoring the method.

Tailoring Factors

Tailoring Traps

• Removing stage boundaries from a project that still needs formal control.
• Treating agile delivery as a replacement for project governance.
• Overloading a simple project with unnecessary documentation.
• Under-controlling a complex or high-risk project.
• Tailoring role names but losing accountability.
• Changing artifact formats but failing to preserve required information.
• Ignoring supplier/customer boundaries in commercial projects.

Agile, Predictive, and Hybrid Scenario Checks

The PRINCE2 Foundation exam may describe different delivery environments. Focus on governance logic.

Can You Do This?

• Explain that PRINCE2 controls the project while teams may use different delivery techniques.
• Identify when agile flexibility still requires change control.
• Recognize that frequent product delivery does not remove the need for business justification.
• Distinguish team-level decisions from project board decisions.
• Tailor documentation without removing essential control information.

Common Weak Areas and Exam Traps

Final-Week Readiness Checklist

Knowledge Refresh

• Recite and explain the PRINCE2 principles in your own words.
• Sketch how the seven processes connect across the project lifecycle.
• Match each practice to its main artifacts, decisions, and risks.
• Review role responsibilities until you can answer without hesitation.
• Compare similar artifacts: project brief vs project initiation documentation, stage plan vs project plan, risk register vs issue register.
• Review outputs, outcomes, benefits, and disbenefits.
• Review tolerance, exception, escalation, and management by exception.
• Review how tailoring preserves principles.

Scenario Practice

• For every practice question, identify the topic being tested before choosing an answer.
• Ask, “Who has authority here?”
• Ask, “Is this within tolerance?”
• Ask, “Is this a risk, issue, change, off-specification, or quality matter?”
• Ask, “Which artifact should be created or updated?”
• Ask, “Does this affect the business case?”
• Ask, “What decision point is the project at?”
• Ask, “What would PRINCE2 do next to maintain control?”

Final Review Table

Practical Next Step

Mark each checklist item as ready, needs review, or uncertain. Start with the uncertain items that affect scenario judgment: roles, tolerances, business case, issues, risks, stage boundaries, and product acceptance. Then use PRINCE2 Foundation-style practice questions to test whether you can apply the checklist under exam conditions.