PRINCE2-Agile-Foundation Sample Questions Answers

In PRINCE2 Agile, a Backlog is the prioritized list of requirements, features, or user stories that define what needs to be delivered for a product. It is a dynamic and evolving list that is continually refined and re-prioritized to ensure the most valuable work is done first. The backlog acts as a single source of truth for what the team needs to deliver and provides transparency to stakeholders regarding progress and priorities. It aligns with agile principles and practices such as Scrum, where the Product Backlog contains all desired work for the product.

The Project Canvas is a high-level tool used for defining project scope and objectives, the Release Map plans releases and iterations, and the Project Log tracks issues, risks, and actions but does not list prioritized requirements.

User inputs are initially gathered as user stories in the product backlog in PRINCE2 Agile. User stories represent small, customer-focused requirements that capture the "who," "what," and "why" of a feature. These stories form the foundation of requirements and quality criteria for the product and ensure that development is driven by user needs and value delivery.

The Definition of Done is developed later as part of the quality management approach to specify when work is complete. Epic user stories are larger features that can be broken down into smaller user stories. The quality register tracks quality-related activities but is not the first step for gathering user inputs.

Trading/swapping is a technique used within the issues practice to manage and resolve conflicts or competing priorities by negotiating trade-offs. For example, scope items, resources, or deadlines may be traded or swapped between stakeholders to reach agreements that keep the project on track.

This collaborative negotiation supports flexible, pragmatic issue resolution, aligning with agile values of collaboration and customer focus. It enables project teams to balance competing demands while maintaining progress and business justification.

Objectives and key results (B) are goal-setting tools, refactoring (C) is a technical practice for code improvement, and delegation poker (D) is about decision-making authority — none specifically target issue resolution.

Trading/swapping aligns with PRINCE2’s controlled management of issues and agile’s collaborative problem-solving approach.

The Release Planning Workshop is the forum where planning for the next stage occurs in PRINCE2 Agile. This workshop brings together the project management team and delivery teams to plan the scope, schedule, and resources for the upcoming release or stage. It helps align business priorities with delivery capacity and supports incremental and iterative delivery approaches.

The Team Planning Workshop focuses on more detailed planning at the team level within the release, the Team Retrospective Workshop is dedicated to reflecting on performance and improving processes, and the Progress Review Workshop is for reviewing progress against the plan rather than planning future work.

Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile, explains that the project management team structure defines how the project will be managed and delivered, including clarity around roles, responsibilities, and ways of working. A key element that should be included within this structure is a description of how products are to be produced, making option D the correct answer.

The project management team structure is not just a list of roles; it provides context on how delivery will operate in practice. This includes how teams are organized, how responsibilities are allocated, and how products will move from concept to completion. Describing how products are to be produced ensures there is shared understanding of the delivery approach, whether it is Agile, iterative, hybrid, or otherwise. This clarity supports coordination, accountability, and effective governance throughout the project lifecycle.

Option A, procurement and contract needs, belongs more appropriately to commercial or procurement management considerations rather than the team structure itself. Option B, a full and firm foundation for initiation, describes the purpose of the initiation stage rather than the contents of the team structure. Option C, arrangements for co-location or remote teams, relates to communication and working practices, which may support delivery but do not define the management structure.

Agile Foundation documents emphasize transparency and alignment between governance and delivery. Including a description of how products are to be produced within the project management team structure helps bridge management expectations with Agile delivery practices. It ensures that all stakeholders understand how work will be organized, how decisions will be made, and how value will be delivered. This supports Agile principles such as collaboration, empowerment, and adaptability while maintaining clear project-level control and accountability.

The Project Backlog is the artifact used to describe the project’s major products in the form of epic user stories. Epic stories are large, high-level user stories that capture significant features or product components that may later be decomposed into smaller, more detailed user stories in the product backlog.

The Project Backlog provides a strategic view of what the project intends to deliver and supports planning at the project level, including releases and stages. It bridges the gap between business requirements and team-level delivery.

The Product Backlog (C) contains detailed user stories ready for development but is typically more granular. The Release Map (B) plans releases and iterations but does not list epic stories. The Project Dashboard (A) is a reporting tool, not a repository of requirements.

The use of epic user stories in the project backlog aligns with agile practices for managing scope and enables incremental delivery aligned with business priorities.

The Team Planning Workshop is primarily held to update the product backlog. This collaborative session allows the delivery team to break down, refine, and reprioritize user stories or tasks to prepare for the upcoming iteration or sprint. The team reviews the product backlog items, clarifies acceptance criteria, estimates effort, and commits to the planned work.

Updating the product backlog at this level ensures that detailed planning aligns with the overall project vision and release goals. It empowers the team to self-organize and manage their workload, supporting agile principles of autonomy and collaboration.

While the project dashboard (A) provides status reporting, the release map (C) focuses on higher-level release planning, and OKRs (D) relate to strategic objectives, these are not the central focus of the team planning workshop.

PRINCE2 Agile promotes team planning workshops as essential forums for translating business priorities into actionable, manageable work for delivery teams.

The burn-down chart is a visual tool used in agile to monitor progress by tracking the remaining work against time. It provides teams and stakeholders with a clear, real-time view of project status and forecast completion, allowing for early identification of potential delays or bottlenecks.

The delegation matrix (A) defines authority, swarming (B) is a team collaboration technique, and t-shirt sizing (C) is an estimation method, none of which directly monitor progress.

Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile practices, explains that the organization practice is responsible for defining the products to be delivered and clarifying who will deliver them. This makes option C the correct answer. The organization practice focuses on establishing and maintaining a clear project management team structure, roles, responsibilities, and relationships to ensure effective delivery.

A key purpose of the organization practice is to ensure that accountability for producing each product is clearly defined. This includes identifying roles such as project manager, product owner, team members, and supporting roles, and ensuring that everyone understands what they are responsible for delivering. By defining who is involved and how they interact, the organization practice creates the foundation for collaboration, decision-making, and governance.

Option A, plans, focuses on when and how work will be carried out rather than who will deliver specific products. Planning answers questions about timelines, sequencing, and dependencies but assumes that responsibilities are already defined. Option B, the business case, explains why the project is worthwhile by outlining expected benefits, costs, and risks, not who will deliver products. Option D, risk, addresses uncertainty and potential threats or opportunities, not product ownership or delivery responsibility.

Agile Foundation documents emphasize that clarity of roles and responsibilities is especially important in Agile environments, where teams are empowered and self-organizing. The organization practice supports this empowerment by setting clear boundaries and accountability while avoiding unnecessary hierarchy. It ensures that everyone involved understands their contribution to value delivery and how their work fits into the wider project.

By defining both the products to be delivered and who will deliver them, the organization practice supports transparency, effective collaboration, and confidence among stakeholders. This clarity enables Agile teams to work autonomously within agreed structures, supporting consistent, high-quality delivery aligned with Agile and PRINCE2 Agile principles.

A primary benefit of an organization being and doing agile is faster time-to-market. Agile methods emphasize iterative delivery, frequent releases, and continuous feedback, enabling organizations to deliver value sooner and adapt quickly to changes. This benefit directly supports business agility and competitive advantage.

Using agile techniques alone (B) is a means, not a benefit. Focusing solely on tasks (C) ignores value and flow, and setting tolerances to zero (D) is neither practical nor encouraged.

Within Agile Foundation guidance and PRINCE2 Agile alignment, the Definition of Done (DoD) plays a critical role in supporting an iterative approach to delivery, making option C the correct answer. PRINCE2 Agile combines the governance strengths of PRINCE2 with the flexibility of Agile delivery, and iteration is central to how value is delivered incrementally. The DoD provides a shared and consistent understanding of what it means for work to be complete at the end of each iteration.

The iterative approach in PRINCE2 Agile relies on delivering small, usable increments frequently. The Definition of Done ensures that every increment meets agreed quality standards before it is considered complete. This supports transparency, predictability, and trust, which are essential for iterative delivery. Without a clear DoD, teams risk producing partially finished work that cannot be reviewed, tested, or released, undermining the benefits of iteration.

Option A is incorrect because Agile and PRINCE2 Agile emphasize continuous feedback as a core mechanism for learning and adaptation. Option B, offering predictive insights, is not a defining element of PRINCE2 Agile’s iterative approach; Agile focuses more on empirical feedback than prediction. Option D is also incorrect because frequent testing is encouraged, not reduced, in iterative Agile delivery.

Agile Foundation documents emphasize that the DoD acts as a quality gate that supports incremental progress while maintaining control. It aligns delivery teams and stakeholders on expectations and ensures that each iteration produces a potentially usable output. In PRINCE2 Agile, this alignment allows teams to work autonomously within defined tolerances while still meeting governance and assurance requirements. By clearly defining what “done” means, the DoD strengthens the iterative cycle of build, review, learn, and adapt, which is fundamental to Agile and PRINCE2 Agile working together.

Agile Foundation guidance clearly states that the transition from merely “doing Agile” to truly “being Agile” is driven by adopting an Agile mindset, making option C the correct answer. An Agile mindset represents a set of beliefs, attitudes, and ways of thinking that prioritize flexibility, learning, collaboration, and continuous improvement over rigid plans and fixed assumptions. Without this mindset, Agile practices often become mechanical routines that fail to deliver their intended benefits.

“Doing Agile” typically involves implementing visible practices such as daily stand-ups, iterations, backlogs, or boards. While these practices are useful, Agile Foundation documents emphasize that they only create lasting value when supported by the right mindset. “Being Agile” means embracing uncertainty, welcoming change, learning from feedback, and focusing on delivering value rather than following predefined plans. The Agile mindset encourages experimentation, reflection, and adaptation at both team and organizational levels.

Option A, the Agile Onion, is a conceptual model that explains the layers of Agile but does not itself transform behavior. Option B, psychological safety, is an important enabler that allows people to speak up, learn, and collaborate, but it is not the overarching driver of Agile transformation. Option D, Agile sustainability, focuses on maintaining Agile ways of working over time rather than initiating the shift from doing to being Agile.

Agile Foundation documents highlight that an Agile mindset fosters a culture where learning is continuous and failure is treated as an opportunity to improve. Leaders support this mindset by empowering teams, encouraging autonomy, and focusing on outcomes instead of outputs. When an organization adopts an Agile mindset, practices become adaptable tools rather than rigid rules. This cultural shift is what truly transforms an organization, enabling it to respond effectively to change, innovate continuously, and remain focused on delivering value.

When transitioning from project delivery into business as usual (BAU), establishing regular feedback loops is crucial to ensure continual improvement. Feedback loops enable ongoing monitoring, learning, and adaptation of both products and processes post-transition. They provide mechanisms for capturing user experiences, operational issues, and evolving requirements that inform future iterations and enhancements.

Feedback loops can take many forms, such as user surveys, retrospectives, operational reviews, or service desk reports. Their regularity and structure ensure that BAU teams remain aligned with customer needs and organizational goals while adapting to changes effectively. This approach fosters a culture of continuous learning and agility even after the formal project has closed.

Providing access to Kanban or team boards (A) supports transparency and workflow management but is more tactical and internal to teams rather than a strategic approach to continuous improvement across BAU. Agreeing on SLAs (C) and KPIs (D) define performance and service targets but do not inherently drive feedback or improvement cycles without mechanisms for learning and response.

PRINCE2 Agile highlights the importance of feedback loops as part of the ‘progress’ and ‘quality’ practices extended into BAU to sustain value delivery.

Agile workshops are collaborative sessions used throughout the project to address various aspects such as problem-solving, release planning, team alignment, and continuous improvement. Workshops encourage open communication, collective decision-making, and foster a shared understanding of goals and challenges.

Unlike a delegation matrix, which defines roles and authorities, or the project log, which records issues and risks, workshops are interactive events that enable timely resolution of challenges. The Agilometer is a diagnostic tool assessing agility maturity but not a problem-solving forum.

Agile workshops embody the agile principle of collaboration and adaptability, enabling teams to respond quickly to issues and refine plans collectively.

PRINCE2 Agile was specifically developed to address the challenge of applying Agile approaches within large, complex, and highly governed environments. Agile frameworks are highly effective at the team level, but Agile Foundation materials recognize that organizations often struggle when attempting to scale Agile across multiple teams, complex dependencies, regulatory constraints, and formal governance structures. This makes option B the correct answer.

Agile frameworks such as Scrum or Kanban focus on small, empowered teams delivering value iteratively. However, when initiatives become larger—spanning multiple teams, suppliers, and organizational units—challenges arise around coordination, assurance, reporting, and decision-making. Senior stakeholders often still require visibility, control, and confidence around investment, risk, and progress. PRINCE2 Agile bridges this gap by combining Agile delivery techniques with the governance, roles, and controls provided by PRINCE2.

Option A is incorrect because Agile frameworks are designed to be flexible rather than rigid. Option C is also not the primary challenge addressed by PRINCE2 Agile, as most Agile frameworks clearly define core roles, even if they differ from traditional roles. Option D is incorrect because Agile frameworks are explicitly designed to be combined with other methods, which is one of Agile’s strengths.

Agile Foundation documents explain that PRINCE2 Agile enables organizations to “blend” Agile delivery with project management governance. It allows Agile teams to work iteratively while ensuring alignment with business objectives, risk management, and stage-based oversight. By providing guidance on how to tailor governance without constraining agility, PRINCE2 Agile supports scaling Agile in complex environments. This makes it particularly valuable for organizations transitioning to Agile while still needing structure, assurance, and control at the enterprise level.

The Progress practice in PRINCE2 Agile is focused on providing a forecast of the project's viability by monitoring actual progress against plans and predicting future performance. It ensures that decisions can be made based on current status and trends, enabling timely interventions if necessary.

This practice involves collecting progress data, reviewing milestones, updating forecasts, and communicating status to stakeholders. Forecasting viability includes assessing whether the project remains aligned with business justification and expected benefits.

While opportunities and threats are part of risk management (B), user needs belong to requirements management (C), and accountability is a broader governance concern (D), progress specifically deals with tracking and forecasting delivery status.

The practice combines traditional PRINCE2 stage controls with agile iterative reviews, providing an integrated view of progress.

The project closure workshop is held to formally close the project, during which project documentation is updated to reflect the final state of the project, lessons learned are captured, and approvals are obtained. This ensures that all activities are completed, the project has delivered its intended products, and knowledge is retained for future projects or organizational learning.

Aligning teams (A) and refining release maps (D) are activities conducted earlier in the lifecycle, while benefits management (B) is usually defined during initiation and planning stages.

The Manage by Exception principle empowers individuals and teams by delegating decision-making within defined tolerances. It ensures governance is efficient by allowing project managers and teams to operate independently within agreed limits, escalating only when exceptions occur. This approach promotes self-management, autonomy, and accountability, which are key to agility, while maintaining control through governance boundaries.

The other principles focus on different aspects: business justification relates to ongoing viability, tailoring adapts the method, and focusing on products emphasizes deliverables but do not specifically address empowerment through governance.

Agile Foundation guidance explains that the release planning workshop is the forum where personas and evolving user needs are revisited and refined, making option C the correct answer. Release planning focuses on aligning upcoming work with user value, business priorities, and learning gained from previous deliveries. As Agile delivery is iterative and incremental, understanding users is not a one-off activity but an ongoing process that evolves as feedback is gathered.

During a release planning workshop, teams review insights from recent increments, stakeholder feedback, and real user behavior. Personas—representations of key user types—are revisited to confirm whether assumptions remain valid or need adjustment. As products evolve, new needs may emerge, priorities may shift, and earlier hypotheses about users may prove incomplete. Release planning provides the structured opportunity to incorporate this learning and refine the understanding of who the users are and what they need most next.

Option A, the team retrospective workshop, focuses on improving the team’s ways of working rather than reviewing user needs or personas. Option B, the project kickoff workshop, is typically held at the start of the initiative to establish initial vision, scope, and understanding, but it does not revisit evolving needs. Option D, the agile enablement workshop, concentrates on assessing and planning for risks associated with Agile adoption, not on refining user personas.

Agile Foundation documents emphasize that Agile success depends on continuous alignment with customer and user value. Release planning workshops support this by ensuring that upcoming work reflects the latest understanding of user needs rather than outdated assumptions. By regularly revisiting personas during release planning, teams strengthen customer focus, reduce waste, and improve the likelihood that delivered increments will meet real user expectations. This approach reinforces Agile principles of feedback, learning, and value-driven delivery.