PRINCE2 PRINCE2-Agile-Foundation - PRINCE2 Agile Foundation (Version 2) Exam

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

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.