That’s not Agile!
You haven’t dotted the I’s, crossed the T’s and conformed to this checklist! You’re not following dot point 27 of document three! Agile is only for software development! Every time I hear statements like this it perturbs me greatly, they are usually repeated with such conviction that I know I have to set about demystifying these rumours lest they continue to grow.
Agile is not an ISO standard or a check list to be followed blindly for the sake of it.
It’s simply a framework, if you like an umbrella term for a set of values and principles that have been shown to improve efficiency, productivity, and quality. Agile is not just a software development methodology though, it’s a way of working that builds on a set of values and principles to deliver business value and manage risks.
Agile methods are adaptive; they have frequent checkpoints and feedback loops that are used to manage and reduce risk. It’s pragmatic; if something doesn’t work it can and should be adapted.
Agile can be used for all sorts of teams and environments as well as being able to be used at the governance level for portfolio management and at the project level for delivery.Its’ strengths lie in the core values and principles and we should take time to remember them. Continue reading “‘A Rose by any other name?’”