How to use Agile Manifesto?

White Rose

Generally, I like elegant and simple rules. They make life super-easy. For example: green light – go, red light – stop. There is nothing to interpret and not much to think about. You just make it a habit: stop on red, go on green. However, not everything is so clear-cut. Sometimes we have shades of red and shades of green and quite a few shades of grey. Take agile manifesto for example.

There are four values that help you set your priorities straight. Which are:

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

And, of course, even thought “we value things on the right, but we value things on the left more.” The question is to what degree? What criteria can we set here? Perhaps, one approach is to ask if things on the right, as they are in your environment right now, actually help facilitate the things on the left? Are processes and tools helping individuals do their work and facilitate interactions? Is documentation supporting the working software? Are contracts flexible enough and support continuing customer collaboration? Is the planning process continuous and helps incorporate change? Perhaps, if you make it a habit to ask these questions, eventually you might find things to be getting more agile in your environment?