What statement is NOT part of the Agile Manifesto?

Question

Options

• AWorking software over comprehensive documentation.
• BCustomer collaboration over contract negotiation.
• CWorking software is the primary measure of progress.
• DGood architectures are built up front so that teams can focus on development.
• EContinuous attention to technical excellence and design enhances agility.
• FBusiness people and developers must work together daily throughout the project.

• B
  4% (1)
• D
  92% (23)
• E
  4% (1)

Explanation

Option D directly contradicts the Agile Manifesto - it promotes "big design up front," which Agile explicitly rejects. The manifesto's 12th principle states the opposite: "The best architectures, requirements, and designs emerge from self-organizing teams," meaning good architecture evolves iteratively, not in a pre-planned phase.

The other options are all genuine Agile statements: A and B are two of the four core Values of the manifesto (working software over documentation; customer collaboration over contract negotiation). C, E, and F are all drawn directly from the 12 Principles - working software as the primary measure of progress, continuous attention to technical excellence, and daily collaboration between business people and developers.

Memory tip: The Agile Manifesto is fundamentally anti-waterfall. Any answer that sounds like traditional waterfall planning - especially "up front" design, rigid contracts, or big documentation phases - is almost certainly the wrong answer when the question asks what Agile supports, and the right answer when asked what Agile rejects.

No community discussion yet for this question.