Comments on: Is having Iterations Enough to be Agile? http://www.fuzzylizard.com/archives/2007/01/03/847/ My thoughts on Agile, Java and Ruby on Rails (mostly) Thu, 08 Jan 2009 20:42:42 +0000 http://wordpress.org/?v=2.7 hourly 1 By: fuzzylizard http://www.fuzzylizard.com/archives/2007/01/03/847/comment-page-1/#comment-9632 fuzzylizard Wed, 10 Jan 2007 03:54:18 +0000 http://www.fuzzylizard.com/archives/2007/01/03/847/#comment-9632 Interesting, and thanks for the link. I like the term and would have to agree that it is definitely an anti-pattern. I think part of the problem inherent in this anti-pattern is a sense of fear and a real sense that they have to get it right the first time. The fear would be the fear of getting it wrong or making mistakes (again and again and again). The company wants to be Agile, but they also do not allow their development team to make mistakes or to get it wrong. This means that the team must get everything right before they do anything. They create iterations in order to manage some of those requirements, but they are still implementing waterfall to ensure they don't get it wrong because this project has to succeed. This means doing things right which means Agile (in today's age), but it also means understanding what you are doing up front. This means singing off on requirements and doing design up front. This means waterfall. Interesting, and thanks for the link. I like the term and would have to agree that it is definitely an anti-pattern.

I think part of the problem inherent in this anti-pattern is a sense of fear and a real sense that they have to get it right the first time. The fear would be the fear of getting it wrong or making mistakes (again and again and again). The company wants to be Agile, but they also do not allow their development team to make mistakes or to get it wrong.

This means that the team must get everything right before they do anything. They create iterations in order to manage some of those requirements, but they are still implementing waterfall to ensure they don’t get it wrong because this project has to succeed.

This means doing things right which means Agile (in today’s age), but it also means understanding what you are doing up front. This means singing off on requirements and doing design up front. This means waterfall.

]]> By: pmarchant http://www.fuzzylizard.com/archives/2007/01/03/847/comment-page-1/#comment-9600 pmarchant Tue, 09 Jan 2007 07:31:28 +0000 http://www.fuzzylizard.com/archives/2007/01/03/847/#comment-9600 The words "iterative waterfall" come to mind. Google search result number 2: http://www.danube.com/blog/kanemar/the_staggered_iterative_waterfall_anti_pattern_part_1.html A case of staggered-iterative-waterfall anti-pattern. The words “iterative waterfall” come to mind.

Google search result number 2:
http://www.danube.com/blog/kanemar/the_staggered_iterative_waterfall_anti_pattern_part_1.html

A case of staggered-iterative-waterfall anti-pattern.

]]>