Free PRINCE2 PRINCE2-Agile-Foundation Practice Exam with Questions & Answers

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.

‘Being agile’ refers to embracing the mindset and principles of agility, not just following agile practices mechanically. Option D illustrates ‘being agile’ because the customer has embraced the iterative approach and focuses on requirements that add real value, which reflects true agile values such as customer collaboration, responding to change, and delivering value early and continuously.

Options A, B, and C describe activities related to agile practices but don’t necessarily reflect the deeper agile mindset or cultural shift fundamental to ‘being agile’.

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.

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.