PRINCE2 Agile Practitioner (Version 2) Exam Blueprint

How to Use This Exam Blueprint

This checklist is for candidates preparing for the PeopleCert PRINCE2 Agile Practitioner (Version 2) exam, official exam code PRINCE2 Agile Practitioner. Use it as a practical study map for final review: identify what you can apply confidently, what you only recognize in theory, and what still breaks down in scenario questions.

The Practitioner level is not only about recalling terms. You should be ready to judge how PRINCE2 governance and agile delivery interact in a project scenario.

Use each section to ask:

• Can I apply the concept to a project situation?
• Can I choose the best next action?
• Can I decide which role, product, practice, or process is involved?
• Can I explain how to tailor PRINCE2 for an agile context without weakening governance?
• Can I spot when a project team is “doing agile activities” but not managing the project effectively?

Topic-Area Readiness Table

Core PRINCE2 Agile Understanding

You should be able to explain PRINCE2 Agile as an approach for applying PRINCE2 project governance while using agile ways of working for delivery where appropriate.

Check Your Understanding

• I can distinguish project direction, project management, and product delivery.
• I can explain why PRINCE2 and agile are not substitutes for each other.
• I can describe how PRINCE2 provides governance while agile helps teams deliver, learn, and adapt.
• I can recognize when agile terminology is being used without enough project control.
• I can recognize when project governance is too heavy and is constraining agile delivery.
• I can explain why tailoring is necessary rather than optional in an agile project environment.

Scenario Cues

PRINCE2 Principles in Agile Scenarios

Know the principles well enough to apply them, not just define them.

Can You Do This?

• Given a scenario, identify which PRINCE2 principle is most relevant.
• Explain how an agile technique supports a PRINCE2 principle.
• Spot where “being agile” is used as an excuse to avoid governance.
• Spot where “following PRINCE2” is used as an excuse to avoid feedback, learning, or collaboration.
• Recommend a tailored response that keeps the principle intact.

PRINCE2 Practices Checklist

The PRINCE2 practices are a major readiness area because Practitioner scenarios often test which management product, role, or decision should be used.

Business Case

Checklist:

• I can identify when a business case should be updated.
• I can explain how agile feedback may strengthen or weaken justification.
• I can distinguish “delivering all requested features” from “delivering enough value.”
• I can identify when benefits expectations are unrealistic or unsupported.
• I can explain why lower-priority scope may be flexed if value is protected.

Organizing

Checklist:

• I can distinguish the project manager’s role from the delivery team’s role.
• I can identify when the project board should be involved.
• I can spot unclear product ownership or prioritization authority.
• I can explain how stakeholder engagement supports acceptance.
• I can recognize when a self-organizing team still needs boundaries and objectives.

Plans

Checklist:

• I can explain progressive elaboration in a PRINCE2 Agile context.
• I can distinguish a stage from an iteration or sprint.
• I can identify when a plan is too detailed too early.
• I can identify when a plan is too vague for governance.
• I can connect product-based planning to agile backlog and delivery planning.
• I can explain how tolerances apply to plans.

Quality

Checklist:

• I can identify missing or weak quality criteria.
• I can distinguish acceptance criteria from general user preferences.
• I can explain why quality should not be silently traded for speed.
• I can identify where testing should be integrated earlier.
• I can recommend quality controls suitable for agile delivery.

Risk

Checklist:

• I can identify risks from agile project facts.
• I can distinguish a risk from an issue.
• I can decide when a risk should be escalated.
• I can explain how early delivery and feedback reduce uncertainty.
• I can identify where agile practices introduce new risks if misused.

Issues and Change

Checklist:

• I can decide whether something is a risk, issue, change, or normal backlog refinement.
• I can identify when change can be handled within tolerances.
• I can identify when change threatens time, cost, quality, scope, benefits, or risk tolerances.
• I can explain why agile responsiveness is not uncontrolled change.
• I can recommend the artifact or decision route that should be updated.

Progress

Checklist:

• I can identify suitable progress information for different audiences.
• I can distinguish team-level progress from project-level control.
• I can decide when progress data suggests a tolerance issue.
• I can explain why transparency is more useful than optimistic reporting.
• I can recognize when a project needs formal escalation rather than more team discussion.

PRINCE2 Processes in Agile Context

You should be able to place agile work inside the PRINCE2 process model and decide what management activity belongs where.

Can You Match the Action to the Process?

• Authorize the project to proceed.
• Agree how project controls will work with agile delivery.
• Assign a work package or equivalent delivery responsibility.
• Review whether the next stage remains justified.
• Escalate an exception.
• Confirm final acceptance.
• Capture lessons from agile delivery and project governance.
• Update the business case after feedback changes expected value.

Agile Concepts You Should Be Able to Apply

The exam may test whether you understand agile as a set of behaviors, principles, and techniques rather than a collection of ceremonies.

Checklist:

• I can explain the difference between iterative and incremental delivery.
• I can describe why frequent feedback supports better governance.
• I can identify when a timebox is being misused.
• I can explain how prioritization protects value.
• I can recognize when collaboration is insufficient for agile working.
• I can distinguish agile flexibility from lack of control.

Fix and Flex Readiness

PRINCE2 Agile scenarios often require judgment about what can change and what should be protected. Be prepared to reason about time, cost, quality, scope, benefits, and risk without assuming everything is flexible.

Decision Prompt

When a scenario presents a deadline conflict, ask:

1. Is the deadline genuinely fixed or only assumed?
2. Which products or features are highest value?
3. What quality criteria must be protected?
4. Can lower-priority scope be deferred?
5. Does the change threaten business justification?
6. Is a tolerance likely to be breached?
7. Who has authority to decide?

Roles, Responsibilities, and Decision Authority

Practitioner questions often test who should act, decide, escalate, approve, or provide information.

Can You Do This?

• Identify who should approve a change outside tolerance.
• Identify who should clarify acceptance criteria.
• Identify who should remove an impediment beyond the team’s control.
• Identify who should update a plan, risk register, issue record, or business case.
• Identify who should decide product priority when stakeholders disagree.
• Identify when a project manager should facilitate rather than direct the team’s internal work.

Products, Artifacts, and Information Checks

Be ready to connect PRINCE2 management products with agile artifacts and information sources. The exact naming in a scenario may vary; focus on purpose.

Checklist:

• I can identify which artifact should be updated after a scenario event.
• I can distinguish product-level acceptance information from project-level governance information.
• I can recognize when backlog items are too vague for delivery.
• I can recognize when a management product is too heavy for the project context.
• I can explain how agile artifacts provide evidence for PRINCE2 control.

Tailoring PRINCE2 for Agile Delivery

Tailoring is a key Practitioner skill. The goal is not to remove PRINCE2 controls; it is to make them fit the project while preserving principles.

Tailoring Decision Questions

Use these prompts when reviewing scenario answers:

• Does the tailoring still support the PRINCE2 principles?
• Is the amount of control proportionate to risk, complexity, and stakeholder need?
• Does the project board still receive the information needed to govern?
• Does the delivery team still have enough autonomy to work effectively?
• Are quality and acceptance criteria still explicit?
• Are decisions recorded sufficiently for the project context?
• Is the approach practical for the team and stakeholders?

Scenario Judgment: What Should Happen Next?

Many Practitioner questions are built around choosing the best next action. Train yourself to slow down and identify the management problem before choosing the agile-sounding or governance-sounding option.

Agile Techniques and Their Exam-Relevant Purpose

You do not need to turn every scenario into a method debate. Focus on why a technique helps project control, value, quality, or collaboration.

Planning and Forecasting Checks

Be ready to reason about multiple planning horizons.

Planning Questions to Practice

• What level of plan is being discussed: project, stage, release, team, or iteration?
• Is the plan detailed enough for current decisions?
• Is the plan too detailed for the uncertainty involved?
• Does the plan identify products, dependencies, risks, and tolerances?
• Are estimates being treated as commitments before enough is known?
• Is progress evidence being used to update forecasts?
• Are lower-priority items available as flex if needed?

Common Planning Traps

Quality, Testing, and Acceptance Readiness

Quality questions often hide inside schedule, scope, or stakeholder scenarios.

Checklist:

• I can explain the role of acceptance criteria.
• I can identify when a definition of done is incomplete.
• I can distinguish verification from acceptance.
• I can recommend earlier customer feedback.
• I can identify when quality problems create project risk.
• I can protect quality while still allowing scope flexibility.

Risk, Issue, and Change Decision Path

Use this simplified decision path when practicing scenario questions.

    flowchart TD
	    A[New event or information appears] --> B{Has it already happened?}
	    B -->|No| C[Consider as risk]
	    B -->|Yes| D{Is it a problem, request, or deviation?}
	    D -->|Problem or impediment| E[Handle as issue or impediment]
	    D -->|Requested change| F[Assess change impact]
	    D -->|Forecast tolerance breach| G[Escalate as exception]
	    C --> H[Assess probability, impact, response, owner]
	    E --> I{Within team or project authority?}
	    F --> J{Within agreed tolerances?}
	    I -->|Yes| K[Manage locally and update information]
	    I -->|No| G
	    J -->|Yes| K
	    J -->|No| G
	    G --> L[Seek decision from appropriate authority]

Decision Checklist

• Is the event a risk, issue, change, or normal delivery detail?
• Does the team have authority to resolve it?
• Does it affect time, cost, quality, scope, benefits, or risk?
• Does it threaten tolerance?
• Does it change business justification?
• Which artifact needs updating?
• Who needs to know or decide?

Governance and Agile Delivery Balance

A strong PRINCE2 Agile Practitioner candidate can avoid two extremes: uncontrolled agile delivery and over-controlled project bureaucracy.

Common Weak Areas and Traps

Use this section for targeted final review.

“Can You Do This?” Practitioner Skills Checklist

Use this as a pass-readiness self-test.

Governance and Tailoring

• I can explain how PRINCE2 governance supports agile delivery.
• I can tailor a control without removing its purpose.
• I can decide when formal escalation is required.
• I can identify the appropriate authority for a decision.
• I can explain why agile teams still need project boundaries.
• I can recognize over-governance and recommend a lighter approach.

Value and Business Justification

• I can connect product priority to expected value.
• I can identify when the business case should be reviewed.
• I can explain why delivering less scope may still be acceptable.
• I can identify when benefits are threatened.
• I can distinguish high-value features from merely requested features.

Delivery and Planning

• I can distinguish project, stage, release, team, and iteration planning.
• I can identify which plan should be updated after a change.
• I can explain how agile forecasting supports progress control.
• I can identify when a plan is too detailed or too vague.
• I can reason about dependencies and constraints.

Quality and Acceptance

• I can identify missing acceptance criteria.
• I can explain why quality should be protected.
• I can distinguish done, accepted, and merely worked on.
• I can recommend earlier quality checking or feedback.
• I can identify quality risk from scenario facts.

Risk, Issues, and Change

• I can classify risks, issues, changes, and impediments.
• I can identify whether an item can be handled locally.
• I can judge whether tolerances are threatened.
• I can recommend updating the right management information.
• I can explain how agile feedback affects risk management.

Stakeholders and Collaboration

• I can identify the right stakeholder engagement approach.
• I can spot decision bottlenecks.
• I can recommend demos, reviews, workshops, or direct collaboration when appropriate.
• I can explain how stakeholder feedback affects priorities and acceptance.
• I can recognize when stakeholder conflict needs governance attention.

Scenario Practice Prompts

Review these prompts and force yourself to answer with a role, artifact, process/practice, and reason.

Final-Week Review Checklist

Content Review

• Re-read your notes on PRINCE2 principles and practice applying each one to agile scenarios.
• Review all PRINCE2 practices and identify the artifact or decision each supports.
• Review all PRINCE2 processes and practice matching actions to processes.
• Review agile concepts: iteration, increment, timebox, prioritization, feedback, collaboration, transparency, and self-organization.
• Review fix/flex reasoning across time, cost, quality, scope, benefits, and risk.
• Review common role-confusion scenarios.
• Review how change, risk, issue, and exception handling differ.

Scenario Technique

• For each practice question, identify the core management problem before reading the options.
• Eliminate answers that remove governance entirely.
• Eliminate answers that over-control the delivery team unnecessarily.
• Prefer answers that protect quality and business justification.
• Prefer answers that use evidence, feedback, and appropriate escalation.
• Watch for answers that sound agile but ignore tolerances, roles, or acceptance.
• Watch for answers that sound formal but block learning or collaboration.

Personal Weak-Spot Drill

Final Readiness Questions

Before you consider yourself ready for the PeopleCert PRINCE2 Agile Practitioner (Version 2) exam, you should be able to answer “yes” to most of these:

• Can I apply PRINCE2 principles to agile project scenarios?
• Can I choose the right practice or process for a scenario event?
• Can I decide when to escalate and when to manage locally?
• Can I explain how agile techniques support governance rather than replace it?
• Can I protect quality while allowing scope flexibility?
• Can I identify the correct role or authority for a decision?
• Can I connect backlog priority to business justification and benefits?
• Can I interpret progress evidence without over-relying on a single metric?
• Can I tailor documentation, reporting, and controls appropriately?
• Can I explain why a proposed answer is wrong, not just why one is right?

Practical Next Step

Use this checklist to mark three categories: confident, needs review, and scenario weak. Then spend your next practice session only on the weak areas. For each missed question, record the tested principle, practice, process, role, and decision point. This will turn practice into targeted readiness for the real PRINCE2 Agile Practitioner exam.