The scenario describes the development team and the product owner (acting as the customer proxy) working in a close partnership. When the goals change, they collaborate to understand the new requirements, re-prioritize work, and find a way to deliver the most important features within the constraints. This active and continuous partnership to respond to change and define value is the core of the agile value "Customer collaboration over contract negotiation." The focus is on the shared understanding and flexible adaptation rather than rigid adherence to an initial plan or contract.

A. Contract negotiation: This is the less-valued counterpart in the Agile Manifesto. The team is collaborating to find a solution, not formally renegotiating a contract's terms and conditions.

C. Comprehensive documentation: This is another less-valued item in the Agile Manifesto. The scenario focuses on communication and collaboration, not the creation of detailed documentation.

D. Processes and tools: This is also a less-valued item. The team is demonstrating the value of individuals and interactions by working together, rather than relying on a specific process or tool to manage the change.

1. Agile Extension to the BABOK® Guide

Version 2

IIBA. Section 2.2.3

"Customer Collaboration over Contract Negotiation

" states

"Agile approaches focus on a collaborative approach to working with customers to understand their needs and develop a solution that meets those needs... This collaborative approach allows the delivery team to gain a deeper understanding of the customer's needs and provides the customer with a deeper understanding of the solution as it evolves." The scenario is a direct application of this principle.

2. Manifesto for Agile Software Development (agilemanifesto.org). The third of the four core values is explicitly stated as "Customer collaboration over contract negotiation." The described behavior of the team working with the product owner to adapt to new goals perfectly embodies this value.

3. Dybå

T.

& Dingsøyr

T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology

50(9-10)

833-859. In their review

the authors highlight that a key principle of agile methods is close collaboration with the customer throughout the project to ensure the system meets their needs

which is precisely what the team in the scenario is doing. (DOI: https://doi.org/10.1016/j.infsof.2008.01.006)