PRINCE2 Agile Foundation V2 PRINCE2-Agile-Foundation Exam Questions

Answer : A

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.

Answer : B

Agility is defined as the ability to embrace and respond to change quickly and effectively. It is a core principle of agile methods, enabling organizations and teams to adapt to evolving business needs, customer feedback, and external factors while delivering value continuously.

This definition contrasts with traditional change control, which often aims to prevent changes (C). Agility promotes flexibility, learning, and continuous improvement, but the belief that anyone is capable of learning (D), while important, is a cultural aspect rather than a direct definition of agility. The sequence of actions (A) relates more to processes than agility itself.

Understanding agility as the capacity to adapt ensures project approaches remain relevant in dynamic environments.

Answer : B

The Managing Product Delivery process includes agreeing on and controlling the requirements for the delivery of specialist products. This process ensures that team managers understand the scope and quality expectations before work begins and that delivery aligns with the project plan.

Initiating a project and starting up a project establish overall direction but do not handle detailed delivery requirements. Managing a stage boundary reviews progress and plans the next stage.

This process maintains clarity and accountability for delivery within PRINCE2's framework, facilitating effective control over specialist products.

Answer : A

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.

Answer : A

When blending PRINCE2 with agile, adopting an agile mindset is the most important factor for success. The mindset involves embracing agile values such as flexibility, collaboration, delivering value incrementally, and being responsive to change. Without this cultural and attitudinal shift, the use of agile techniques or processes becomes superficial and fails to deliver the benefits of agility.

PRINCE2 is a highly structured project management method with defined roles, processes, and controls. Integrating agile methods requires more than just overlaying practices like Scrum or Kanban; it demands a fundamental shift in thinking about leadership, governance, team dynamics, and customer involvement.

Fostering psychological safety (B) is indeed important because it allows teams to express ideas, take risks, and innovate without fear of negative consequences. However, this psychological safety is a component of the broader agile mindset.

Using agile techniques (C) and following processes (D) are enablers but do not guarantee agile success. Teams may mechanically perform ceremonies without understanding the principles behind them.

The PRINCE2 Agile guidance emphasizes that the mindset must permeate all levels of the project and organization. Leaders and teams should adopt agility as a philosophy, not just a set of practices.

Answer : B

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.

Answer : C

Agile Foundation guidance describes the project canvas as a living, lightweight artifact that supports alignment, transparency, and ongoing benefit realization throughout the project lifecycle. It should not be treated as a one-time planning document. The correct point at which the project canvas should be both updated and used to assess whether intended benefits have been or will be realized is at the end of each delivery stage, making option C the correct answer.

Agile and PRINCE2 Agile approaches emphasize incremental delivery and continuous validation of value. Each delivery stage produces usable outputs or increments that can be reviewed against expected outcomes and benefits. Updating the project canvas at the end of each delivery stage allows the team and stakeholders to reflect on what has actually been delivered, what has changed, and whether assumptions made earlier are still valid. This includes reassessing benefits, risks, stakeholders, and priorities based on real evidence rather than predictions.

Option A, the end of the pre-project stage, is too early, as no meaningful delivery has occurred to assess benefits. Option B, the end of initiation, focuses on planning and setup rather than value realization. Option D, the end of the final delivery stage, is too late because it limits opportunities to adapt if benefits are not being realized as expected.

Agile Foundation documents stress the importance of frequent inspection and adaptation. By reviewing and updating the project canvas at the end of each delivery stage, teams can make informed decisions about continuing, pivoting, or stopping work. This supports effective governance while preserving agility. Regular benefit assessment ensures that the project remains aligned with business objectives and continues to justify investment, reinforcing Agile's focus on value delivery rather than simply completing planned activities.