Agile versus methodologies

This post is more than 13 years old.

Posted at 07:00 on 14 April 2011

If the Agile Manifesto says this:

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.

Then why do some people describe Agile as “an umbrella term covering a number of methodologies, such as Scrum and XP”? It sounds like a bit of a contradiction in terms to me.

Not that there's anything bad about methodologies of course -- it's just that it seems to me that the whole point of the Agile Manifesto is to put them firmly in their place.