In the past, a team has been unable to deliver solutions in a timely manner and they feel this is due to the customer being unable to decide what they want. The team has decided to ask the customer to “sign-off” on their requirements. This violates the following value statement:

The team's decision to enforce a "sign-off" on requirements is a direct shift from a collaborative, partnership-based approach to a more rigid, contractual one. This action is taken to lock down scope and create a formal agreement that can be used to resist future changes, which is characteristic of contract negotiation. It fundamentally undermines the agile value of working closely and continuously with the customer to discover and refine their needs throughout the delivery lifecycle. Instead of collaborating to manage change, the team is creating a process to prevent it, which is the essence of an adversarial, contract-based relationship.

A. Individuals and interactions over process and tools: While a new process (sign-off) is being introduced, the core violation is its contractual and adversarial nature, making D a more specific and accurate answer.
B. Prioritizing outputs over outcomes: This describes an agile anti-pattern but is not one of the four core values stated in the Agile Manifesto, which the question is referencing.
C. Working solutions over comprehensive documentation: The problem is not the documentation itself, but its use as a rigid contract to halt collaboration and change, which is the central point of option D.

1. Manifesto for Agile Software Development. (2001). The third value explicitly states, "Customer collaboration over contract negotiation." The scenario described is a classic example of reverting to contract-style negotiation instead of maintaining collaboration. Retrieved from agilemanifesto.org.

2. IIBA. (2017). Agile Extension to the BABOK® Guide, Version 2. In Section 3.2.2, "The Agile Mindset," the guide explains that "Customer Collaboration over Contract Negotiation" fosters a cooperative relationship rather than an adversarial one. Introducing a sign-off to manage an "indecisive" customer creates an adversarial dynamic.

3. Cohn, M. (2010). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional. In Chapter 3, "Agile Values," Cohn discusses that agile teams prefer to collaborate with customers on an ongoing basis rather than negotiating a detailed contract (like a signed-off requirements document) upfront. The sign-off represents a move toward the "contract negotiation" side of the value statement.