Friday, March 9, 2012

Misguided Agile - "Agile" != "Faster"

Yes, "Agile" does not look same as "Faster", it does not even spell same and it does not have same meaning. If you see a project on Agile causing lots of pain to everybody around then a question should be asked - why are we doing Agile?

And if in the answer, project owner mentions word "Faster" then chances are high this is misguided agile, a guided missile that is going to land on your project and team. This is true even if Faster is the last word of the fifth reason for choosing Agile. It is like hero word, that takes the whole screen of mind even when other words exist.



In my view Agile is about getting software right. Consider a team building a software in isolation and bringing it out to customer after a year only to be denied acceptance. Customer says, "that's not what i wanted ...". There was a time when this was not only happening but was happening a lot. And at that time we wanted a way to collaborate with Customer, to create right software, a software that customer wants and will use.

Fast forward few years and now we have a situation where even if you don't have a customer in sight, even when things can be completely defined beforehand, we still need Agile because it has started meaning Faster. It should be ability to respond to changes but it is about getting more quickly from same resources. While Faster might be and generally is a side effect of Agile, the basics have to be kept in mind. There are subtle changes to Agile that make this process lose its beauty and make this a ugly daily reporting tool.