PRINCE2-Agile-Foundation PRINCE2 Agile Foundation (Version 2) Exam Questions and Answers

In Agile Foundation guidance, the risk practice is explicitly responsible for the identification, assessment, and management of uncertainties, making option A the correct answer. Risk is defined as uncertainty that, if it occurs, will have a positive or negative impact on objectives. Agile recognizes that uncertainty is inherent in complex and adaptive work, so effective risk management is essential to successful delivery.

The risk practice focuses on proactively identifying uncertainties early, assessing their likelihood and impact, and determining appropriate responses. Agile Foundation documents emphasize that risk management in Agile is continuous rather than a one-time activity. Risks are regularly reviewed, updated, and addressed throughout the lifecycle as new information emerges. This aligns with Agile principles of transparency, inspection, and adaptation, allowing teams to respond to uncertainty in a timely and informed manner.

Option B, plans, focuses on outlining how objectives will be achieved and how work will be organized over time. While planning may take risks into account, it does not primarily identify or assess uncertainties. Option C, quality, ensures that outputs meet agreed standards and acceptance criteria but does not deal directly with uncertainty. Option D, business case, justifies why a project should proceed by outlining costs, benefits, and risks at a high level, but it does not actively manage or assess uncertainties on an ongoing basis.

Agile Foundation guidance highlights that Agile approaches often reduce risk by delivering incrementally, seeking early feedback, and validating assumptions quickly. However, this does not eliminate the need for a structured risk practice. Instead, risk management supports Agile delivery by making uncertainties visible and manageable. By embedding risk identification and assessment into regular team activities, organizations can make better decisions, protect value, and increase confidence among stakeholders while still maintaining flexibility and responsiveness to change.

Agile Foundation guidance identifies the Agilometer assessment as a key tool used to assess risks associated with Agile adoption, making option C the correct answer. The Agilometer is specifically designed to evaluate how suitable Agile approaches are for a particular project, team, or organizational context before or during adoption. It helps organizations understand the level of risk involved in applying Agile and highlights areas that may need additional support, tailoring, or controls.

The Agilometer works by assessing several dimensions related to Agile readiness, such as stakeholder engagement, organizational culture, team capability, leadership support, and delivery environment. By scoring these factors, it provides a structured and transparent view of potential risks and constraints. This allows decision-makers to identify where Agile is likely to succeed easily and where challenges may arise, enabling proactive risk management rather than reactive problem-solving.

Option A, an enterprise agility assessment, focuses on overall organizational maturity and long-term transformation rather than project-level or adoption-specific risks. Option B, a project dashboard, is used for tracking progress, metrics, and status, not for assessing suitability or adoption risk. Option D, a cumulative risk burn-down chart, may be used to visualize risk reduction over time, but it does not assess whether Agile adoption itself is appropriate or risky in a given context.

Agile Foundation documents emphasize that Agile is not a one-size-fits-all solution. The Agilometer supports informed decision-making by encouraging thoughtful consideration of constraints, governance needs, and cultural readiness. By identifying adoption risks early, organizations can tailor Agile practices, apply hybrid approaches where necessary, and set realistic expectations. This structured assessment helps protect value delivery while maintaining the flexibility and responsiveness that Agile aims to provide.

Kanban uses a flow-based approach to visualize and control work in progress (WIP). It emphasizes limiting WIP to improve flow and reduce bottlenecks, with continuous monitoring via Kanban boards. This approach supports flexibility, transparency, and efficiency in managing tasks.

The Agilometer (A) measures agility, Lean (B) is a broad philosophy focusing on waste reduction, and Scrum (D) is an iterative framework but uses time-boxed sprints rather than flow-based control.

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 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.

Agile Foundation guidance recognizes that a smooth and effective handover to operations depends on providing clear, relevant, and usable information about what has been built and how it works. Documentation on functionality is therefore the key factor that ensures the operations team has a clear understanding of deliverables during the handover process, making option C the correct answer.

Although Agile values working solutions over comprehensive documentation, it does not eliminate documentation altogether. Instead, Agile promotes “just enough” documentation that is fit for purpose. During handover, operations teams need to understand system behavior, features, configurations, limitations, and operational requirements. Functional documentation provides this clarity by explaining what the product does, how it should be used, and how it behaves under normal and exceptional conditions. This enables operations teams to support, maintain, and troubleshoot the product effectively.

Option A, retrospective documentation, focuses on lessons learned and process improvements for the delivery team rather than explaining the product itself. While useful for continuous improvement, it does not directly support operational understanding of deliverables. Option B, Kanban or team boards, provide visibility into work in progress and workflow during development, but they are not designed to communicate finalized product functionality during handover. Option D, a risk management approach, helps identify and mitigate risks but does not clearly describe the delivered product or its capabilities.

Agile Foundation materials emphasize collaboration between delivery and operations, often aligned with DevOps principles, to reduce handover friction. Clear documentation on functionality supports this collaboration by ensuring shared understanding and continuity after delivery. When operations teams know exactly what has been delivered and how it functions, they can confidently take ownership, maintain service quality, and respond effectively to issues. This approach aligns with Agile’s focus on sustainable delivery, transparency, and long-term value creation.

The Agile Enablement Workshop is specifically designed to support the transition of teams and organizations into agile ways of working. Its primary purpose is to identify, assess, and plan for risks related to agile adoption. This includes challenges like cultural resistance, skills gaps, tooling needs, and process adaptations. The workshop ensures that these risks are proactively managed to smooth the agile transformation and increase the chances of successful agile delivery.

By focusing on agile adoption risks rather than project delivery or business as usual, the workshop addresses the foundational changes required for agility at team and organizational levels. Effective enablement workshops facilitate buy-in, identify training needs, and help tailor agile frameworks to the organization's context.

Agile Foundation guidance describes co-creation as a collaborative approach where value is created together by people who share common attitudes, values, and goals. This makes option C the correct answer. Co-creation goes beyond simply assigning work or motivating individuals to meet predefined objectives. Instead, it emphasizes collective ownership, shared understanding, and active participation by all relevant stakeholders in shaping outcomes.

In Agile environments, co-creation is rooted in the belief that the best solutions emerge when diverse perspectives work together in an open and trusting environment. Teams, customers, users, and stakeholders collaborate continuously to explore needs, generate ideas, and refine solutions. This shared mindset ensures that everyone involved is aligned on purpose and value, rather than working in isolation or following instructions without context.

Option A focuses on motivation to meet objectives, which reflects performance management rather than co-creation. While motivation is important, it does not necessarily involve shared ownership or joint value creation. Option B, agreeing ways of working, relates to establishing working agreements or team norms, which support collaboration but do not define co-creation itself. Option D, instructing the execution of tasks, represents a command-and-control approach that is contrary to Agile principles and does not encourage shared responsibility or creativity.

Agile Foundation documents emphasize that co-creation strengthens engagement, trust, and innovation. When people share attitudes, values, and goals, they are more likely to challenge assumptions constructively, learn from each other, and adapt solutions based on feedback. This approach supports Agile principles such as collaboration, customer focus, and continuous improvement. Co-creation ensures that value is not simply delivered to stakeholders but created with them, leading to better outcomes, higher satisfaction, and more sustainable Agile ways of working.

The Delivering level is responsible for the day-to-day management and decision-making within the constraints set by the project manager. Delivering teams carry out the actual work to create the project products and manage their activities under the project’s governance framework. The Project Manager manages the overall project, while directing sets the strategic direction and commissioning authorizes initiation.

This separation ensures clear responsibilities and empowers the delivery teams to self-manage within defined boundaries.

The Team Retrospective Workshop is explicitly designed to facilitate team growth and continuous improvement in working practices. It is a fundamental agile practice where the team reflects on the recently completed work or sprint to identify what went well, what didn’t, and what could be improved. The goal is to foster an environment of trust and openness, enabling teams to discuss challenges and successes honestly.

Retrospectives promote inspect and adapt principles by encouraging teams to continuously evaluate their processes, collaboration, and tools. They help uncover systemic issues, process bottlenecks, or interpersonal challenges that may be impeding productivity or quality. Teams use this feedback to implement actionable improvements, which can range from adjusting communication methods to refining definitions of done or ready.

This workshop supports a key agile mindset—continuous learning and improvement—which directly contributes to team maturity, performance, and morale. Importantly, retrospectives are not about assigning blame but rather about fostering a growth mindset that accepts change as an opportunity to evolve.

While Project Kickoff Workshops (A) initiate project alignment and Progress Review Workshops (C) monitor project status, they do not primarily focus on team process improvements. The Team Planning Workshop (D) is concerned with planning upcoming work, not retrospection.

In PRINCE2 Agile, retrospectives are a critical tool to blend traditional project management with agile principles by promoting regular reflection and incremental enhancements.

Agile Foundation guidance emphasizes building quality into the product from the very beginning rather than relying on late-stage inspection or escalation. When a minor quality control failure occurs during product creation, the most appropriate initial response is to revisit the development and test activities, making option C the correct answer. Agile promotes continuous quality assurance through iterative development, frequent testing, and fast feedback loops, allowing teams to correct issues as soon as they emerge.

In Agile environments, quality is a shared responsibility of the entire team. Minor defects or quality issues are viewed as learning opportunities rather than failures that require formal escalation. Revisiting development and testing activities allows the team to quickly identify root causes, such as unclear acceptance criteria, gaps in automated tests, or misunderstandings in requirements. By addressing the issue at its source, teams can prevent similar defects from recurring in future iterations.

Option A, escalating the issue to the project manager, is generally unnecessary for minor quality failures in Agile. Agile teams are empowered to self-manage and resolve issues at the team level whenever possible. Option B, performing an independent review, may be appropriate for major or systemic quality problems but is excessive as an initial response to a minor issue. Option D, discussing the issue with the chief product owner, is also not the first step unless the issue affects product value or requires a change in priorities.

Agile Foundation documents stress the importance of continuous improvement, built-in quality practices, and early defect resolution. Techniques such as test-driven development, continuous integration, peer reviews, and frequent retrospectives support this approach. By immediately revisiting development and test activities, Agile teams maintain flow, reduce rework, and ensure that quality issues are resolved quickly and effectively, reinforcing Agile principles of transparency, inspection, and adaptation.

One of the significant challenges when merging traditional project management approaches like PRINCE2 with agile delivery methods is the lack of guidance on doing agile. While PRINCE2 provides a structured framework focusing on governance, control, and business justification, agile introduces flexible, iterative, and people-centered approaches. The integration of these requires clear guidance on how to implement agile practices effectively within the PRINCE2 framework.

PRINCE2 Agile acknowledges that while it offers a comprehensive method to combine governance and agility, many organizations and practitioners struggle with practical implementation, especially in how to “do agile” properly. This includes understanding how to adopt agile roles, ceremonies, and artifacts without losing control, as well as aligning agile delivery with PRINCE2’s management layers.

The challenge is compounded by the fact that agile methodologies emphasize adaptive planning and team autonomy, whereas traditional project management often focuses on upfront planning and command-and-control structures. PRINCE2 Agile aims to bridge this gap by providing detailed guidance, but a lack of practical ‘how-to’ agile advice remains a common issue.

Other options like terminology differences (A), unclear processes (B), and guidance at delivery level (C) are lesser challenges because PRINCE2 Agile provides a common vocabulary and defined processes that include delivery considerations.

The principle that establishes governance by delegating responsibilities and setting tolerances is manage by exception, making option C the correct answer. Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile principles, explains that effective governance does not require constant oversight or micromanagement. Instead, it relies on clearly defined roles, delegated authority, and agreed tolerances within which teams are empowered to operate.

Manage by exception works by setting measurable tolerances for key aspects such as time, cost, scope, quality, risk, and benefits. As long as work remains within these agreed limits, the team or delivery level can proceed independently without escalation. This creates clarity around accountability while allowing teams the autonomy needed to work efficiently and respond to change—an essential aspect of Agile delivery. Escalation only occurs when forecasts indicate that tolerances will be exceeded, ensuring that senior management attention is focused where it adds the most value.

Option A, ensure continued business justification, focuses on confirming that the project remains viable and worthwhile, but it does not define how governance is enacted day to day. Option B, tailor to suit the project, emphasizes adapting methods and controls to the project context rather than establishing governance through delegation. Option D, focus on products, ensures clarity around outputs and acceptance criteria but does not address governance or escalation mechanisms.

Agile Foundation documents highlight that manage by exception supports agility by balancing control with empowerment. Teams gain the freedom to self-manage and deliver iteratively, while leadership retains confidence that risks are controlled and objectives are protected. This principle reduces unnecessary reporting, speeds up decision-making, and supports trust between governance levels. By clearly delegating responsibilities and defining tolerances, manage by exception provides a practical and effective governance model compatible with Agile ways of working.

Reference https://publications.axelos.com/prince2agile2016/content.aspx?page=pra_126 &showNav=true&expandNav=true

A well-recognized challenge when merging traditional project management with Agile approaches is the use of different terminology, making option B the correct answer. Agile Foundation materials highlight that traditional project management and Agile have evolved from different perspectives, each with its own language, concepts, and assumptions. When these approaches are combined within the same organization or project, misunderstandings often arise due to terminology differences rather than fundamental conflicts in intent.

Traditional project management commonly uses terms such as scope, milestones, deliverables, baselines, and change control, while Agile uses concepts like backlog, iterations, increments, velocity, and value delivery. Even when the underlying goals are aligned, different terminology can create confusion among stakeholders, project managers, Agile teams, and senior leadership. This confusion may lead to misaligned expectations, incorrect reporting, or resistance to Agile practices, as people may interpret the same words differently or assume conflicting meanings.

Option A, lack of clear processes, is generally not a common issue because both project management and Agile provide structured approaches, albeit in different forms. Option C, lack of guidance at the project level, is also not accurate, as Agile Foundation guidance increasingly addresses how Agile can operate at team, project, and organizational levels. Option D, the use of a flexible framework, is actually a benefit of Agile rather than a challenge.

Agile Foundation documents emphasize that overcoming terminology differences requires education, shared understanding, and alignment rather than choosing one approach over the other. By establishing a common language, clarifying roles and expectations, and focusing on value delivery rather than labels, organizations can successfully integrate Agile ways of working with project management governance. Addressing terminology differences early helps reduce friction, improves collaboration, and enables a more effective hybrid or Agile-informed project environment.

The Agile Enablement Workshop provides a collaborative environment where teams and stakeholders define critical agile artifacts, including the Definition of Ready. This definition specifies the criteria a user story or product backlog item must meet before work can begin, ensuring clarity and readiness.

The workshop facilitates alignment on quality standards, scope, and expectations, reducing ambiguity and improving flow through development cycles. By involving all key participants, the Definition of Ready is meaningful and practical, tailored to the project's specific context.

While starting up (A), kickoff (B), and initiation workshops (C) focus on project foundation and planning, they do not specifically focus on agile readiness criteria.

This workshop is essential for embedding agile practices within PRINCE2 governance and fostering effective delivery.

Agile Foundation guidance explains that the purpose of the agile enablement workshop is to identify, assess, and plan for risks associated with Agile adoption, making option C the correct answer. This workshop is a structured activity designed to help organizations and project teams understand how well Agile ways of working fit their specific context and what challenges may arise when adopting Agile approaches.

The agile enablement workshop focuses on readiness rather than delivery execution. It examines factors such as organizational culture, governance expectations, stakeholder engagement, team capability, leadership support, and external constraints. By discussing these areas openly, participants can identify potential barriers to Agile adoption, assess their impact, and agree on actions to reduce or manage those risks. This proactive approach supports informed decision-making and avoids unrealistic expectations about Agile.

Option A, risks associated with project delivery, relates more to traditional project risk management practices. Option B, team delivery risks, focuses narrowly on team-level execution issues rather than adoption. Option D, enterprise agility risks, applies at a broader organizational transformation level and goes beyond the typical scope of an agile enablement workshop, which is usually project- or initiative-focused.

Agile Foundation documents emphasize that Agile adoption is not risk-free and should be approached thoughtfully. The agile enablement workshop helps ensure that Agile is tailored appropriately rather than applied mechanically. It supports alignment between Agile teams and governance structures, clarifies where flexibility is possible, and highlights where controls are required. By identifying and planning for adoption risks early, organizations increase the likelihood of successful Agile implementation while preserving the core values of adaptability, collaboration, and value-driven delivery.

The Recommend step in issue management involves analyzing the issue and evaluating possible options to resolve it. At this stage, the project team or responsible individuals identify potential solutions, weigh their pros and cons, and recommend the best course of action to decision-makers.

Capture is the initial identification and recording of the issue, Decide involves making the final decision on the recommended solution, and Implement is the execution of the chosen resolution. Evaluating options thoroughly during the Recommend phase helps ensure informed decision-making and effective issue resolution.

This structured approach aligns with PRINCE2’s focus on proactive issue management, maintaining control and reducing risk impacts.