Alec the Geek

mobile version http://alecthegeek.mofuse.mobi/

Agile is not a panacea, neither is it all wrong

Posted by Alec on 23 January 2007

Andrew said last December

Another Anti-Agile Gripe « The Wandering Glitch 2

the ‘agile’ ethos promotes a mentality that actively avoids solving problems ahead of time. That leads to short-termism that ultimately bakes bugs into the code!

I really wanted to say something about this as the time but real life overtook me so here and now is my contribution to the never ending discussion of ‘Agile’ vs. ‘Waterfall’. First some obvious things:

  1. Anything done badly, including Agile, will fail
  2. There is no one size fits all. The correct approach is the one tailored to the produce the needed result given the requirements, team skills, politics and resource constraints

Agile attempts delays decisions as late as possible. In my experience this is potentially a “good thing”. I have lost count of the number of times, after a project has been moved to support, there has been general and widespread condemnation of the technical decisions made by the original team. Of course when you do ask the original team they say that the decision was made in the context of what was known at the time and if they did it over again then it would be a different decision.

In addition the requirements and environment in which the system operates change all the time, so the criteria on which the decision was made no longer apply.

One of Agile’s potential benefits is that is seeks to reduce the cost of change and make it as constant as possible during the life of the project — this is a worthy gaol no matter what methodology is followed.

Agile also recognises that a) we learn more as the project progresses and b) everything else changes around us. The approach is to delay decisions that can be reasonably delayed and to approach development with a process that makes change as cheap as possible.

The process that Andrew describes of avoiding the solving of problems that need to be fixed is not one I recognise. In fact I find myself, when doing re-factoring, thinking ahead to solving problems before they occur. So Andrew and I must be on different planets, which is strange considering we live in the same Melbourne suburb :-) .

I have limited experience of Agile and I have only used it in a few projects, however I have worn the hats of Agile developer, designer and manager. Agile has given me more choices during my projects and made my work more enjoyable, so that to me seems all positive. I intent to do more of it where and when I consider it appropriate.

powered by performancing firefox

7 Responses to “Agile is not a panacea, neither is it all wrong”

  1. [...] on January 23rd, 2007. Alec recently replied to one of my Agile diatribes with a very interesting set of comments. His point is that no project [...]

  2. So you’re saying Agile is neither perfect, nor the worst thing ever? Brave stance.

  3. Alec said

    Hej Tomas,

    That’s me — I should have become a diplomat :-) .

    On a more serious note, what I am saying is that you can make a mess of things no matter which approach you take and conversely no one a methodology is going to solve all your problems, despite what the vendors and evangelists say (I’m old enough to have seen snake oil before)

    So pick the approach that will give you the best result for the situation you are currently in, even though it may not be Agile, and be flexible.

    Personally though I like Agile thus far, so please give me more wherever reasonable.

  4. [...] on February 2nd, 2007. It seems that our little Anti-Agile spat generated a fair amount of traffic for both Alec and I. Alec’s excellent blog attracted a [...]

  5. James said

    Software development should be the goal, not documentation development. Agile can fail just as easily, I have seen this happen in some major banks. They had an attitude that “this agile stuff is so much cooler than the other stuff we do”, yet never focused on the iteration management.

  6. My, that fence looks comfortable… may i come and join you on it?

    Like all things, it’s a horses for courses decision… I don’t think there’s enough data yet about long term benefits/drawbacks maintenance-wise.

    I’m sure someone said a while back “object orientation is not a panacea, neither is it all wrong” and I’m sure 10 years from now it will be something else.

  7. gday sport.

    Another quote that seems almost designed for the Agile Ethos:

    If you don’t have time to do it right, where are you going to find the time to do it over?
    – fortune :-)

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>