Is it Blasphemous to Criticize Agile?


This is how I was planning to start my post …

“…believe me … I do think agile works … in most … well if not in most cases then in many cases. That by implication means it is not a silver bullet for all situation. In fact, no technique, no methodology, no solution can be applied all situations and agile is no exception.

However, I have noticed a tendency among agilist to proclaim that if agile has not worked in a specific situation then the fault lies squarely on improper usage rather than any limitation of agile. All you have to do is apply agile properly and it would work. Who is to say what proper agile is? Agile manifesto does not help in determining what makes agile agile. Conversely, how do we judge what agile is not…”

…but then I saw this – Agile’s Teenage Crisis?. It provides 20 point criticism of Agile and how it is practiced. It is nice to know that the thought leaders are thinking about the same issues.

I don’t want to list the points – you better read the post.

However, there is one point that has been bothering me for some time and it is not fully addressed in the 20 points mentioned.

The point is about “Continuous delivery of valuable software”. Can we compare this to “CEO working to create value for shareholder”?

Do you see any similarity?

Both focus on the short term. CEO focuses on the next quarter result and its impact on stock price. They assume that anyway on the long term everybody is dead. This post nicely summarizes the dilemma of the CEO.

However, visionary CEO’s will always balance the short term and the long term.

Agile developers concentrate only on the current sprint and assume that if there is any architectural problem later code refactoring can take care of it. Big upfront design is frowned upon. Similarly if the agile team has experienced developers who can visualize the impact of every design decision things generally work out.

However, are all developers all so experienced that they can intuitively figure out what the right design is? How about the need to debate, introspect and visualize the impact of any design decision? Can it be done it your focus is always on delivering the next user story and how much business value it delivers?

Quoting Philippe Kruchten from Agile’s Teenage Crisis?

“…While agile practices could help control technical debt, they are also often at the root, the cause of massive technical debt…”

Udayan Banerjee on Google+
About these ads
Comments
3 Responses to “Is it Blasphemous to Criticize Agile?”
  1. MK says:

    Every application goes through its own lifecycle. From inception, through its useful life to eventual retirement. Can we say that Agile’s usefulness varies based on where in the Application life you put it to use. Sometimes you use Agile to built on a idea, where go-to-market is important, technical quality is less of a relevant or too expensive to gamble. When it proves its usefulness, you use a more clasical model to build your robust application, built to last longer. After which you switch back to agile to manage the incremental change in functionality. Is that been your observation too?

    • Udayan Banerjee says:

      If I get you right, you are saying that to build a robust application you need to do an upfront design.

      This is a hot topic – you will get diametrically opposite answer depending on who you ask!

  2. David McLean says:

    Udayan – thanks this is good thought provoking – I site right between the CEO and the developers so it appeals to me

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 987 other followers

%d bloggers like this: