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

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

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

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.

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.

Delegation poker is a collaborative game used to define and clarify decision-making authority within teams. It helps teams agree on who has the power to make decisions for specific areas, from the team level to senior management. Using cards representing different levels of delegation, team members discuss and align expectations, ensuring clarity and reducing conflicts.

This technique fosters transparency, shared ownership, and empowerment, which are critical for agile teams operating under PRINCE2 governance. It also helps balance autonomy and control, supporting the principle of manage by exception.

Other options: a team skills matrix documents competencies, personas represent user archetypes for design, and magic estimation is a sizing technique — none focus on decision authority.

Delegation poker aligns well with PRINCE2 Agile’s emphasis on defined roles and empowered teams.

Artificial Intelligence (AI) in PRINCE2 Agile is recognized as a tool that can assist in reducing uncertainty and ambiguity by providing data-driven insights, predictive analytics, and automation of routine tasks. This support helps teams better understand changing environments and respond faster, thereby addressing complexity associated with change initiatives.

While AI can add complexity if misused, PRINCE2 Agile focuses on its beneficial role in supporting decision-making and reducing unknowns rather than complicating governance or communication.

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.

A key benefit of being and doing agile is increasing user satisfaction by delivering value early and continuously, adapting to feedback, and ensuring the product meets real user needs. Agile approaches emphasize collaboration with customers and iterative delivery, which enhances satisfaction compared to traditional, rigid methods.

While following processes (A) and using agile techniques (B) are means to an end, they do not directly guarantee benefits. Focusing solely on tasks (D) risks losing sight of value delivery.

User satisfaction is a central measure of agile success and reflects the effective application of agile principles.

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.