Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile practices, explains that the organization practice is responsible for defining the products to be delivered and clarifying who will deliver them. This makes option C the correct answer. The organization practice focuses on establishing and maintaining a clear project management team structure, roles, responsibilities, and relationships to ensure effective delivery.
A key purpose of the organization practice is to ensure that accountability for producing each product is clearly defined. This includes identifying roles such as project manager, product owner, team members, and supporting roles, and ensuring that everyone understands what they are responsible for delivering. By defining who is involved and how they interact, the organization practice creates the foundation for collaboration, decision-making, and governance.
Option A, plans, focuses on when and how work will be carried out rather than who will deliver specific products. Planning answers questions about timelines, sequencing, and dependencies but assumes that responsibilities are already defined. Option B, the business case, explains why the project is worthwhile by outlining expected benefits, costs, and risks, not who will deliver products. Option D, risk, addresses uncertainty and potential threats or opportunities, not product ownership or delivery responsibility.
Agile Foundation documents emphasize that clarity of roles and responsibilities is especially important in Agile environments, where teams are empowered and self-organizing. The organization practice supports this empowerment by setting clear boundaries and accountability while avoiding unnecessary hierarchy. It ensures that everyone involved understands their contribution to value delivery and how their work fits into the wider project.
By defining both the products to be delivered and who will deliver them, the organization practice supports transparency, effective collaboration, and confidence among stakeholders. This clarity enables Agile teams to work autonomously within agreed structures, supporting consistent, high-quality delivery aligned with Agile and PRINCE2 Agile principles.

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.