How to reflect on your own agility
A lot of people are busy working in the “agile industry”, as there seems to be one. Scrum Masters, Product Owners and Agile Coaches of all kinds are swarming the market place, looking for their next “agile transformation”.
To me, that’s fine. As long as it makes people happy and money is well spent of course.
However, if you are in the business of telling other people how to be agile and especially if you are judging anyone on “how agile they are”, then at least have the decency to check your own agility.
The Manifesto for Agile Software Development gives you plenty of hints on how to do that. Just start by looking at the first sentence of that manifesto:
We are uncovering better ways of developing software by doing it and helping others do it.
That single line of text gives you three important things to reflect on:
- What better way(s) of developing software have I uncovered recently? And why the heck does that matter?
- Did I even develop software lately? How did it turn out? What value did it bring? To whom? Did I learn anything new? Did doing it make me happy?
- Did I help other people develop software? Did it actually help them? Did they learn anything? Did it increase their options? Did it make them happy?
If you are not involved in any of that software and programming stuff, just replace the piece that says “of developing software” with the thing that you do.
What DO you do by the way?
That important question to myself: “what the heck am I supposed to do again?” often sends me straight back to reality when I inadvertedly strayed from it. Again.
Be careful with telling people what to do and especially with judging others. Start with yourself. Have the manifesto and those questions for reflection close for when you need them 🙂