Try 10 focused PRINCE2 Agile Foundation questions on PRINCE2 Agile Principles and Practices, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PRINCE2 Agile Foundation |
| Topic area | PRINCE2 Agile Principles and Practices |
| Blueprint weight | 40% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate PRINCE2 Agile Principles and Practices for PRINCE2 Agile Foundation. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 40% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: PRINCE2 Agile Principles and Practices
What is the main purpose of the PRINCE2 Agile principle of keeping governance visible?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: Keeping governance visible means project control stays clear and transparent in an agile environment. It enables timely direction, monitoring of tolerances, and informed decisions without forcing teams to abandon agile ways of working.
In PRINCE2 Agile, keeping governance visible ensures that accountability, control, and decision-making remain clear while delivery is performed using agile techniques. The project still needs transparent status, tolerances, priorities, and escalation paths, but this is done in a way that does not overload the team with unnecessary bureaucracy. The practical effect is that project-level roles can direct and control the work with confidence, while delivery teams retain flexibility over how they build and refine products within timeboxes and backlogs. This supports agility without weakening governance. It is different from techniques used for estimation, defining completion, or capturing lessons learned, because those serve different purposes.
Keeping governance visible provides transparency for control and decision-making while allowing agile teams to work flexibly.
Topic: PRINCE2 Agile Principles and Practices
Which PRINCE2 Agile practice is used to define and control quality criteria so that products are useful, fit for purpose, and acceptable to stakeholders?
Best answer: C
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, the quality practice is concerned with making sure products meet agreed quality criteria. Those criteria help teams build outputs that are usable and acceptable, not just completed on time.
The core idea is that the quality practice defines what an acceptable product looks like before and during delivery. In an agile context, this matters because teams deliver incrementally and need clear quality criteria to judge whether each product or feature is useful, fit for purpose, and ready to be accepted. PRINCE2 Agile links quality to agreed expectations, so delivery is not only fast but also valuable and acceptable to stakeholders.
The closest distractors relate to control in other areas, but they do not define product quality criteria as their main purpose.
The quality practice sets and manages quality criteria so products meet agreed needs and acceptance expectations.
Topic: PRINCE2 Agile Principles and Practices
Two delivery teams are preparing the next release on a PRINCE2 Agile project. Team A keeps a technical task list. Team B expresses backlog items as user stories and estimates them in story points before creating a release map. What is the main planning advantage of Team B’s approach?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: User stories help planning because they express work in terms of user value, which makes backlog prioritization, estimation, and release discussion clearer. In PRINCE2 Agile, that improves the quality of planning information used to build and review a release map.
In PRINCE2 Agile, user stories support the Plans practice by helping the team and Product Owner describe work in a customer-focused way that is suitable for prioritization and estimation. When backlog items are written as user stories and then estimated, the team can discuss likely scope and sequencing for a release more effectively. This gives better input to artifacts such as the product backlog and release map than a simple technical task list, because the planning conversation is based on value and outcomes, not just internal activity.
A technical task list may help delivery at team level, but it is weaker for deciding what should be included in a release. The key point is that user stories improve planning quality by linking scope, value, and estimation.
User stories describe value from the user’s perspective, making backlog prioritization and release planning easier when combined with estimation.
Topic: PRINCE2 Agile Principles and Practices
Which TWO statements correctly describe how user stories support planning in PRINCE2 Agile?
Correct answers: C, D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: User stories support the Plans practice by expressing requirements in a form that is easy to discuss, prioritize, and estimate. That makes them useful inputs to backlog management and release planning, but they do not replace planning artifacts or governance roles.
In PRINCE2 Agile, user stories help planning because they describe work in a clear, lightweight way that teams and stakeholders can understand. This makes it easier to break down requirements, prioritize them in a backlog, and estimate them for delivery. Those estimates and priorities then support planning decisions such as what is likely to be delivered in an iteration, release, or stage timebox, often shown in a release map.
User stories support planning artifacts; they do not replace them. A release map is still needed to show intended delivery over time, and governance approval is not required before the delivery team can estimate stories. The key point is that user stories improve planning visibility and forecast discussions.
User stories give a simple, consistent form for planning discussions, estimation, and prioritization in the backlog.
Estimated and prioritized user stories help inform release-map decisions about likely scope across timeboxes.
Topic: PRINCE2 Agile Principles and Practices
On a PRINCE2 Agile project, the project manager needs help maintaining logs, organizing workshop outputs, and updating the project dashboard. The project board also wants an independent view of whether delivery remains aligned to the business case and governance needs. Which statement correctly compares project assurance and project support in this situation?
Best answer: A
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, project assurance and project support have different purposes. Project assurance gives the project board independent confidence that the project is being governed properly, while project support helps the project manager with administrative and reporting activities.
The key distinction is independence versus support. Project assurance acts on behalf of the project board to check that the project remains viable, properly governed, and aligned to agreed requirements such as the business case. It is not just an extra pair of hands for the project manager. Project support, by contrast, provides practical help to the project manager, such as maintaining records, supporting reporting, and helping with administrative coordination.
In the scenario, the request for an independent view for the project board points to project assurance. The need to maintain logs, organize workshop outputs, and update reporting points to project support.
Agile ways of working increase transparency, but they do not remove the need for independent assurance.
Project assurance serves the project board through independent oversight, whereas project support assists the project manager with administrative support.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project has three delivery teams. The project executive wants a single, high-level view of overall status, forecast delivery confidence, and any emerging exceptions for governance decisions. Which progress artifact is most appropriate?
Best answer: A
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The key discriminator is the decision level. A project executive needs an overall governance view across the project, so the project dashboard is the most suitable progress artifact. It summarizes status for management attention rather than detailed team control.
In PRINCE2 Agile, the progress practice emphasizes transparency and the use of information radiators that fit the audience and decision need. A project dashboard is aimed at project-level stakeholders who need an aggregated view of status, trends, confidence, and possible exceptions across the project. That matches the project executive’s need for governance information.
A team dashboard and burn chart are more focused on delivery-level visibility, helping agile teams track work and short-term progress. A Definition of Done belongs to quality, not progress. The key takeaway is to match the artifact to the level of control and decision-making required.
A project dashboard provides a governance-level view of overall project progress and supports decision-making by senior roles.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project includes this artifact entry:
ID: ISS-07
Summary: Test environment access delayed
Impact: May affect the current iteration goal
Owner: Project manager
Status: Open
What is the purpose of this artifact?
Best answer: A
What this tests: PRINCE2 Agile Principles and Practices
Explanation: This artifact is for issue management. The decisive clues are the issue ID, summary, impact, owner, and open status, which show that a current problem is being logged and tracked for action.
In PRINCE2 Agile, the purpose of an issue artifact is to capture and monitor events, problems, requests, or concerns that have already arisen and need management attention. The clue in the excerpt is that something has happened now: access is delayed, there is an owner, the impact is stated, and the status is open. That is different from a list used to prioritize future scope, a risk record for uncertain events, or a quality record used to confirm acceptance against criteria.
The key point is that issue information supports visibility, ownership, and follow-up so the project can respond quickly and keep control. The closest distractor is the risk purpose, but a risk is uncertain, whereas this delay has already occurred.
The entry shows an issue being recorded, owned, and tracked so it can be managed during the project.
Topic: PRINCE2 Agile Principles and Practices
A Project Executive wants a concise view of overall progress and any emerging exceptions, while the agile team already uses detailed information to manage daily work. In PRINCE2 Agile, what is the main purpose of the project dashboard?
Best answer: C
What this tests: PRINCE2 Agile Principles and Practices
Explanation: The project dashboard is for project-level visibility, not team-level task control. It gives governance roles a concise summary of status, trends, and exceptions so they can monitor progress and make informed decisions.
In PRINCE2 Agile, the key distinction is audience and purpose. A project dashboard supports project-level governance by providing a summarized view of overall status, progress, forecasts, and any exceptions that may need attention. It is aimed at roles such as the Project Executive and other project-level stakeholders who need transparency without seeing all delivery detail.
A team dashboard serves a different purpose. It helps the delivery team manage its day-to-day work with more detailed, operational information. So in this scenario, where a Project Executive needs a concise oversight view, the project dashboard is the appropriate artifact. The closest distractor is the team-focused option, which is correct for delivery management but not for project governance.
A project dashboard summarizes progress, trends, and exceptions at project level so governance roles can monitor and direct the project.
Topic: PRINCE2 Agile Principles and Practices
Which TWO statements show how PRINCE2 Agile balances project management control with agile responsiveness? Select TWO.
Correct answers: B, D
What this tests: PRINCE2 Agile Principles and Practices
Explanation: PRINCE2 Agile balances control and responsiveness by keeping governance and key constraints clear while allowing delivery detail to adapt. Stage control and fix-and-flex both show this blend of PRINCE2 oversight with agile ways of working.
A core PRINCE2 Agile idea is to keep enough project management control to maintain direction, while giving agile teams room to respond quickly during delivery. Two common clues are stage-based governance and the fix-and-flex approach. Stage boundaries and tolerances provide management control, but teams can still reorder and refine work inside timeboxes. Likewise, PRINCE2 Agile often protects important constraints such as time and cost, while allowing lower-priority scope to vary so value can still be delivered. By contrast, freezing all detailed requirements removes agile responsiveness, and changing project tolerances without escalation removes PRINCE2 control. The balance comes from combining clear governance with controlled flexibility.
This combines PRINCE2 governance control at stage level with agile flexibility during delivery.
This is the PRINCE2 Agile idea of protecting key constraints by flexing less critical scope.
Topic: PRINCE2 Agile Principles and Practices
A PRINCE2 Agile project has three agile teams. Each team already has a Product Owner managing its team backlog. The project board wants one person to align customer priorities across all teams and provide a clear project-level view of what should be delivered first. Which role is MOST appropriate?
Best answer: B
What this tests: PRINCE2 Agile Principles and Practices
Explanation: In PRINCE2 Agile, the organization practice keeps governance and delivery responsibilities clear by defining distinct roles. When several agile teams each have their own Product Owner, the Chief Product Owner provides the project-level customer direction and coordinates priorities across teams.
The key distinction here is between team-level delivery ownership and project-level product direction. A Product Owner usually manages priorities for one team’s backlog, but when several teams are involved, PRINCE2 Agile uses the Chief Product Owner to give a single, coherent customer view at project level. This helps the organization practice maintain clear responsibilities: team Product Owners focus on detailed team priorities, while the Chief Product Owner aligns those priorities across the project.
The project manager still manages the project as a whole, including coordination and control, but does not replace the customer-priority role. The agile coach supports agile ways of working, but does not own backlog priority decisions. The main takeaway is that the Chief Product Owner bridges project governance and agile delivery without blurring responsibilities.
The Chief Product Owner provides the project-level customer focus and aligns priorities across multiple team Product Owners.
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, then return to PM Mastery for timed practice.