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

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 Team Planning Workshop is primarily held to update the product backlog. This collaborative session allows the delivery team to break down, refine, and reprioritize user stories or tasks to prepare for the upcoming iteration or sprint. The team reviews the product backlog items, clarifies acceptance criteria, estimates effort, and commits to the planned work.

Updating the product backlog at this level ensures that detailed planning aligns with the overall project vision and release goals. It empowers the team to self-organize and manage their workload, supporting agile principles of autonomy and collaboration.

While the project dashboard (A) provides status reporting, the release map (C) focuses on higher-level release planning, and OKRs (D) relate to strategic objectives, these are not the central focus of the team planning workshop.

PRINCE2 Agile promotes team planning workshops as essential forums for translating business priorities into actionable, manageable work for delivery teams.

The Agile Enablement Workshop provides a collaborative environment where teams and stakeholders define critical agile artifacts, including the Definition of Ready. This definition specifies the criteria a user story or product backlog item must meet before work can begin, ensuring clarity and readiness.

The workshop facilitates alignment on quality standards, scope, and expectations, reducing ambiguity and improving flow through development cycles. By involving all key participants, the Definition of Ready is meaningful and practical, tailored to the project's specific context.

While starting up (A), kickoff (B), and initiation workshops (C) focus on project foundation and planning, they do not specifically focus on agile readiness criteria.

This workshop is essential for embedding agile practices within PRINCE2 governance and fostering effective delivery.

Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile, explains that the project management team structure defines how the project will be managed and delivered, including clarity around roles, responsibilities, and ways of working. A key element that should be included within this structure is a description of how products are to be produced, making option D the correct answer.

The project management team structure is not just a list of roles; it provides context on how delivery will operate in practice. This includes how teams are organized, how responsibilities are allocated, and how products will move from concept to completion. Describing how products are to be produced ensures there is shared understanding of the delivery approach, whether it is Agile, iterative, hybrid, or otherwise. This clarity supports coordination, accountability, and effective governance throughout the project lifecycle.

Option A, procurement and contract needs, belongs more appropriately to commercial or procurement management considerations rather than the team structure itself. Option B, a full and firm foundation for initiation, describes the purpose of the initiation stage rather than the contents of the team structure. Option C, arrangements for co-location or remote teams, relates to communication and working practices, which may support delivery but do not define the management structure.

Agile Foundation documents emphasize transparency and alignment between governance and delivery. Including a description of how products are to be produced within the project management team structure helps bridge management expectations with Agile delivery practices. It ensures that all stakeholders understand how work will be organized, how decisions will be made, and how value will be delivered. This supports Agile principles such as collaboration, empowerment, and adaptability while maintaining clear project-level control and accountability.