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

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.

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.

Psychological safety is a critical enabler of effective Agile teams, and Agile Foundation materials often reference the four progressive levels of psychological safety: inclusion safety, learner safety, contributor safety, and challenger safety. Among these, contributor safety is the level that specifically encourages individuals to share their ideas, knowledge, and skills openly while making meaningful contributions to the team’s work.

Contributor safety exists when team members feel trusted and empowered to apply their skills, experience, and ideas without fear of embarrassment, rejection, or negative consequences. At this level, individuals are not only accepted as part of the team but are also encouraged to actively participate, take ownership of tasks, and contribute value. Agile environments rely heavily on this level of safety because collaboration, cross-functional work, and self-organization depend on people confidently sharing what they know and what they can do.

Option C, inclusion safety, is more foundational. It ensures that individuals feel accepted and respected as members of the group, but it does not necessarily mean they feel safe enough to contribute ideas or skills. Option D, learner safety, focuses on the ability to ask questions, experiment, and make mistakes in order to learn. While important, it centers on learning rather than contribution. Option A, challenger safety, represents the most advanced level, where individuals feel safe to challenge existing ideas, processes, and decisions. This goes beyond sharing skills and ideas into constructive dissent.

Agile Foundation guidance emphasizes contributor safety because Agile teams thrive when every member actively contributes to delivering value. When contributor safety is present, teams benefit from diverse perspectives, improved problem-solving, higher engagement, and stronger accountability. This level of psychological safety directly supports Agile principles such as collaboration, transparency, and continuous improvement, making option B the correct answer.