Comments on: The Staggered-Iterative-Waterfall (Anti-)Pattern, Part 1

By: Quora

Quora — Tue, 01 Feb 2011 01:48:48 +0000

How would it be best to implement an outsourced and off-shored QA team with an in-house development team using an agile methodology?…

This isn’t Agile software development. This is iterative waterfall [1] [2] … often called ScrumFall or WaterScrum and is a common anti-pattern. From personal experience this model of development is fugly [3]. My most honest reply to this question is…

By: Kane Mar

Kane Mar — Wed, 19 Jul 2006 17:47:43 +0000

I recieved this trackback a while ago:

http://agilitateur.azeau.com/index.php?itemid=33&catid=8

It’s written as a response to an article by Dave Nicolette, but has links to this article. I orgininally dismissed it out of hand. The author makes a number of assumptions that are demonstrably false (i.e., false by demonstration).

To quote: “Nevertheless, performing all the activities in the same iteration is not an easy job … The question is : can they fully achieve it ? Obviously not.”

Obviously not? I must object! In any case, regardless of how I personally feel about the article I now think it’s only fair to present you (the audience) with an alternative point of view.

By: Neenu Sachdev

Neenu Sachdev — Thu, 02 Feb 2006 13:22:26 +0000

I would agree with the author…

From the Business/Client Prespective: There is a steep learing curve with the clients. They hear the buzz words like RUP and get all fired up. At some point they try to equate the RUP model to the Waterfall model and get very confused. They have trouble understanding the requirements as use cases. They are used to thinking linearly like a waterfall model and have trouble comprehending the iterativeness of the model.

I thinks the author has captured very fine details like “iterative” being overloaded; which is very good.