Try 40 free PRINCE2 Agile Foundation questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length PRINCE2 Agile Foundation practice exam includes 40 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 40-question full-length practice format for PRINCE2 Agile Foundation Version 2 review. Always confirm current booking, language availability, and delivery rules directly with PeopleCert.
Set a 60-minute timer and answer all 40 questions before reading explanations. Track misses by PRINCE2-agile blending, principles, themes, processes, behaviours, or delivery focus.
Use this page as a PRINCE2 Agile Foundation diagnostic, not as the only measure of readiness. The most useful result is the pattern behind your misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your foundation model may be stable. Review explanations and protect timing. | |
| Many PRINCE2-governance misses | Revisit roles, tolerances, stages, management products, and business justification. | |
| Many agile-practice misses | Drill timeboxes, feedback, transparency, prioritization, and team collaboration. | |
| Many tailoring misses | Review how agile practices support PRINCE2 control rather than replace it. | |
| You choose rigid or uncontrolled answers | Look for the option that preserves both governance and adaptive delivery. |
| Field | Record |
|---|---|
| Overall score | ___ / 40 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | PRINCE2 control / agile concepts / tailoring / wider context |
| Most expensive mistake type | too rigid / too uncontrolled / weak prioritization / role confusion / other: ___ |
For concept review before or after this set, use the PRINCE2 Agile Foundation guide on PMExams.com.
This static page is useful for one diagnostic pass. PM Mastery is better for repeated practice because it gives you varied timed attempts, focused PRINCE2 Agile drills, explanations, and progress history instead of one page you can memorize.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-15 | 20 minutes | Keep governance and agile vocabulary decisions quick. |
| Questions 16-30 | 40 minutes cumulative | Watch for tailoring and prioritization traps. |
| Questions 31-40 | 60 minutes cumulative | Finish with enough time to review marked hybrid-control items. |
If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Give more weight to varied timed attempts in PM Mastery than to repeating one static page.
| Item | Detail |
|---|---|
| Issuer | PeopleCert |
| Exam route | PRINCE2 Agile Foundation |
| Official exam name | PRINCE2 Agile Foundation (Version 2) |
| Full-length set on this page | 40 questions |
| Exam time | 60 minutes |
| Topic areas represented | 4 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Agile Mindset and Change Management | 30% | 12 |
| PRINCE2 Agile Principles and Practices | 40% | 16 |
| PRINCE2 Agile Processes and Workshops | 25% | 10 |
| PRINCE2 Agile Wider Context | 5% | 2 |
Topic: Agile Mindset and Change Management
A project manager says, “If we are agile, the team can change direction at any time without governance.” Which TWO statements correctly distinguish an agile mindset from unmanaged flexibility in PRINCE2 Agile? Select TWO.
Correct answers: B, C
What this tests: Agile Mindset and Change Management
Explanation: An agile mindset is not the same as uncontrolled change. In PRINCE2 Agile, teams respond to change through transparency, feedback, and agreed limits, so agility improves control rather than removing it.
In PRINCE2 Agile, being agile means adopting behaviors and ways of thinking that support collaboration, learning, and responsiveness to change. That does not mean working without governance. Agile teams still need clear priorities, visibility of progress, and agreed boundaries for decision-making.
An agile mindset is shown when teams:
Unmanaged flexibility is different. It treats agility as permission to change direction randomly, ignore priorities, or leave expectations unclear. In PRINCE2 Agile, agility and control work together; agility is disciplined responsiveness, not a lack of control.
An agile mindset supports adaptation, but in PRINCE2 Agile it still operates within agreed governance and tolerance limits.
An agile mindset relies on visibility and feedback to help the project stay controlled while learning and adapting.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project is preparing for a project board decision on whether to continue into the next stage. The board wants someone, acting on its behalf, to independently check that the project manager’s reporting is reliable and that agreed controls are being followed. Which role has this governance responsibility?
Best answer: D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: This responsibility belongs to project assurance because it gives the project board independent confidence about progress information and control compliance. The clue is acting on the board’s behalf to check, not directing the project or providing administration.
In PRINCE2 Agile, project assurance is the role that monitors the project independently for the project board. Its purpose is to give the board confidence that the project is being managed correctly, that reporting is dependable, and that agreed controls are in place and being followed. That is a governance responsibility, not a delivery or administrative one.
The key clue is “independently check” on behalf of the board. The project executive is accountable for overall project success and continued business justification, but does not perform the assurance function personally. Project support helps with administration and reporting services, while the senior supplier represents supplier interests and technical feasibility.
When the need is independent oversight for the board, think project assurance.
Project assurance provides independent checking to the project board that the project is being conducted properly and that information used for decisions is trustworthy.
Topic: PRINCE2 Agile Processes and Workshops
A PRINCE2 Agile project is nearing closure. The project manager wants a workshop to identify what went well, what did not go well, and what lessons should be captured before the project is closed.
Which agile workshop best fits this need?
Best answer: B
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The decisive clue is the need to capture lessons about how the team worked before project closure. That points to a retrospective, which is the agile workshop used to reflect on performance, identify improvements, and record learning.
In PRINCE2 Agile, closing a project includes confirming what has been achieved and capturing lessons for future work. The workshop that best supports this is the retrospective because it is specifically used to reflect on ways of working, discuss what went well or badly, and identify improvements.
A review is mainly about inspecting the product or increment with stakeholders. Release planning looks ahead to upcoming delivery, and a daily stand-up coordinates immediate work. The key clue here is reflection and lesson capture at the end of the project, which is the purpose of a retrospective.
A retrospective focuses on learning from how the work was done, which directly supports lesson capture when closing a project.
Topic: Agile Mindset and Change Management
In PRINCE2 Agile, what does culture mean in the context of organizational change management?
Best answer: D
What this tests: Agile Mindset and Change Management
Explanation: In PRINCE2 Agile, culture refers to the shared values, beliefs, and norms in an organization or team. It matters because those shared behaviors can help agile ways of working be accepted quickly or can cause resistance to change.
At Foundation level, culture in PRINCE2 Agile is understood as the shared norms, values, and accepted ways of behaving within a team or organization. This is an important OCM concept because agile change is not only about introducing practices such as reviews or backlogs; it also depends on whether people are willing to collaborate, adapt, and work transparently. A supportive culture can encourage experimentation, feedback, and continuous improvement, while a resistant culture can slow or block agile adoption. The key point is that culture shapes how people react to change, so understanding it helps explain why the same agile approach may succeed in one environment and struggle in another.
Culture is the shared way people think and behave, so it can either support or resist agile change.
Topic: Agile Mindset and Change Management
Which PRINCE2 term matches this description?
The permitted range of deviation for time, cost, quality, scope, benefits, and risk that is used to control project performance and trigger escalation if exceeded.
Best answer: A
What this tests: Agile Mindset and Change Management
Explanation: In PRINCE2, project performance is controlled by setting targets for six aspects and allowing defined deviation around them. That permitted deviation is called tolerance, and exceeding it leads to escalation under management by exception.
PRINCE2 controls project performance through six aspects: time, cost, quality, scope, benefits, and risk. For each level of management, acceptable limits can be set around these targets. Those limits are called tolerance. If forecast performance is expected to go outside tolerance, the matter is escalated to the next management level.
This differs from agile delivery terms that focus on product quality or flow. Acceptance criteria describe what a product or user story must meet. Definition of Done states the conditions for completion. A work in progress limit controls flow by restricting how much work is active at one time.
The key distinction is that tolerance is a PRINCE2 project control concept, not a product-quality or Kanban flow concept.
Tolerance is the allowed deviation against PRINCE2 performance targets across the six project aspects.
Topic: PRINCE2 Agile Principles and Practices
In PRINCE2 Agile, the purpose of the ____ practice is to identify, assess, and control uncertainty that could affect project objectives.
Best answer: A
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, risk is about uncertainty that may affect objectives. The risk practice exists to identify, assess, and control that uncertainty so the project can respond appropriately and stay viable.
The core concept is the risk practice. In PRINCE2 Agile, a risk is an uncertain event or set of events that, if it occurs, could affect objectives. The purpose of the risk practice is therefore to identify uncertainty early, assess its likely effect, and control it through suitable responses and ongoing review.
This matters in agile projects because uncertainty can emerge quickly as work is delivered iteratively. PRINCE2 Agile still requires clear management of risk, even when teams are working in short timeboxes and adapting frequently. A key distinction is that risk concerns something that has not happened yet, whereas an issue is something that already exists. The closest distractor is issues, but issues are managed after uncertainty has become a current problem or event.
The risk practice manages uncertainty by identifying, assessing, and controlling events that could affect objectives.
Topic: Agile Mindset and Change Management
A PRINCE2 Agile project is introducing a new expense process to three departments in small releases. The project manager wants organizational change to be supported by visibility of adoption and by feedback after each release. The delivery team already uses a team dashboard for day-to-day work. Which approach BEST supports OCM in this situation?
Best answer: D
What this tests: Agile Mindset and Change Management
Explanation: Agile supports OCM by using transparency, engagement, feedback, and incremental change to help people adapt as the project progresses. In this scenario, the project dashboard is the right artifact because it communicates project-level progress and adoption information to a wider stakeholder group.
The key idea is that agile helps organizational change by making change visible, inviting feedback early, and introducing it in manageable increments. Here, the project is rolling out a new process across departments in small releases, so stakeholders need a transparent view of how adoption is going and what is being learned after each increment.
A project dashboard is suited to that wider communication need because it summarizes project-level progress, feedback, and outcomes for stakeholders beyond the delivery team. This supports engagement and allows decisions to be adjusted as the organization responds to each release. A team dashboard is useful, but mainly for the team’s day-to-day delivery coordination rather than broad OCM communication.
The main takeaway is that agile supports OCM not just by doing agile activities, but by making incremental change visible and responsive across the organization.
A project dashboard gives wider stakeholders transparent, project-level visibility so feedback from incremental change can guide ongoing adoption.
Topic: Agile Mindset and Change Management
Which statement best describes the purpose of the project canvas in PRINCE2 Agile?
Best answer: C
What this tests: Agile Mindset and Change Management
Explanation: In PRINCE2 Agile, the project canvas helps blend project management with agile by giving stakeholders and delivery teams a simple, shared view of the project. Its practical effect is better alignment and communication without losing agile flexibility.
The project canvas is a lightweight visual artifact used to summarize key project information in a way that is easy to discuss and update. This supports the PRINCE2 Agile blend by connecting project-level governance and direction with agile ways of working, helping everyone maintain a common understanding of what the project is trying to achieve. In practice, it improves communication, supports collaboration, and makes it easier to discuss priorities, scope, and outcomes across project and delivery roles. It is not the detailed team work list, a progress-tracking chart, or a completion standard for individual items.
The project canvas gives a concise, shared view of key project information so project management and agile delivery can align quickly.
Topic: PRINCE2 Agile Principles and Practices
In PRINCE2 Agile, the ____ is used to justify continued investment by focusing on expected benefits and value, while backlog ordering alone mainly decides what should be delivered first.
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, ongoing justification comes from the business case, not from backlog ordering by itself. Backlog ordering helps prioritize delivery, but the business case explains why the project should continue to receive investment.
The key distinction is purpose. The business case practice is used to confirm that the project remains worthwhile by considering expected benefits, value, costs, and risks. In an agile context, backlog ordering helps the team and stakeholders decide which work should be done first to maximize value delivery, but it does not replace the need for continued business justification.
A product backlog is a prioritization tool. A release map is a planning aid. A burn chart is a progress-tracking aid. Only the business case answers the question of whether the project should continue to be funded and supported.
So, ordering work well supports value delivery, but justification for investment still comes from the business case.
The business case provides the reason for the project to continue, based on expected benefits, costs, risks, and value.
Topic: PRINCE2 Agile Principles and Practices
In a PRINCE2 Agile project, the delivery team uses daily stand-ups to coordinate work. The project board wants a governance control that lets the team work autonomously unless agreed limits are forecast to be exceeded. What is the purpose of setting tolerances?
Best answer: A
What this tests: PRINCE2 Agile Principles and Practices
Explanation: Tolerances are a PRINCE2 governance control used to support manage by exception. They set agreed limits for time, cost, scope, quality, risk, or benefits so the agile team can deliver autonomously unless an exception is forecast.
In PRINCE2 Agile, governance control and agile delivery practices serve different purposes. Tolerances are a PRINCE2 control mechanism: they define the boundaries within which authority is delegated. This means the project manager or delivery team can manage day-to-day work without constant senior intervention, but must escalate if performance is forecast to go outside agreed limits.
This is different from agile team practices, which focus on delivery flow and team learning, for example:
The key distinction is that tolerances provide governance oversight, not a delivery ceremony.
Tolerances support PRINCE2 governance by enabling manage by exception while leaving day-to-day delivery with the agile team.
Topic: PRINCE2 Agile Processes and Workshops
At the end of a PRINCE2 Agile stage, the team holds a workshop to confirm what is likely to be delivered in the next stage and to update the release map. This is a ____.
Best answer: D
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The clue is the stage-boundary focus on future delivery and the release map. In PRINCE2 Agile, that points to a release planning workshop, not a workshop that inspects past performance or coordinates daily work.
A release planning workshop supports Managing a stage boundary when the project needs to look ahead and refresh delivery expectations for the next stage. The key indicator is the update to the release map, which helps show what is likely to be delivered and when. That makes it different from a retrospective, which looks back at how the team worked, a review, which examines delivered products, or a daily stand-up, which coordinates immediate work. The main takeaway is that future scope and release timing at a stage boundary signal release planning.
Updating the release map and agreeing likely delivery for the next stage are key clues for a release planning workshop at a stage boundary.
Topic: PRINCE2 Agile Processes and Workshops
A PRINCE2 Agile project is in delivery. The project manager is overseeing the current stage, and the agile team is using workshops to inspect results and improve how it works. Which TWO statements are correct? Select TWO.
Correct answers: B, C
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The correct statements distinguish a PRINCE2 Agile process from an agile workshop by purpose. Controlling a stage is a management process for the current stage, while a retrospective is a workshop used by the team to improve its way of working.
In PRINCE2 Agile, a process and a workshop are not the same thing. A process describes a structured area of project management responsibility, while an agile workshop is a collaborative event that supports delivery and learning. In this scenario, Controlling a stage is the process the project manager uses to monitor progress, manage issues, and keep the current stage under control. A retrospective is an agile workshop where the team reflects on what went well, what did not, and what should improve next.
The wrong statements confuse process purposes with other activities. Managing a stage boundary is about reviewing the current stage and preparing for the next one, not handling work packages during the stage. A review workshop focuses on examining completed work and gathering feedback, not defining project roles.
This is the purpose of the Controlling a stage process: to manage and monitor the stage on a day-to-day basis.
A retrospective is used to reflect on team working and agree actions for continuous improvement.
Topic: PRINCE2 Agile Wider Context
A project uses an AI tool to summarize dashboards, draft risk updates, and suggest backlog changes. Which clue shows this is an appropriate AI use case in PRINCE2 Agile?
Best answer: C
What this tests: PRINCE2 Agile Wider Context
Explanation: In PRINCE2 Agile, AI may support elements such as reporting, analysis, and draft outputs, but it does not replace accountable people. The decisive clue is that governance and decision accountability remain with the defined human roles.
The core idea is that AI is used as a support mechanism, not as a substitute for PRINCE2 Agile governance. In a suitable use case, AI can help with tasks such as summarizing dashboards, drafting updates, or proposing options, because these activities assist the project team and speed up information handling. However, accountability for decisions, approvals, assurance, and direction must remain with the relevant PRINCE2 Agile roles.
If the scenario shows that people still own decisions and governance, the AI use is appropriate. If the scenario says AI is approving, authorizing, or replacing a role, that goes beyond support and conflicts with the principle that accountability stays with human roles.
The key distinction is support versus substitution.
AI can support analysis and drafting, but accountable PRINCE2 Agile roles must still make and own decisions.
Topic: PRINCE2 Agile Principles and Practices
In PRINCE2 Agile, the ____ provides day-to-day support to the delivery team on agile working methods and team dynamics, while product-priority decisions remain with the Product Owner.
Best answer: D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The missing term is team coach. In PRINCE2 Agile, this role helps the delivery team work effectively in an agile way, especially through coaching, facilitation, and team improvement, while prioritization decisions stay with the Product Owner.
The team coach is a delivery-focused support role. Its main contribution is to help the team apply agile practices effectively, improve collaboration, and strengthen team dynamics on a day-to-day basis. This means influencing how the team works rather than deciding what the team should build.
In PRINCE2 Agile, product-priority and value decisions are part of the Product Owner’s area, not the team coach’s. The agile coach is a related role, but typically has a broader coaching remit across teams or the wider organization rather than the close day-to-day focus on one delivery team. The Chief Product Owner is also different because that role works at a higher product-governance level.
The key distinction is that the team coach improves team performance and agile behavior, not product direction.
The team coach supports the delivery team’s agile ways of working and team effectiveness without owning backlog prioritization.
Topic: Agile Mindset and Change Management
In PRINCE2 Agile, ____ are collaborative sessions that address the need for alignment and shared understanding by helping people explore ideas and plan together.
Best answer: A
What this tests: Agile Mindset and Change Management
Explanation: The missing term is workshops. In PRINCE2 Agile, workshops are used to bring people together so they can align, explore options, plan collaboratively, and develop shared understanding.
Workshops in PRINCE2 Agile are collaborative sessions designed to meet a common project need: getting the right people together to create alignment and shared understanding quickly. They support exploration, planning, clarification, and engagement, which helps teams and stakeholders work from the same view of what is needed and why. This fits the agile mindset because it encourages direct collaboration, faster feedback, and collective ownership of outcomes.
The closest distractor is retrospectives, but those are focused specifically on learning and improvement after work has been done, not the broader purpose described here.
Workshops are the PRINCE2 Agile sessions used to bring people together to align, explore, plan, and build shared understanding.
Topic: PRINCE2 Agile Processes and Workshops
During Initiating a Project, stakeholders hold a workshop to agree the high-level order of delivery and what should be included in each release. Which agile workshop is this?
Best answer: C
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The key clue is that the workshop is agreeing what will be delivered in each release and in what order. In PRINCE2 Agile, that points to a release planning workshop used to shape the high-level delivery view during initiation.
Agile workshops support Initiating a Project by creating shared understanding early and quickly. A release planning workshop is used when the team and stakeholders need a high-level view of delivery across releases, including sequencing and likely release content. That makes it the best match for a scenario about deciding what goes into each release.
A prioritization workshop focuses on ranking work by importance, a review workshop inspects completed output, and a retrospective workshop looks at how the team can improve. The decisive clue here is planning release content, not inspecting work or improving team behavior.
A release planning workshop focuses on the high-level sequencing and content of releases, which is the decisive clue in the scenario.
Topic: PRINCE2 Agile Processes and Workshops
During a stage, the team holds a short meeting every day to share recent progress, state what they will do next, and raise any blockers. Which agile workshop is being described?
Best answer: B
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The clue is the short meeting held every day to discuss progress, next steps, and blockers. In PRINCE2 Agile, that describes a daily stand-up, which supports monitoring and control during a stage.
A daily stand-up is the agile workshop most closely associated with frequent coordination during delivery. Its purpose is to give quick visibility of current progress, immediate priorities, and impediments so the team and project manager can maintain control within the stage.
The key clues are:
An iteration review is for showing completed work to stakeholders. A retrospective is for reflecting on how the team works and identifying improvements. Iteration planning is for agreeing the work to be done in the next iteration. The blocker-focused daily coordination makes this a daily stand-up.
A daily stand-up is the short, frequent workshop used to coordinate progress and expose impediments during delivery.
Topic: PRINCE2 Agile Wider Context
Which TWO statements correctly describe how AI can support PRINCE2 Agile elements?
Select TWO.
Correct answers: A, D
What this tests: PRINCE2 Agile Wider Context
Explanation: In PRINCE2 Agile, AI can support analysis, drafting, and insight generation for artifacts such as dashboards and release maps. It does not replace human judgement, governance decisions, or accountability held by roles such as the project manager or project executive.
The key idea is that AI is a support capability, not a substitute for PRINCE2 Agile authority. At syllabus depth, AI can help prepare or improve information used in practices, artifacts, and decisions, such as summarizing progress data for a project dashboard or identifying backlog patterns that may inform a release map. This can make reporting and planning faster and more consistent.
However, PRINCE2 Agile governance still depends on named human roles. Accountable people must review the information, apply judgement, and make decisions such as whether to escalate, approve plans, or confirm continued business justification. AI can inform these activities, but it cannot own governance or replace role accountability.
A useful test is simple: AI may support the work, but it does not become the accountable decision-maker.
AI can help produce dashboard content, but accountability for interpreting it and acting on it stays with the project manager.
AI may support planning analysis, yet approval of release decisions remains with the appropriate human roles.
Topic: Agile Mindset and Change Management
A PRINCE2 Agile project team has introduced user stories, regular reviews, retrospectives, and frequent delivery of small product increments. The project manager says these are examples of doing agile. Which benefit is MOST directly linked to this distinction?
Best answer: B
What this tests: Agile Mindset and Change Management
Explanation: Doing agile means using agile techniques and events such as reviews, retrospectives, user stories, and frequent delivery. Their most direct benefit is fast feedback, which helps the team learn early and improve the product. This distinction matters because PRINCE2 Agile separates practical agile methods from the wider agile mindset.
In PRINCE2 Agile, doing agile refers to using agile techniques, events, feedback mechanisms, and delivery practices. These create short feedback loops: small increments are delivered sooner, reviews gather user reactions, retrospectives improve the way the team works, and user stories help clarify needs. The most direct practical benefit is earlier feedback that allows quick refinement of products and priorities.
Being agile is different. It is more about mindset, behavior, and culture, such as openness, collaboration, and willingness to adapt. PRINCE2 Agile Foundation tests this distinction because a team may use agile practices without fully adopting an agile culture, and candidates need to recognize which benefits come from the practices themselves. The closest distractor is the culture-focused option, which is valuable but belongs more to being agile.
Agile techniques, events, feedback loops, and incremental delivery mainly create faster learning and product refinement.
Topic: PRINCE2 Agile Principles and Practices
An agile team provides this update to the project manager:
Iteration 3 burn chart
Day 1: 40 points remaining
Day 5: 22 points remaining
Day 10: 6 points remaining
In PRINCE2 Agile, what is the main purpose of a burn chart like this?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: A burn chart supports the PRINCE2 Agile progress practice by making remaining work visible over time. This gives transparent information for monitoring and simple forecasting of whether the team is likely to complete the timebox as planned.
In PRINCE2 Agile, a burn chart is used for the progress practice. Its purpose is to provide visible, current information about how much work remains in a timebox, so the team and project manager can see whether delivery is progressing as expected. This supports transparency and helps inform decisions about whether the work is on track.
A burn chart is not mainly a quality control tool, a prioritization tool, or a risk log. It is a progress-monitoring artifact that helps stakeholders quickly understand delivery status and likely completion within the agreed timebox.
The key distinction is that it shows progress trend, not product quality, value order, or risk detail.
A burn chart is a progress artifact used to make remaining work visible and help assess whether the timebox is on track.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project has two delivery teams. The Project Executive wants a concise view of overall project status for governance discussions. The teams want detailed, day-to-day visibility of work in progress and delivery trends. Which statement BEST compares the two dashboards?
Best answer: C
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The key difference is purpose and level. A project dashboard gives a high-level view for project oversight and governance, while a team dashboard gives detailed delivery information that helps the agile team manage work transparently day by day.
In PRINCE2 Agile, dashboards support transparency, but they are used at different levels. A project dashboard is aimed at project-level stakeholders and gives a concise summary of overall status, such as progress, forecast, and key information needed for governance. A team dashboard is aimed at the delivery team and shows more detailed, operational information to help manage ongoing work.
This means the Project Executive would normally use the project dashboard, while developers and other team members would use the team dashboard for daily visibility. Burn charts and similar detailed delivery measures are typically associated with team-level monitoring, not as a replacement for project-level reporting.
The main distinction is high-level governance visibility versus detailed team delivery visibility.
A project dashboard is for project-level oversight, while a team dashboard helps the team manage detailed delivery progress.
Topic: Agile Mindset and Change Management
Which statement correctly describes the difference between being agile and doing agile in PRINCE2 Agile?
Best answer: A
What this tests: Agile Mindset and Change Management
Explanation: In PRINCE2 Agile, being agile refers to the mindset, values, and behaviors that support adaptability and collaboration. Doing agile refers to applying methods and techniques such as Scrum, Kanban, backlogs, or timeboxes to organize and deliver work.
The key distinction is that being agile is about how people think and behave, while doing agile is about the practices they use. Being agile supports responsiveness, collaboration, learning, and value focus. Doing agile provides practical structures and techniques, such as backlogs, reviews, stand-ups, and visual boards, to help teams work in an agile way.
A simple use case is a project team that welcomes feedback and adapts priorities when customer needs change: that shows being agile. If the same team also uses a backlog and short timeboxes to manage delivery, that shows doing agile.
A team can do agile practices without truly being agile if the mindset is missing.
This matches PRINCE2 Agile: mindset shapes behavior, while methods and techniques provide practical ways of working.
Topic: PRINCE2 Agile Processes and Workshops
During Managing product delivery, a team reaches the end of a timebox. It shows stakeholders the user stories that meet the Definition of Done and collects feedback on the delivered products. Which agile workshop is being described?
Best answer: B
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: This describes a review workshop. In PRINCE2 Agile, a review is used to inspect completed products or user stories at the end of a timebox and obtain stakeholder feedback based on what has been delivered.
The key clue is that the team is showing completed user stories that satisfy the Definition of Done and is collecting feedback from stakeholders. That is the purpose of a review workshop: to inspect the product increment produced during the timebox and confirm whether it meets expectations.
A retrospective is different because it focuses on how the team worked, not on the delivered product itself. Planning is about agreeing upcoming work, and a stand-up is a short coordination meeting during delivery. In this case, the delivery information from completed stories and the Definition of Done points directly to a review.
A review examines completed work at the end of a timebox and gathers stakeholder feedback on the product increment.
Topic: Agile Mindset and Change Management
In PRINCE2 Agile, what is the main reason agile maturity matters in an agile transformation?
Best answer: C
What this tests: Agile Mindset and Change Management
Explanation: Agile maturity matters because agile capability develops progressively as people, teams, and the organization learn new ways of working. In PRINCE2 Agile, this supports realistic expectations for transformation and ongoing improvement.
Agile maturity is a success factor because becoming agile is not a one-time switch. In PRINCE2 Agile, capability develops over time as teams build skills, adopt agile behaviors, improve collaboration, and embed the agile mindset more consistently across the organization. This matters at Foundation level because it explains why agile transformation should be seen as progressive improvement, not instant perfection.
The other options describe different concepts, not the reason agile maturity is important.
Agile maturity matters because teams and organizations become more capable incrementally, not instantly.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project manager needs a planning artifact that gives a project-level view of when groups of products are expected to be delivered, while leaving detailed day-to-day planning to the agile team. What is the purpose of a release map?
Best answer: D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: A release map is used for project-level planning in PRINCE2 Agile. It shows an overall view of when scope is expected to be delivered through releases, rather than managing the team’s detailed iteration tasks.
In PRINCE2 Agile, a release map helps bridge project-level planning and agile delivery. Its purpose is to provide a high-level view of how scope is expected to emerge over time through planned releases. This supports forecasting and communication at the project level without replacing the team’s more detailed planning artifacts.
The agile team still manages short-term delivery detail separately, such as work for the current iteration. A release map is therefore about timing and sequencing of expected delivery at a higher level, not task tracking, quality definition, or estimation technique. The key distinction is that it supports project visibility, while team-level artifacts support day-to-day delivery control.
A release map is a project-level planning artifact used to show the forecast delivery of scope across releases over time.
Topic: Agile Mindset and Change Management
On a PRINCE2 Agile project, the project manager wants a project-level view of remaining work, while the delivery team needs a detailed list of features for upcoming iterations. Which TWO statements are correct? Select TWO.
Correct answers: B, D
What this tests: Agile Mindset and Change Management
Explanation: The product backlog is the delivery-focused list of detailed features or user stories. The project backlog is a higher-level project view of remaining work, used for oversight across the whole project rather than replacing team planning.
The main distinction is level and purpose. A product backlog supports agile delivery, so it contains detailed items such as features or user stories that a team can refine, prioritize, and use for upcoming iterations. A project backlog sits at a higher level and gives the project manager a broader view of what remains to be delivered across the project. This helps coordinate and monitor work across releases or stages.
The project backlog does not replace the delivery team’s backlog, because teams still need detailed items for day-to-day planning. Likewise, stage authorization is a governance activity and is not the main purpose of a product backlog. The key contrast is delivery detail versus project-level oversight.
A product backlog is the detailed, prioritized list of features or user stories used to support delivery.
A project backlog provides a broader project-level view of remaining work to support management oversight.
Topic: PRINCE2 Agile Principles and Practices
Exhibit: Visible work board
In Progress: 5 items
Blocked: 2 items
- API access not available
- Supplier answer overdue
Review note: work is starting to queue
In PRINCE2 Agile, which TWO statements are correct about how this visible agile work management supports the Issues practice? Select TWO.
Correct answers: B, D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: Visible agile work management, such as a team board or Kanban-style board, helps people see blocked items and queues quickly. That supports the PRINCE2 Agile Issues practice because issues can be identified early and then managed before they affect delivery more seriously.
In PRINCE2 Agile, visible work management helps make problems transparent. When blocked items, overdue dependencies, or growing queues appear on a board, the team and project roles can see that something is affecting the flow of work. This supports the Issues practice by helping identify issues early and by prompting timely discussion, action, and, if needed, escalation.
Visibility is helpful, but it does not replace issue management. A board shows that a problem exists; the issue still needs to be considered and handled appropriately to protect delivery and project objectives. The key point is that visible work management surfaces issues quickly, while the Issues practice ensures they are managed in a controlled way.
Visible work management makes blocked work and bottlenecks easy to spot, so issues can be addressed quickly.
The Issues practice is concerned with surfacing and controlling matters that could affect project delivery and objectives.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project uses agile delivery teams. Which TWO responsibilities typically belong to the Product Owner rather than the project manager? Select TWO.
Correct answers: C, D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, the Product Owner is focused on product value and detailed delivery decisions, especially backlog priorities and requirement clarification. The project manager remains responsible for project-level control, governance, and reporting.
The key distinction is delivery focus versus project-control focus. The Product Owner represents customer need at the team level, helping the team understand what to build next and confirming that completed work is acceptable. That is why backlog prioritization, story clarification, and acceptance of completed work sit with the Product Owner.
A common confusion is to treat backlog decisions as project management work, but in PRINCE2 Agile those decisions support agile delivery rather than project governance.
The Product Owner directs delivery value by ordering backlog items based on business need and priority.
The Product Owner works closely with the team on requirement detail and confirms whether delivered work meets need.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project has three delivery teams. Each team already has its own Product Owner. The project now needs one person to keep priorities aligned across all teams, represent the overall customer view at project level, and maintain a coherent direction for the product. Which role should do this?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The correct role is the Chief Product Owner because the need is to coordinate customer priorities across several teams at the project level. In PRINCE2 Agile, that is wider than the scope of a single team’s Product Owner.
This scenario distinguishes a project-level product leadership role from team-level delivery and support roles. When several delivery teams each have their own Product Owner, the Chief Product Owner provides the overall customer view, aligns priorities across teams, and helps keep the product direction consistent.
A Product Owner typically focuses on one team’s work and backlog decisions. An agile coach supports agile ways of working and team improvement, but does not own cross-team product prioritization. The project executive is accountable for the business case and overall project success, not for managing detailed product priorities across delivery teams.
The key clue is the need to coordinate multiple teams while representing the overall customer perspective.
The CPO coordinates product direction and priorities across multiple teams at project level, where team-level Product Owners already exist.
Topic: PRINCE2 Agile Principles and Practices
An agile team updates a burn chart every day during an iteration. The project board wants a concise view of overall status and only needs escalation if tolerances are forecast to be exceeded. Which statement correctly compares the two progress views in PRINCE2 Agile?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, progress information is presented at different levels for different decisions. Burn charts usually help the delivery team manage short-term work, while the project dashboard summarizes wider project status and supports exception control when tolerances may be exceeded.
The progress practice uses transparency to support control at both delivery level and project level. A team dashboard helps the team inspect and adapt its work frequently, so it can include detailed agile measures such as burn charts. These show how work is progressing within an iteration or release.
A project dashboard is more summarized. It helps the project manager and project board understand overall progress, assess whether tolerances are likely to be exceeded, and decide whether exception action or escalation is needed. Agile delivery does not remove PRINCE2 governance; it adds timely, visible information that improves decision-making.
The key comparison is detailed delivery tracking for the team versus higher-level control and exception visibility for the project.
This matches the progress practice by separating day-to-day team visibility from higher-level project control and exception management.
Topic: Agile Mindset and Change Management
Which TWO statements correctly describe PRINCE2 Agile? Select TWO.
Correct answers: A, C
What this tests: Agile Mindset and Change Management
Explanation: PRINCE2 Agile is a blend of PRINCE2 governance and agile delivery, not just agile delivery on its own. It keeps project-level direction, control, and accountability while enabling agile teams to work with iterative and collaborative delivery approaches.
PRINCE2 Agile combines the PRINCE2 project management method with agile delivery approaches. The key idea is that governance, direction, and control still exist at the project level, while delivery teams can use agile practices and behaviors to create products iteratively. This is different from generic agile delivery, which usually focuses mainly on team-level ways of working such as backlog management, iteration, and collaboration. PRINCE2 Agile therefore adds a project governance layer around agile delivery instead of replacing governance with agile team autonomy alone. The main distinction is that PRINCE2 Agile bridges project management and agile delivery rather than acting as a stand-alone agile method.
PRINCE2 Agile is defined by blending PRINCE2 governance with agile delivery ways of working.
PRINCE2 Agile connects PRINCE2 management and governance to agile delivery at team level.
Topic: PRINCE2 Agile Processes and Workshops
Exhibit: Workshop note
Timing: very early in the project
Purpose: align vision, expectations, and ways of working
Participants: key stakeholders and team representatives
Next step: move into more detailed planning
Which agile workshop does this note describe?
Best answer: A
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: The decisive clue is the timing and purpose: it happens very early and creates shared understanding of the vision and ways of working. In PRINCE2 Agile, that matches a project kick-off workshop supporting Starting up a project.
In PRINCE2 Agile, Starting up a project is supported by workshops that create early alignment and engagement. A project kick-off workshop brings key people together at the beginning of the project to agree a common understanding of the vision, expectations, and how the project will work. The exhibit points to this because it stresses very early timing and shared ways of working before detailed planning begins.
Release planning is about organizing delivery across releases, not broad startup alignment. Retrospectives and daily stand-ups are delivery-cycle events used later to improve or coordinate ongoing work. The key takeaway is that project kick-off helps the project start with shared direction and collaboration.
This is the early workshop used to align vision, expectations, and ways of working at the start of the project.
Topic: PRINCE2 Agile Principles and Practices
During an iteration review, the team reports that a supplier has already missed an agreed delivery date, so planned work cannot start as expected. Why should this be handled as an issue in PRINCE2 Agile?
Best answer: C
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The decisive clue is that the supplier has already missed the delivery date. In PRINCE2 Agile, a risk is uncertain and may happen, but an issue is something that has happened, is happening, or is certain to happen and now needs management attention.
In the Issues practice, the key distinction is certainty. If something is still uncertain, it is managed as a risk. If it has already happened, is currently happening, or is unavoidable, it is managed as an issue. In the scenario, the missed delivery is no longer a possibility; it is a current fact affecting planned work. That makes issue handling appropriate because the focus is on deciding and tracking the response now.
A useful test is:
The closest distractor is the option about uncertainty, but that applies only before the missed delivery actually occurs.
An issue is used when the event has already occurred, so the immediate concern is how to respond and manage the impact.
Topic: PRINCE2 Agile Principles and Practices
Which TWO statements correctly describe the team coach role in PRINCE2 Agile? Select TWO.
Correct answers: C, D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The team coach supports the delivery team by coaching, facilitating, and improving agile ways of working. The role influences how the team works and develops, rather than owning backlog priorities or providing project administration.
In PRINCE2 Agile, the team coach is a delivery-focused coaching role. Its main contribution is to help the team work effectively using agile practices, strengthen collaboration, and support continuous improvement. This means the role influences team behaviour, facilitation, and the way work is carried out.
The team coach is different from nearby roles:
So, the team coach is primarily concerned with helping the team become more effective in agile delivery, not with product prioritization or project administration.
The team coach helps the team use agile ways of working effectively and improve how it collaborates and delivers.
The team coach focuses on day-to-day team effectiveness, while an agile coach supports wider agile change and capability.
Topic: PRINCE2 Agile Principles and Practices
A project board insists that the delivery date and budget remain unchanged, but agrees that lower-priority requirements can be adjusted as the team learns more during delivery. Which PRINCE2 Agile concept does this describe?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: This describes fix and flex. The clue is that project-level control is kept by fixing date and budget, while agile responsiveness is achieved by flexing lower-priority scope as delivery progresses.
In PRINCE2 Agile, fix and flex is the idea of fixing certain constraints to maintain project management control while allowing flexibility elsewhere to support agile delivery. In this example, the fixed delivery date and budget provide control, and the ability to adjust lower-priority requirements provides responsiveness. That balance is the defining clue.
MoSCoW can help decide which requirements may move, but it is only a prioritization technique. Timeboxing fixes a period of time, but the stem is about the broader balancing approach between control and flexibility. MVP focuses on the smallest usable outcome, not specifically on fixing constraints while flexing scope.
The key takeaway is that fixed governance constraints plus flexible lower-priority scope points to fix and flex.
This is fix and flex because key constraints stay fixed while less critical scope can vary to keep agility within control.
Topic: PRINCE2 Agile Processes and Workshops
A project executive is considering a PRINCE2 Agile project to introduce a customer portal. Before spending much effort, the organization wants to confirm the idea is worth taking forward and appoint the key people. If the project proceeds, it then wants firmer controls, plans, and management information for delivery. Which statement best compares the two processes?
Best answer: B
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: Starting up a project is the early pre-project process used to confirm there is a worthwhile basis to proceed and to appoint key roles. Initiating a project follows that decision and establishes the project on a firm basis with the controls, plans, and management information needed for delivery.
In PRINCE2 Agile, these two processes have different purposes. Starting up a project happens first and is deliberately lightweight. It checks whether there is a viable and worthwhile project to initiate, appoints key people, and gathers enough information to request authorization for the initiation stage. Initiating a project comes next if that decision is positive. Its purpose is to establish solid foundations for the project by developing the Business Case, controls, management approaches, and plans needed for governance and delivery. In this scenario, the first need is the early decision about whether to proceed at all; the later need is the fuller setup for controlled project delivery. Agile delivery techniques do not remove this distinction.
This matches the PRINCE2 Agile distinction between the pre-project viability check and the later establishment of firm project foundations.
Topic: PRINCE2 Agile Processes and Workshops
A PRINCE2 Agile project is at the end of a stage. The project executive has received both a project dashboard and a team dashboard from the agile delivery team. Which action best reflects the purpose of Directing a project?
Best answer: D
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: In PRINCE2 Agile, Directing a project is about governance decisions such as authorizing stages and giving overall direction. Agile information supports those decisions, but governance should stay at the project level and avoid taking over day-to-day team delivery.
The key distinction is between project governance and team delivery. In the Directing a project process, the project executive or project board uses summarized information, such as a project dashboard, to judge continued business justification, overall progress, risk, and whether to authorize the next stage. PRINCE2 Agile welcomes agile information, but it uses it at the right level.
A team dashboard, backlog detail, retrospective actions, and task assignment belong to the delivery level. Those help the team and delivery roles manage work inside iterations and releases. Governance should be informed by agile data without stepping into detailed control of how the team delivers.
The main takeaway is that Directing a project uses agile information for oversight and authorization, not for managing the team’s daily work.
Directing a project is a governance process, so the project executive uses summarized agile information to make authorization decisions rather than manage team delivery.
Topic: PRINCE2 Agile Processes and Workshops
Which PRINCE2 Agile process matches this description?
The project manager confirms product acceptance, supports transition to operational use, gathers review and retrospective results, captures lessons, and recommends that the project be closed in a controlled way.
Best answer: C
What this tests: PRINCE2 Agile Processes and Workshops
Explanation: This description matches Closing a project. In PRINCE2 Agile, controlled closure includes confirming acceptance, enabling handover or transition, reviewing performance and lessons, and preparing the recommendation to close the project formally.
Closing a project is the PRINCE2 Agile process used when the work is finishing and the project needs to be shut down in a controlled manner. It checks that the required products have been accepted, that transition to operational use or ongoing support is arranged, and that review information is collected. In an agile context, this can include outputs from reviews and retrospectives to help confirm what was delivered and what was learned.
The process also ensures lessons are captured for future work and provides the information needed for a formal closure recommendation. The key idea is not just stopping delivery, but closing with acceptance, transition, review evidence, and lessons in place. A nearby distractor is Managing a stage boundary, which is about moving between stages, not ending the whole project.
This process focuses on confirming acceptance, arranging transition, recording lessons, and recommending formal project closure.
Topic: PRINCE2 Agile Principles and Practices
A delivery team is about to start a user story in the next iteration. The story exists in the product backlog, but its acceptance criteria are unclear and the developer and tester have different views of what is needed. Which response is most appropriate?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The decisive clue is that the team has not yet started work and lacks a shared understanding of the story. Definition of Ready is used to check that an item is sufficiently clear and ready before the team begins.
Definition of Ready is a quality-related agreement used before work starts. It helps the team confirm that a user story or backlog item is understood well enough to begin, including clarity about what is needed and how it will be accepted. In this scenario, the acceptance criteria are unclear and team members interpret the work differently, so the problem is readiness, not completion or reporting.
A Definition of Done is used to confirm that work has been completed to the required standard. Dashboards help show status and progress, and escalation is for matters needing higher-level attention. The key point is that the team first needs enough shared understanding to start the work properly.
Definition of Ready helps confirm that a backlog item is understood well enough to begin work with shared expectations.
Topic: Agile Mindset and Change Management
Which TWO statements show the effect of an agile mindset on team learning, feedback, and adaptation in PRINCE2 Agile? Select TWO.
Correct answers: A, B
What this tests: Agile Mindset and Change Management
Explanation: An agile mindset supports short feedback loops and continuous learning. In PRINCE2 Agile, this is seen in retrospectives that improve team working and in review feedback that updates the product backlog.
Being agile means using learning and feedback throughout delivery, not waiting until the end of the project. In PRINCE2 Agile, teams inspect and adapt regularly. Retrospectives help the team improve how it works, while reviews provide feedback on products and can lead to updates in the product backlog. This shows that adaptation is expected and useful when it improves value and learning. By contrast, delaying learning until project closure or treating plans as fixed would reflect a more predictive mindset, not an agile one. The key idea is continuous learning with controlled adaptation.
An agile mindset encourages regular reflection so the team can learn and adapt continuously.
An agile mindset values feedback, so backlog items can be refined or reprioritized as learning emerges.
Use the PRINCE2 Agile Foundation Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PRINCE2 Agile Foundation guide on PMExams.com for concept review, then return here for PM Mastery practice.