the Agile Manifesto

We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

-- Excerpted from http://www.agilemanifesto.org

One CounterAgileSentiment expressed in response to the above directly quoted excerpt is from TerryMiramax^?:

• Individuals and interactions over processes and tools
  • because quality inspection and demands for reproducibility are a threat to the benefits our union fought for us; we do not want to lose our jobs
• Working software over comprehensive documentation
  • because it's so educating to invent the wheel over and over again
• Customer collaboration over contract negotiation
  • because commitment is always hazardous
• Responding to change over following a plan
  • because chaos is fun

See AgileDevelopment. Perhaps there could be point/counterpoint pages for WhyAgileDevelopmentWorks^? and WhyAgileDevelopmentWorksNot^?. Also see CounterAgileSentiment for more references to pages and books making the case against various agiles methods/practices.