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

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.

The PRINCE2 practices represent the essential aspects of project management that must be applied consistently from start to finish in every project. These practices cover key areas such as managing risks, issues, quality, plans, progress, and change. They provide structured guidance and tools to ensure the project remains viable, controlled, and aligned with business objectives.

While processes define the stages and flow of activities, and the people element refers to roles and skills, practices are the ongoing activities and controls embedded throughout the project lifecycle. The project context shapes how practices and processes are tailored but does not itself define the consistent elements.

This consistent application of practices supports governance, transparency, and control, critical for successful project outcomes.

The Risk practice is specifically aimed at controlling uncertainties that could impact the achievement of the project’s objectives. In PRINCE2 Agile, risk management involves identifying, assessing, and controlling threats and opportunities to reduce negative impacts and maximize positive outcomes.

Effective risk management is a core theme and practice in PRINCE2 Agile and is crucial for agile environments where change and uncertainty are inherent. The practice ensures that risks are continuously monitored and appropriate responses are planned and implemented. This proactive management helps keep the project viable and aligned with business justification.

While plans support managing scope and resources, issues deal with current problems rather than potential future events, and quality ensures that products meet requirements, risk management uniquely focuses on uncertainty.

The PRINCE2 Agile guidance emphasizes integrating agile techniques such as frequent reviews and retrospectives to improve risk awareness and control.

Speaking the language of leadership is essential for securing leadership buy-in when scaling agile. This means framing agile benefits, risks, and requirements in terms that resonate with leaders—such as business value, risk management, and return on investment—rather than just agile jargon.

While empowering teams (D) and emphasizing agile practices (C) are important, without leadership understanding and support, agile scaling is unlikely to succeed. Ensuring all decisions come from leadership (B) contradicts agile principles of decentralization and empowerment.

Effective communication tailored to leadership priorities fosters alignment and commitment.

The starting-up workshop is the initial workshop where the foundation for the project is established, including the creation and clarification of project role descriptions. Defining roles early ensures clarity of responsibilities, helps establish governance, and sets expectations for the project team.

Kickoff (B) focuses on launching the project, initiation (C) develops detailed plans, and the project canvas (D) is a tool for capturing high-level information but does not define roles explicitly.

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.

The Project Closure Workshop is the formal forum used to reflect on lessons learned during the project lifecycle. It is held towards the end of the project and provides an opportunity for the project team, stakeholders, and sponsors to review successes, challenges, and areas for improvement.

Capturing lessons learned supports organizational learning, helps avoid repeating mistakes, and improves future projects and agile adoption. This reflective practice aligns with PRINCE2’s focus on continuous improvement and governance requirements.

Other workshops such as team planning (A) focus on upcoming work, agile enablement (B) on agile adoption, and project kickoff (C) on project initiation, none of which prioritize lessons learned reflection.

The project closure workshop is a vital practice to ensure knowledge retention and maturity in both traditional and agile project environments.

Agile Foundation guidance often explains Agile concepts using the “Agile Onion” model, which shows how different layers of Agile build upon one another. Within this model, principles provide the core guidelines that help teams understand the purpose behind Agile practices, making option D the correct answer. Principles act as a bridge between high-level values and practical methods, explaining why certain ways of working are encouraged.

The Agile Onion typically places mindset at the center, followed by values, then principles, and finally practices, techniques, and processes on the outer layers. While practices describe what teams do and processes describe how work flows, principles explain the intent that guides those actions. They help teams make informed decisions when situations change or when standard practices do not fit the context. By understanding principles, teams can adapt their practices while still remaining aligned with Agile thinking.

Option A, processes, focus on structured sequences of activities and are concerned with execution rather than purpose. Option B, mindset, represents underlying beliefs and attitudes, which shape behavior but do not explicitly provide guidance on how or why specific practices are used. Option C, values, define what is important, such as collaboration or customer focus, but they do not give enough direction on how to translate those values into action.

Agile Foundation documents emphasize that principles are essential for sustainable Agile adoption. They enable teams to move beyond mechanical “doing Agile” and toward thoughtful “being Agile.” When teams understand the principles behind practices, they are better equipped to tailor their approach, respond to change, and apply Agile effectively in different environments. Principles ensure consistency of intent while allowing flexibility in execution, which is fundamental to Agile success.

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.

In Agile Foundation guidance, the product backlog is the primary artifact that provides a list of user stories, making option C the correct answer. The product backlog is a prioritized, evolving list of all the work needed to deliver and improve a product. User stories are the most common way of expressing requirements within the product backlog because they focus on user needs, value, and desired outcomes rather than detailed technical specifications.

The product backlog is owned and maintained by the product owner, who is responsible for ensuring that the backlog items are clearly defined, ordered by value, and aligned with business goals. User stories within the product backlog describe features, enhancements, fixes, and technical work from the perspective of the user or customer. This supports Agile’s emphasis on delivering value early and continuously while allowing flexibility as requirements change.

Option A, project backlog, is not a standard Agile Foundation artifact. Agile focuses on products and value streams rather than traditional project-centered task lists. Option B, project canvas, is a high-level visual planning tool used to summarize objectives, stakeholders, risks, and constraints, but it does not contain detailed user stories. Option D, release map, outlines planned releases and timelines at a high level, showing when groups of features or increments may be delivered, but it does not provide the detailed list of user stories themselves.

Agile Foundation documents highlight that the product backlog is dynamic and continuously refined through backlog refinement activities. User stories are added, removed, split, or re-prioritized based on feedback, learning, and changing business needs. This adaptability ensures that teams always work on the most valuable items first. By serving as the single, transparent source of requirements, the product backlog enables collaboration, alignment, and effective value delivery, which is why it is the correct artifact for listing user stories.

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.

Stakeholders are best described as those who can affect or be affected by the project. This definition is aligned with PRINCE2’s view and recognized globally in project management standards. Stakeholders include anyone with an interest or influence in the project outcomes, including project team members, users, suppliers, and external entities. Understanding and managing stakeholder engagement is crucial for project success, as stakeholders’ expectations and needs impact decisions and project delivery.

Options A, B, and D describe subsets or partial perspectives of stakeholders but do not capture the full inclusive scope.

Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile, explains that the closing a project process is primarily used to formally accept the project product, making option C the correct answer. This process ensures that the project has delivered what was agreed, that acceptance criteria have been met, and that the project can be closed in a controlled and orderly manner.

The closing a project process confirms that all products have been completed, approved, and handed over to the appropriate operational or business teams. Formal acceptance of the project product is critical because it provides clarity that delivery is complete and that responsibility for the product has transitioned from the project to ongoing operations or use. Agile Foundation documents emphasize that even in Agile environments, clear closure and acceptance are essential to good governance and benefit realization.

Option A, controlling the link between the project manager and the delivery team, relates to the managing product delivery process, not closing a project. Option B, ensuring the project is viable, is the purpose of the continued business justification principle and is reviewed throughout the project lifecycle, not just at closure. Option D, ensuring focus remains on delivering the stage’s products, aligns with the controlling a stage process, which operates while work is still ongoing.

Agile Foundation materials highlight that closing a project is more than an administrative step. It also includes confirming that benefits management responsibilities are handed over, lessons learned are captured, and stakeholders agree that the project objectives have been met. In Agile and PRINCE2 Agile contexts, this formal closure provides confidence to senior management that investment has delivered its intended outcomes.

By formally accepting the project product, the closing a project process ensures clarity, accountability, and a clean transition from project delivery to operational use, reinforcing disciplined governance while remaining compatible with Agile delivery approaches.

In Agile Foundation guidance, the team retrospective workshop is a key event focused on continuous improvement, making identifying improvement opportunities the correct answer. Retrospectives are held at regular intervals, typically at the end of an iteration or delivery cycle, to allow the team to reflect on how they worked together and how their processes, tools, and interactions can be improved.

The primary purpose of a retrospective is not to plan product features or refine requirements, but to inspect and adapt the team’s way of working. During the workshop, team members openly discuss what went well, what did not go as expected, and what could be improved. This reflection helps teams identify specific, actionable improvement opportunities that can be applied in the next iteration. Agile foundations emphasize creating a safe environment during retrospectives so that honest feedback and constructive discussion can occur.

Option A, prioritizing user stories, is typically done during backlog refinement or planning sessions and is the responsibility of the product owner with input from the team. Option B, defining acceptance criteria, usually takes place when preparing user stories before or during iteration planning, not during retrospectives. Option D, updating the project canvas, is a high-level planning or governance activity rather than a team-level continuous improvement practice.

Agile Foundation documents stress that retrospectives are essential for fostering a culture of learning and adaptability. By consistently identifying and implementing improvement opportunities, teams can enhance collaboration, improve quality, reduce waste, and increase predictability over time. Retrospectives also reinforce shared ownership of team performance, encouraging everyone to contribute to positive change. This focus on continuous improvement aligns directly with Agile principles of inspection and adaptation, making identifying improvement opportunities the central and most appropriate activity of the team retrospective workshop.

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 Agilometer is a diagnostic tool used within PRINCE2 Agile to assess the agility maturity and identify risks associated with adopting or operating in an iterative and agile environment. It helps teams and organizations evaluate their current agile capabilities, cultural readiness, and potential challenges that may impact project delivery.

The Agilometer highlights risk areas such as resistance to change, lack of agile skills, unclear roles, or insufficient governance adaptation. By providing a structured assessment, it enables proactive risk management and targeted improvements to reduce uncertainties inherent in iterative approaches.

Other artifacts like the project backlog (A) track requirements, the risk management approach (C) defines the method of managing risks but does not specifically identify iterative risks, and the Definition of Done (D) clarifies completion criteria rather than risks.

The Agilometer supports continuous improvement and risk mitigation aligned with PRINCE2’s risk and quality practices, ensuring agile projects remain viable and controlled.

The concept of “being Agile” rather than merely “doing Agile” is a central theme in Agile Foundation guidance. “Being Agile” refers to adopting the Agile mindset, values, and principles as a way of thinking and behaving, rather than simply applying a set of tools, ceremonies, or techniques. This mindset emphasizes adaptability, collaboration, continuous learning, and responsiveness to change, which is best represented by option B.

Agile foundations clearly distinguish mindset from mechanics. While timelines, documentation, and techniques have their place, they are secondary to people, interactions, and the ability to respond effectively to changing circumstances. Adaptability means welcoming change, even late in development, when it improves value for customers and stakeholders. Collaboration emphasizes close, ongoing cooperation between cross-functional team members, business representatives, and customers, ensuring shared understanding and faster decision-making.

Option A focuses on strict timelines and task completion, which aligns more closely with traditional predictive or plan-driven approaches. Agile recognizes that rigid timelines can reduce flexibility and discourage learning. Option C emphasizes document-driven processes, which contradict the Agile value of prioritizing working solutions over comprehensive documentation. Documentation is useful, but it should support value delivery, not dominate it. Option D highlights Agile techniques for efficiency, which reflects “doing Agile” rather than “being Agile.” Techniques such as stand-ups, boards, or retrospectives only create value when guided by an Agile mindset.

In Agile foundations, “being Agile” enables teams to continuously inspect and adapt their ways of working, improve relationships, and deliver meaningful outcomes. By focusing on adaptability and collaboration, organizations create environments where teams can respond effectively to uncertainty, learn from feedback, and consistently deliver value, which is the true intent of Agile.

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.