Agile vs. Waterfall: Where's the Responsibility?

Sunday, January 6th, 2008

In an ongoing series about Agile, Scott Sehlhorst posted this nice tidbit today.

Agile Absolves Developers:

A waterfall development team, in contrast, is avoiding responsibility. It may be that the team does not consciously realize that they are doing it, or even intend to do it. Intelligent people can agree to disagree about the reasons that an organization does or does not pursue agile - that’s another debate. A team may not be able to handle the additional responsibility. An organization may be unwilling to create an environment that makes this ownership possible.

[Via: Tyner Blain]

Scott, don't worry about posting it early! You gave me something to read tonight, especially with the great links!!! :)

More fun from Programmers

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Reddit
  • Slashdot
  • Technorati
  • description
  • NewsVine
  • StumbleUpon
  • E-mail this story to a friend!
  • Sphinn

Filed under Programmers, Software Design. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses - Join the Conversation to “Agile vs. Waterfall: Where's the Responsibility?”

  1. Scott Sehlhorst Says:
    January 6th, 2008 at 11:48 pm

    Thanks. This ends up being a surprisingly touchy subject for a lot of people. I’ve found a lot of people that “don’t believe the hype” and rightly so - because they have judged agile methodology based on the writings of a few people who don’t share anything more than hype. I wish more people would find the people like Kelly and Levant and Mishkin and others who write valuably from their real world experiences. It would change (or open) a lot of minds.

  2. jamiegrove Says:
    January 7th, 2008 at 7:54 am

    Thanks for the comment, Scott. I completely agree. Most of the hype tends to come from those new to the field, which is an immediate turn off to many established programmers (for good reason too).

    Yet, there are plenty of guys ut there with gray hair who believe in agile methods. I’m one of them! :)

    Frankly, adapting agile methods would extend a lot of careers. Not to mention making programming fun (and productive) again.

Leave a Reply