A. Customer collaboration over a constant indefinite pace
B. Customer collaboration over contract negotiation
C. Customer collaboration over feature negotiation
D. Customer collaboration over ongoing internal conversation
The Correct Answer is
B. Customer collaboration over contract negotiation
Explanation
The Agile Manifesto, which is a foundational document for Agile development, emphasizes the value of individuals and interactions, working software, customer collaboration, and responding to change. Specifically, it prefers “customer collaboration over contract negotiation.” This principle highlights the importance of working closely with customers to understand their needs and adapt to changes, rather than sticking rigidly to contract terms that may not reflect the current needs or challenges of the project. This approach fosters a more flexible, responsive, and ultimately productive relationship between service providers and their clients.
The other options, while incorporating elements of Agile thinking or common phrases related to customer engagement, are not directly quoted from the Agile Manifesto.
The Agile Manifesto, formulated in February 2001 by seventeen software developers, outlines four fundamental values and twelve principles designed to guide software development in the Agile methodology. These values and principles emphasize adaptability, customer collaboration, and the continuous delivery of valuable software.
Here’s a closer look at each of the four core values of the Agile Manifesto, including the specific value you asked about
1. Individuals and interactions over processes and tools
This value prioritizes the human element of software development, recognizing that the best work comes from people who communicate well and work together efficiently. While processes and tools are important, they should serve to facilitate human interaction rather than hinder it.
2. Working software over comprehensive documentation
Agile development values documentation, but it places a higher priority on delivering functional software. The idea is that a working product is more valuable to the customer and users than extensive documentation that outlines every detail of the plans and processes but delays actual product delivery.
3. Customer collaboration over contract negotiation
This is the value you mentioned. It emphasizes the importance of ongoing collaboration with the customer throughout the development process. Agile teams seek to work closely with customers to understand their needs and feedback, adjusting the project direction accordingly. This approach is favored over sticking rigidly to the terms of a contract that may not allow for the flexibility needed to deliver the best possible outcome.
4. Responding to change over following a plan
While Agile projects start with a plan, they are built to accommodate change. The Agile methodology recognizes that requirements, goals, and user needs can evolve throughout a project. Agile teams are prepared to adapt to these changes to provide the most value to the customer, rather than rigidly adhering to an initial plan.
The Agile Manifesto and its values represent a shift from traditional, plan-driven approaches to software development (often referred to as “waterfall”) to a more iterative, flexible approach. The principles further elaborate on these values, guiding how to apply them in day-to-day development practices, such as delivering working software frequently, welcoming changing requirements, and building projects around motivated individuals.
The emphasis on “customer collaboration over contract negotiation” specifically guides teams to engage customers as active participants in the development process. This collaborative approach ensures that the development team can make adjustments based on real-time feedback, leading to a product that better meets the customer’s needs and expectations.
Other Leading SAFe 6.0 Question – Why is it important to decouple deployment from release?