What does NOT belong to cornerstones of the agile manifesto?

Question

Options

• AIndividuals and interactions over processes and tools
• BWorking software over comprehensive documentation
• CProcesses over people
• DCustomer collaboration over contract negotiation
• EResponding to change over following a plan

• A
  2% (1)
• B
  4% (2)
• C
  93% (53)
• E
  2% (1)

Explanation

C ("Processes over people") is the odd one out because it directly contradicts the Agile Manifesto's first value, which prizes individuals and interactions over processes and tools - Agile explicitly de-emphasizes rigid processes in favor of human collaboration. Options A, B, D, and E are all verbatim or near-verbatim restatements of the Manifesto's four core values, which were established in 2001 by the Agile Alliance. The trap in option C is that it sounds plausible - processes do exist in Agile - but the Manifesto's position is the opposite: people come before processes, not the other way around.

Memory tip: The Manifesto always puts the "human/flexible" thing on the left and the "rigid/traditional" thing on the right (e.g., "X over Y"). Any choice that flips that hierarchy - like putting processes above people - is the impostor.

No community discussion yet for this question.