Prepare for PRINCE2 Agile Foundation (Version 2) with free sample questions, a 40-question full-length diagnostic, topic drills, timed mock exams, PRINCE2 control, agile concept, tailoring, prioritization, governance-plus-delivery fit scenarios, and detailed explanations in PM Mastery.
Start a practice session for PRINCE2 Agile Foundation (Version 2) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same app-family account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same PM Mastery account you use on web. The same PM Mastery subscription works across web and mobile.
Free diagnostic: Try the 40-question PRINCE2 Agile Foundation full-length practice exam before subscribing. Use it to see whether your misses come from PRINCE2 controls, agile concepts, tailoring, prioritization, or governance-plus-delivery fit.
PRINCE2 Agile Foundation (Version 2) is the entry PeopleCert route for learners who need PRINCE2 governance language plus agile delivery concepts in the same certification path. Use this page to confirm whether the PRINCE2 Agile lane fits better than classic PRINCE2, Scrum, or SAFe before moving into full PM Mastery practice.
PeopleCert’s current public page lists this assessment as PRINCE2 Agile Foundation (Version 2), and its public naming update maps PRINCE2 Agile to PRINCE2 Agile Version 2. If you searched for the older PRINCE2 Agile Foundation version 1 route: This route has been replaced or renamed. Use this page to choose the current equivalent.
Official source check: Last checked May 5, 2026 against PeopleCert's PRINCE2 Agile Foundation Version 2 product page.
PeopleCert lists PRINCE2 Agile Foundation Version 2 as a 40-question, 60-minute, closed-book multiple-choice exam with a 60% passing score. Confirm current language availability, booking, and delivery details directly with PeopleCert before scheduling.
PRINCE2 Agile Foundation questions usually reward the choice that preserves PRINCE2 control while still enabling agile delivery, collaboration, and adaptation. Weak answers usually force one side to eliminate the other.
| Scenario signal | First check | Strong answer usually… | Weak answer usually… |
|---|---|---|---|
| Agile delivery seems to conflict with governance | Which PRINCE2 control must remain | Keeps justification, roles, tolerances, quality, and escalation while using agile delivery practices | Removes PRINCE2 control because the team is agile |
| Time or capacity is fixed | Prioritization and tolerance | Uses prioritization to protect essential outcomes and manage flexibility | Treats all scope as equally mandatory |
| Stakeholders want frequent feedback | Transparency and product focus | Uses reviews, information radiators, and collaboration to improve control | Adds status reports without learning |
| Agile suitability is uncertain | Context and risk | Checks team capability, uncertainty, stakeholder access, and delivery environment | Assumes agile practices always fit |
| A term sounds Scrum-specific | PRINCE2 Agile fit | Connects the agile concept to project governance and product delivery | Answers as if this were only a Scrum exam |
| Area | What the exam tests | What PM Mastery practice should force | Common trap |
|---|---|---|---|
| PRINCE2 control | Whether governance still applies in agile settings | Recognize which controls remain non-negotiable | Thinking agile means no governance |
| Agile delivery | Whether agile concepts support adaptation and feedback | Connect agile practices to project control | Memorizing agile terms without context |
| Tailoring | Whether the method is adapted proportionately | Choose fit-for-context controls and practices | Copying one delivery model into every project |
| Prioritization | Whether scope flexibility is used deliberately | Protect must-have outcomes under constraints | Letting every request become mandatory |
If you want concept-first reading before heavier simulator work, use the companion PRINCE2 Agile Foundation Version 2 Study Guide on PMExams.com. Then return here for timed mocks, topic drills, explanations, and the full PM Mastery practice route.
Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.
Try these 24 public sample questions for PRINCE2 Agile Foundation V2. They are original PM Mastery practice items aligned to PRINCE2 Agile principles, behaviours, tailoring, governance, and delivery decisions. They are not PeopleCert exam questions and are not copied from any exam sponsor.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
During an iteration, the team discovers that a supplier has delivered the wrong interface component, and two user stories are now blocked. Which statement BEST describes this in PRINCE2 Agile?
Best answer: A
Explanation: The blocked stories are caused by a problem that has already occurred, so this is an issue, not a risk. In PRINCE2 Agile, current problems are captured and handled through the issues practice.
The issues practice in PRINCE2 Agile is used to identify, assess, and control matters that need attention, especially current problems. In this scenario, the wrong component has already been delivered and is already blocking work, so the situation is an issue. A risk is different because it is uncertain and may happen in the future.
Agile teams should expose problems quickly, but visibility tools do not replace the practice itself. The issue still needs to be captured and managed appropriately.
The key distinction is simple: something happening now is an issue; something that might happen later is a risk.
The problem has already happened, so PRINCE2 Agile treats it as an issue to be identified, assessed, and controlled.
Topic: PRINCE2 Agile processes, agile workshops, and application
In PRINCE2 Agile, which process uses early agile collaboration to shape the initial understanding of the project before deciding whether to begin full initiation?
Best answer: D
Explanation: Starting up a project is the PRINCE2 Agile process used to form the initial view of the project and confirm that it is worthwhile to proceed. Early agile collaboration helps create shared understanding before the project moves into detailed initiation work.
The core concept is the purpose of the Starting up a project process. In PRINCE2 Agile, this process is used at the beginning of the project to establish whether there is a sensible basis to start and to create an initial understanding of what the project is about. Early agile collaboration, such as short workshops or discussions with key stakeholders and delivery people, helps build that shared understanding quickly and realistically.
This is different from later processes that manage detailed planning, stage control, or product delivery. The key point is that starting up a project happens before full initiation and helps shape the project from the outset.
This process establishes the project’s initial basis and can use early agile collaboration to clarify scope, approach, and viability.
Topic: PRINCE2 Agile processes, agile workshops, and application
During a stage, a project manager wants frequent visibility of completed work, work in progress, and blockers so that progress can be monitored and quick decisions can be made. Which agile workshop most directly provides this support?
Best answer: B
Explanation: The key clue is the need for frequent visibility during the stage. A daily stand-up is the workshop used to surface current progress, work in progress, and blockers so the project manager can monitor the stage and act quickly if needed.
In PRINCE2 Agile, Controlling a stage needs timely information about current delivery status so progress can be monitored and decisions can be made quickly. The daily stand-up is designed for this purpose because it provides short, frequent updates on what has been done, what is being worked on, and what is blocked. That makes it a strong source of current information for stage control.
By contrast, other workshops have different purposes:
The decisive clue is the need for ongoing monitoring during the stage, not future planning or end-of-iteration reflection.
A daily stand-up gives frequent, short updates on progress and impediments, which directly supports stage monitoring and prompt decisions.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
A PRINCE2 Agile project has several delivery teams, each with its own Product Owner. To support the Organization practice purpose of clear responsibilities and communication, one role coordinates product decisions across the teams and links them to project-level governance. Which role is this?
Best answer: A
Explanation: The role described is the Chief Product Owner. In PRINCE2 Agile, this role helps connect agile delivery decisions with project-level governance when there are multiple teams or Product Owners.
In the PRINCE2 Agile Organization practice, roles and responsibilities are defined so governance and agile delivery work together clearly. The Chief Product Owner sits above individual Product Owners when needed and keeps product direction consistent across teams. This helps project-level governance receive a coherent view of priorities, scope, and value while allowing delivery teams to work in an agile way.
A Product Owner usually focuses on one team or one area of product decision-making. An agile coach supports agile working and team development, and the project manager coordinates the project overall. The key distinction is that the Chief Product Owner provides the product-focused link across multiple teams into governance.
The Chief Product Owner aligns multiple Product Owners and provides the main product link between agile delivery teams and project-level governance.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
Which PRINCE2 Agile term refers to a governance role that provides independent confidence to the project board, rather than a team-level collaboration technique?
Best answer: A
Explanation: Project assurance is part of the PRINCE2 Agile Organization practice and supports governance by giving the project board an independent view of how the project is being run. The other options are agile team techniques or artifacts used to help delivery teams collaborate and manage work.
In PRINCE2 Agile, role clarity is important because governance responsibilities must stay distinct from team-level delivery activities. Project assurance is a governance role that checks the project is being conducted properly and gives the project board confidence that controls, quality, and progress are appropriate. That is different from agile collaboration techniques, which help the team coordinate work and improve delivery.
A daily stand-up is a short team coordination event. A retrospective is a team improvement workshop. A Kanban board is a visual workflow tool. These support collaboration and transparency within delivery, but they do not provide independent governance assurance to the project board.
The key distinction is whether the term describes project governance oversight or team collaboration in day-to-day delivery.
Project assurance is a governance role that independently checks the project’s conduct and supports the project board with confidence in control and progress.
Topic: Agile mindset, project management, and organizational change management
In PRINCE2 Agile, what is a timebox?
Best answer: B
Explanation: A timebox is a fixed period of time used in PRINCE2 Agile for iterations, releases, and stages. Its purpose is to maintain control and focus by protecting the timeframe and managing work within it.
In PRINCE2 Agile, a timebox is a fixed duration used to organize work at different levels, such as an iteration, a release, or even a stage. The key idea is that the time available is set first, which helps teams stay focused and gives management a clear control point. Rather than extending the end date easily, the work is managed to fit within the agreed period.
This differs from nearby concepts such as a backlog, which is a list of work, or a burn chart, which is a reporting tool. It also differs from tolerance, which is an allowed deviation, not the planned time period itself.
The main takeaway is that timeboxing fixes the timeframe to support pace, control, and delivery focus.
A timebox is a set duration used to create focus and control, with work managed to fit the fixed timeframe.
Topic: Agile mindset, project management, and organizational change management
During project initiation, the project manager says, “We must apply the fundamental requirements that determine whether this is genuinely a PRINCE2 project, whatever delivery approach we use.” Which PRINCE2 Project Management integrated element is being described?
Best answer: D
Explanation: The clue is “fundamental requirements” that determine whether a project is genuinely using PRINCE2. In PRINCE2 Project Management, that description matches the principles, not the practices, processes, or project context.
PRINCE2 Project Management is structured around integrated elements, including principles, people, practices, processes, and project context. The principles are the core, universal requirements of PRINCE2. They are the decisive clue whenever the wording refers to what must be applied for a project to be recognized as a PRINCE2 project.
Practices describe aspects of project management that need ongoing attention, such as business case, risk, or quality. Processes describe the lifecycle progression of the project. Project context refers to the environment and circumstances surrounding the project. So when the stem focuses on fundamental requirements that define PRINCE2 use, the correct match is principles.
Principles are the fundamental requirements that must be applied for a project to be considered a PRINCE2 project.
Topic: PRINCE2 Agile processes, agile workshops, and application
A PRINCE2 Agile project has completed its current stage. The project is expected to continue, and the Project Board needs updated information to decide whether to authorize the next stage. Which process should be used?
Best answer: A
Explanation: When a project is continuing beyond the current stage, PRINCE2 Agile uses Managing a stage boundary to prepare updated information for governance decisions. Closing a project is only used when the whole project is ending, not when another stage may follow.
The key distinction is purpose. Managing a stage boundary is used when one stage is ending but the project itself is not necessarily finished. It prepares the information the Project Board needs, such as performance information and planning for what comes next, so the Board can decide whether to authorize another stage.
Closing a project is different because it is used when the entire project is ending. Its purpose is to confirm product acceptance, evaluate performance, and bring the project to an orderly close. In this scenario, the project is expected to continue, so the appropriate process is the one that supports an end-of-stage decision rather than final project closure.
A common confusion is with Directing a project: that process contains the Board’s decision-making, but the end-of-stage preparation is done in Managing a stage boundary.
This process is used at the end of a stage to provide the Project Board with the information needed to decide on the next stage.
Topic: Agile mindset, project management, and organizational change management
Which TWO statements correctly distinguish popular agile approaches from PRINCE2 Agile? Select TWO.
Best answer: B
Explanation: PRINCE2 Agile is not a separate agile delivery method like Scrum or Kanban. It is a way to combine PRINCE2 project management and governance with agile delivery approaches, so methods such as Scrum and Kanban can be used inside a PRINCE2 Agile project.
The key distinction is purpose. Popular agile approaches such as Scrum and Kanban mainly help teams organize and deliver work in an agile way. PRINCE2 Agile provides project management, governance, and control while allowing agile delivery techniques to be used where appropriate.
In Foundation terms:
A common confusion is to treat PRINCE2 Agile as if it were just another delivery framework, when its role is broader than that.
Scrum is an agile delivery approach, while PRINCE2 Agile provides the project management and governance context around such delivery.
Topic: PRINCE2 Agile processes, agile workshops, and application
A governance note says the Project Board will authorize initiation, each stage, and project closure, while delegating day-to-day management to the project manager. Which PRINCE2 Agile process purpose is being described?
Best answer: D
Explanation: The decisive clue is the Project Board authorizing initiation, stages, and closure. In PRINCE2 Agile, that describes Directing a project, which is about overall governance and key decision-making rather than day-to-day management.
Directing a project is the PRINCE2 Agile process in which the Project Board exercises overall control and makes key decisions for the project. The strongest clue in the stem is that the Project Board authorizes initiation, stage progression, and project closure. Those are governance decisions, not delivery-management activities.
By contrast, the project manager handles day-to-day management during a stage, and information for end-of-stage decisions is prepared elsewhere before being submitted to the Project Board. The key takeaway is that when the Board is making authorization decisions at major control points, the process purpose is Directing a project.
This is the Project Board governance process that authorizes key points in the project while leaving day-to-day control to the project manager.
Topic: Agile mindset, project management, and organizational change management
In PRINCE2 Agile, t-shirt sizing provides a quick, high-level estimate of the ____ size of backlog items.
Best answer: D
Explanation: T-shirt sizing is a simple agile estimation technique used to compare work items at a high level. Its purpose is to show relative size quickly, not to calculate exact duration or cost.
T-shirt sizing uses labels such as small, medium, large, and extra large to compare backlog items. In PRINCE2 Agile, this helps teams form a fast, shared view of how big items are relative to one another. It is useful early on or when detailed estimation is unnecessary, because it supports quick discussion and prioritization without implying precision. The key distinction is that it is comparative and approximate, unlike exact time-based or cost-based estimates.
A common Foundation-level use is to size user stories or backlog items before more detailed planning. The main takeaway is that t-shirt sizing is for relative estimation, not precise forecasting.
T-shirt sizing compares items with each other, so it estimates relative size rather than exact time, cost, or effort.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
When feedback from early releases changes the view of expected benefits, the ____ should be reviewed to confirm continued business justification.
Best answer: A
Explanation: In PRINCE2 Agile, feedback from early delivery can change understanding of value and benefits. When that happens, the business case should be reviewed because it is the basis for continued business justification.
The key clue is the change in expected benefits. In PRINCE2 Agile, agile feedback from early releases, reviews, or user responses can improve understanding of what value will actually be delivered. Because the business case explains why the project remains worthwhile, any material change to expected benefits may affect whether the project still has valid business justification.
A product backlog may change to reflect new priorities, but that does not replace reviewing the business case. Quality definitions and dashboards also support delivery, yet they do not determine whether the project continues to be justified. The main takeaway is that changes in benefit understanding point first to the business case.
The business case is reviewed when agile feedback changes expected benefits because it supports continued business justification.
Topic: PRINCE2 Agile processes, agile workshops, and application
A project is nearing the end of a stage. The project manager reviews learning from retrospectives, checks product progress against the release map, and updates forecasts before seeking approval for the next stage.
Which statement best explains why this work belongs to managing a stage boundary rather than controlling a stage?
Best answer: A
Explanation: Managing a stage boundary focuses on looking ahead from the end of one stage to the next. In PRINCE2 Agile, learning, updated forecasts, and evidence of product progress are used to decide whether the next stage remains viable and ready for authorization.
The key feature of managing a stage boundary is that it bridges one stage to the next. At this point, the project manager uses what has been learned, reviews actual product progress, and refreshes forecasts so the next stage can be planned and presented for approval. In an agile context, sources such as retrospectives, release information, and backlog or product progress help inform that view.
By contrast, controlling a stage is mainly about monitoring and directing the current stage, not preparing the formal basis for the next one.
Managing a stage boundary uses current-stage learning and updated forecasts to support planning and approval of the next stage.
Topic: Agile mindset, project management, and organizational change management
Which TWO statements correctly describe the PRINCE2 principle learn from experience in an agile context? Select TWO.
Best answer: A
Explanation: In PRINCE2 Agile, learn from experience still applies fully. Agile reviews, feedback, and retrospectives create frequent opportunities to capture lessons and use them during the project, not just at the end.
The PRINCE2 principle learn from experience means lessons are sought, recorded, and acted on throughout the project lifecycle. In an agile context, this connects strongly to feedback loops such as reviews and retrospectives, because these events regularly reveal what is working well and what should change. Agile delivery does not replace the principle; it reinforces it by creating more frequent learning points. PRINCE2 expects teams to consider lessons from previous work at the start and to continue learning as the project progresses. The key idea is continuous improvement based on evidence from experience, not waiting until closure to reflect.
A common confusion is to assume agile ceremonies make the principle unnecessary, when in fact they are practical ways to support it.
Retrospectives are a direct agile mechanism for capturing and using lessons, which supports learn from experience.
Topic: PRINCE2 Agile processes, agile workshops, and application
Complete the statement.
In PRINCE2 Agile, when senior decision-makers need to inspect the latest product increment before deciding on continued investment, the most relevant agile workshop is a ____.
Best answer: A
Explanation: A review workshop is used to inspect delivered work and gather feedback on the latest increment. That makes it the best fit for supporting Directing a project, where senior decision-makers need visible evidence before authorizing continued investment.
In PRINCE2 Agile, Directing a project is concerned with senior-level governance and decision-making rather than day-to-day team coordination. A review workshop supports this by showing completed or evolving product increments to key stakeholders so they can assess progress, quality, and value. In the scenario, the decisive clue is that senior decision-makers want to inspect the latest product increment before deciding whether to continue funding. That is exactly the purpose of a review workshop. Retrospectives focus on improving how the team works, daily stand-ups coordinate daily activity, and planning workshops prepare future work rather than provide governance-level inspection of delivered outcomes.
A review workshop gives senior decision-makers visible evidence of the latest increment so they can support governance decisions in Directing a project.
Topic: PRINCE2 Agile integration in the wider context
Before handing over a product from an agile project to operations, the project should confirm ____ so that support, training, and service arrangements are in place.
Best answer: D
Explanation: In PRINCE2 Agile, transition to operations is not just about finishing the product. The project also needs evidence that the operational environment can accept and support it, which is covered by operational readiness.
Operational readiness is the check that the live environment is prepared for acceptance and handover. It typically includes the information and arrangements needed for support, training, service management, documentation, and ongoing use so that the product can deliver continued value after the project hands it over.
By contrast, Definition of Done shows when a product increment is complete to the agreed quality level, but it does not prove that operations can run it. A release map helps plan releases over time, and retrospective findings help improve the team’s way of working. A product may be done for delivery but still not be ready for operations.
Operational readiness confirms the receiving operational area is prepared to accept, support, and use the product.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
In the PRINCE2 Agile Plans practice, which TWO statements correctly describe how story points and t-shirt sizing support agile estimation? Select TWO.
Best answer: A
Explanation: Story points and t-shirt sizing help teams estimate work relatively rather than precisely. In PRINCE2 Agile, that relative sizing supports the Plans practice by helping forecast what backlog scope may fit into releases or timeboxes.
The core idea is that story points and t-shirt sizing are agile estimation techniques for comparing the relative size or effort of backlog items. They do not aim to produce exact task durations for every item. In PRINCE2 Agile, this supports the Plans practice because relative estimates help the team and project manager discuss likely delivery scope and use artifacts such as the release map more effectively.
Relative estimates are useful because they:
A close distractor is the idea that estimates must be converted into exact days, but PRINCE2 Agile uses these techniques mainly to support forecasting and planning decisions, not detailed certainty.
Story points and t-shirt sizes are relative estimation techniques used to compare the size of backlog items.
Topic: PRINCE2 Agile processes, agile workshops, and application
In PRINCE2 Agile, which agile artifact is commonly used during Initiating a project to capture and refine the project’s high-level foundation in a collaborative workshop?
Best answer: A
Explanation: The project canvas is the agile artifact used to capture the project’s core elements at a high level during initiation. It supports workshop-based discussion so the project foundation can be explored, clarified, and refined early.
In PRINCE2 Agile, Initiating a project establishes a clear and shared foundation for the work ahead. A project canvas helps do this by bringing key project information together in a simple, visual form that can be discussed and refined in a workshop. It supports early alignment on areas such as purpose, scope, stakeholders, benefits, and delivery approach.
This makes it well suited to the initiation stage, where the aim is to build a solid basis for governance and delivery without creating unnecessary detail too early. By contrast, artifacts such as a product backlog or release map support delivery planning in more specific ways, while dashboards are used more for reporting and tracking progress. The key distinction is that the project canvas helps shape the overall project foundation.
The project canvas is used to summarize and refine the project’s high-level foundation collaboratively during initiation.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
In PRINCE2 Agile, what is the main role of the risk practice when frequent agile feedback is available?
Best answer: B
Explanation: In PRINCE2 Agile, the risk practice is about managing uncertainty. Frequent agile feedback from reviews, demos, and similar events can reveal new threats or opportunities, so risk understanding is updated continually rather than only at fixed points.
The PRINCE2 Agile risk practice focuses on identifying, assessing, and controlling uncertainty. In an agile context, frequent feedback loops make this especially dynamic because each review, demonstration, or iteration can provide new evidence about what is or is not risky. This means risks may be discovered earlier, existing risks may change in probability or impact, and some risks may reduce as learning increases. The key idea is that agile feedback does not replace risk management; it strengthens it by improving visibility and enabling ongoing reassessment.
A close distractor is progress measurement, which also uses frequent information, but that is about status and delivery performance rather than uncertainty itself.
The risk practice manages uncertainty, and frequent agile feedback helps refine the understanding of risks throughout the project.
Topic: PRINCE2 Agile processes, agile workshops, and application
A PRINCE2 Agile project is approaching closure.
Workshop notes
- Confirm final product acceptance
- Review what helped and hindered delivery
- Capture lessons for future work
Which TWO agile workshops are most clearly supporting closing a project? Select TWO.
Best answer: A
Explanation: Closing a project in PRINCE2 Agile includes confirming acceptance and capturing lessons. The workshop notes point directly to a review workshop for acceptance and a retrospective for reflection and learning.
In PRINCE2 Agile, closing a project is supported by agile workshops that help confirm what has been delivered and capture learning from the work. The decisive clues in the notes are final product acceptance and reviewing what helped or hindered delivery. Those are typical purposes of a review workshop and a retrospective.
A review workshop focuses on showing delivered products to stakeholders and confirming acceptance. A retrospective focuses on reflecting on how the team worked and identifying lessons for future use. By contrast, a daily stand-up supports day-to-day coordination during delivery, and a release planning workshop looks ahead to future delivery rather than project closure.
A retrospective supports project closure by reviewing performance and capturing lessons learned.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
A PRINCE2 Agile project is preparing the next iteration. The team is uncertain whether a new external service can be integrated within the release timebox, and the project manager wants information to support a risk decision.
Which TWO items are most appropriate for the risk practice? Select TWO.
Best answer: A
Explanation: The best choices are the items that directly help identify, assess, or reduce uncertainty in the PRINCE2 Agile risk practice. A risk register captures the risk formally, and a spike is an agile technique used to learn more and lower uncertainty before committing further work.
In PRINCE2 Agile, the risk practice focuses on understanding uncertainty and deciding how to respond to it. In this scenario, the uncertainty is whether the external service can be integrated within the release timebox. A risk register supports this by documenting the risk clearly, including its cause, event, effect, and response. A spike supports the same need from an agile perspective by creating a short, timeboxed investigation to learn more and reduce uncertainty.
The other items are useful in PRINCE2 Agile, but they serve different practices. Definition of Done mainly supports quality, and a burn chart mainly supports progress tracking. The key distinction is whether the item directly supports risk identification, assessment, or reduction.
A risk register is a PRINCE2 risk artifact used to record and manage uncertainty and planned responses.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
In PRINCE2 Agile, the quality practice uses the ____ to confirm that a backlog item is clear, testable, and ready to enter delivery.
Best answer: A
Explanation: The missing term is Definition of Ready. In PRINCE2 Agile, this supports the quality practice by checking whether work is sufficiently understood before delivery begins, whereas completion is confirmed later by the Definition of Done.
PRINCE2 Agile uses the quality practice to make expectations visible before, during, and after delivery. A Definition of Ready helps a team confirm that a backlog item has enough clarity, testability, and shared understanding to be taken into delivery work. This improves flow and reduces rework caused by starting items too early.
By contrast, a Definition of Done is used at the end of delivery to confirm that the work is complete and meets agreed completion criteria. Acceptance criteria describe what must be true for a specific item, while the quality register records quality-related information at project level. The key distinction is that readiness criteria guide starting work, and completion criteria guide finishing work.
The Definition of Ready sets the agreed readiness checks a backlog item must meet before work starts.
Topic: PRINCE2 Agile integration in the wider context
Which TWO examples show agile product management beyond the project environment? Select TWO.
Best answer: B
Explanation: Agile product management beyond the project environment focuses on the product’s continuing lifecycle, value, and evolution. Clues include ongoing prioritization across releases and decisions driven by customer feedback over time.
The key distinction is whether the activity is about managing the product over its continuing life or managing work inside a specific project. Agile product management beyond the project environment looks beyond project completion and focuses on sustained value delivery, future releases, and ongoing customer needs. A long-lived product backlog is a strong clue because it supports continual enhancement of the product over time. Likewise, prioritizing based on ongoing customer feedback and whole-life value shows product-level thinking. By contrast, approving stage tolerances is project governance, and daily stand-ups are team-level delivery coordination. The best clue is continuity of product ownership, value, and backlog decisions beyond one project boundary.
A long-lived product backlog signals ongoing product management beyond a single project or stage.
Topic: PRINCE2 Agile principles, practices, artifacts, and agile context
A project board wants early evidence that a product idea is worth further investment. In PRINCE2 Agile, creating a ____ helps test viability with the minimum set of features.
Best answer: A
Explanation: The missing term is the artifact used to test whether an idea is worth pursuing with minimal investment. In PRINCE2 Agile, that is the minimum viable product, which directly supports business case thinking and continued business justification.
In the business case practice, PRINCE2 Agile focuses on confirming that the project remains worthwhile. A minimum viable product (MVP) helps do this by delivering the smallest useful version of a product so stakeholders can test viability, value, and learning before committing more investment. That makes it closely linked to decision-making about whether to continue, adjust, or stop work.
A Definition of Done is a quality agreement, while burn charts and dashboards are used for progress visibility. Those are useful in agile delivery, but they do not provide the same direct evidence about whether the product idea itself justifies further investment.
The key point is that MVP supports business case evidence, not just delivery control.
An MVP is used to test whether the product idea is viable while investing only in the minimum useful feature set.
Use this flow when a question asks how PRINCE2 governance and agile delivery can work together. Foundation questions usually reward knowing what remains controlled and where agile practices add flexibility.
flowchart LR
A["Project justification and governance"] --> B["PRINCE2 roles and controls"]
B --> C["Agile delivery context"]
C --> D["Tolerances and prioritization"]
D --> E["Iterative delivery and feedback"]
E --> F["Controlled adaptation"]
| Concept | Foundation use |
|---|---|
| Governance | PRINCE2 controls do not disappear when agile delivery is used. |
| Tolerance | Defines boundaries for delegated decision-making. |
| Prioritization | Helps protect essential outcomes when time or capacity is fixed. |
| Transparency | Agile information radiators and reviews support control. |
| Tailoring | Choose agile practices that fit the project context. |
Use this live PRINCE2 Agile Foundation V2 page for web and app access, public sample questions, timed mocks, topic drills, plans, and related PM Mastery exam links.
| If you need to practice… | Best page | Why |
|---|---|---|
| classic PRINCE2 method fundamentals | PRINCE2 Foundation | Best live route for the core PRINCE2 method before you layer in agile tailoring. |
| applied PRINCE2 scenario work | PRINCE2 Practitioner | Best live route when you already know PRINCE2 basics and want longer application scenarios. |
| Scrum and agile decision-making | PMI-ACP | Best live route when the real need is broader agile delivery judgment rather than PRINCE2 governance. |
| If you are deciding between… | Main distinction |
|---|---|
| PRINCE2 Foundation vs PRINCE2 Agile Foundation Version 2 | PRINCE2 Foundation is the classic structured method route; PRINCE2 Agile Foundation adds agile delivery context. |
| PRINCE2 Agile Foundation Version 2 vs PMI-ACP | PRINCE2 Agile Foundation keeps a governance-first lens; PMI-ACP is broader agile delivery across frameworks. |
| PRINCE2 Agile Foundation Version 2 vs PSM I | PRINCE2 Agile Foundation blends governance with agility; PSM I is team-level Scrum mechanics and accountabilities. |
| Timing | Practice focus | What to review after the set |
|---|---|---|
| Days 7-5 | One 40-question diagnostic plus drills in weak areas | Whether misses came from governance, agile concepts, tailoring, prioritization, or route confusion |
| Days 4-3 | Mixed governance-plus-agile sets | Whether you can explain how the answer preserves control while enabling adaptation |
| Days 2-1 | Light review of tolerances, prioritization, agile suitability, and feedback mechanisms | Only recurring traps; avoid switching into pure Scrum or pure PRINCE2 assumptions |
| Exam day | Short warm-up if useful | Choose the answer that balances PRINCE2 control with agile delivery |
If you can score above 75% on several unseen mixed attempts and explain how each answer balances governance and agility, you are likely ready. Do not keep repeating familiar questions until memory replaces route-specific reasoning.