Important PRINCE2-Agile-Foundation Exam Questions

Answer: D

Explanation:

Agile Foundation guidance, aligned with PRINCE2 Agile concepts, explains that integrated elements are used to describe different aspects of how a project is structured and delivered. Among these elements, the ''people'' element specifically defines who is working on the project and who is affected by the project, making option D the correct answer.

The people element focuses on roles, responsibilities, relationships, and stakeholders involved in the project. It identifies not only the delivery team members but also sponsors, users, customers, suppliers, and any individuals or groups impacted by the project's outcomes. Agile and PRINCE2 Agile both emphasize that successful delivery depends heavily on people, collaboration, and clear accountability. Understanding who is involved and affected ensures effective communication, engagement, and decision-making throughout the project lifecycle.

Option A, the project context, describes the environment in which the project operates, including organizational, regulatory, and external factors, but it does not specifically define who is involved. Option B, the PRINCE2 practices, focuses on areas such as risk, quality, plans, and progress, providing guidance on what needs to be managed rather than who is involved. Option C, the PRINCE2 processes, outlines the flow of activities and decision points during the project, not the people performing or impacted by them.

Agile Foundation documents stress that Agile delivery is people-centric. Self-organizing teams, empowered roles, and active stakeholder involvement are core to Agile success. The people element supports this by ensuring clarity around roles, expectations, and collaboration pathways. By clearly defining who is working on the project and who is affected by it, teams can build trust, manage stakeholder needs effectively, and adapt to change more smoothly. This alignment of people with purpose and value delivery is central to both Agile principles and PRINCE2 Agile integration.

Answer: A

Explanation:

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

Explanation:

In Agile Foundation guidance, the risk practice is explicitly responsible for the identification, assessment, and management of uncertainties, making option A the correct answer. Risk is defined as uncertainty that, if it occurs, will have a positive or negative impact on objectives. Agile recognizes that uncertainty is inherent in complex and adaptive work, so effective risk management is essential to successful delivery.

The risk practice focuses on proactively identifying uncertainties early, assessing their likelihood and impact, and determining appropriate responses. Agile Foundation documents emphasize that risk management in Agile is continuous rather than a one-time activity. Risks are regularly reviewed, updated, and addressed throughout the lifecycle as new information emerges. This aligns with Agile principles of transparency, inspection, and adaptation, allowing teams to respond to uncertainty in a timely and informed manner.

Option B, plans, focuses on outlining how objectives will be achieved and how work will be organized over time. While planning may take risks into account, it does not primarily identify or assess uncertainties. Option C, quality, ensures that outputs meet agreed standards and acceptance criteria but does not deal directly with uncertainty. Option D, business case, justifies why a project should proceed by outlining costs, benefits, and risks at a high level, but it does not actively manage or assess uncertainties on an ongoing basis.

Agile Foundation guidance highlights that Agile approaches often reduce risk by delivering incrementally, seeking early feedback, and validating assumptions quickly. However, this does not eliminate the need for a structured risk practice. Instead, risk management supports Agile delivery by making uncertainties visible and manageable. By embedding risk identification and assessment into regular team activities, organizations can make better decisions, protect value, and increase confidence among stakeholders while still maintaining flexibility and responsiveness to change.

Answer: D

Explanation:

The Delivering level is responsible for the day-to-day management and decision-making within the constraints set by the project manager. Delivering teams carry out the actual work to create the project products and manage their activities under the project's governance framework. The Project Manager manages the overall project, while directing sets the strategic direction and commissioning authorizes initiation.

This separation ensures clear responsibilities and empowers the delivery teams to self-manage within defined boundaries.

Answer: A

Explanation:

In Agile Foundation guidance, the team coach plays a key role in supporting one or more Agile teams in adopting and improving Agile ways of working. A core responsibility of the team coach is to liaise with the agile coach, making option A the correct answer. This relationship ensures alignment between team-level coaching and organization-wide Agile adoption.

The team coach focuses primarily on the day-to-day effectiveness of the team. This includes helping the team understand Agile principles, improve collaboration, enhance communication, and continuously improve their ways of working. The agile coach, on the other hand, typically operates at a broader level, supporting multiple teams, leaders, and the organization as a whole in embedding Agile culture and practices. By liaising with the agile coach, the team coach ensures that insights, challenges, and progress at the team level are shared and addressed consistently across the organization.

Option B, liaising with the project manager, is not a primary responsibility of the team coach in Agile foundations. While coordination may occur, Agile reduces dependency on traditional command-and-control roles. Option C, liaising with the chief product owner, is also not central to the team coach role, as product ownership focuses on value and prioritization rather than team dynamics and Agile maturity. Option D, liaising with project assurance, aligns more with governance and compliance functions rather than coaching responsibilities.

Agile Foundation documents emphasize that effective coaching relies on collaboration between coaching roles. The team coach provides detailed, practical feedback from the team, while the agile coach offers strategic direction, consistency, and organizational support. This collaboration strengthens Agile adoption, helps remove systemic impediments, and ensures that teams are supported both locally and at scale. By liaising with the agile coach, the team coach helps create a coherent, sustainable Agile environment focused on continuous improvement and value delivery.