Comments on: The Difference Between Waterfall, Iterative Waterfall, Scrum and Lean Software Development (In Pictures!)

By: the rasx() context » Blog Archive » Some Simple Scrum Words

the rasx() context » Blog Archive » Some Simple Scrum Words — Fri, 11 Dec 2009 00:50:08 +0000

[...] I was perhaps more biased toward Iterative Waterfall Development… “This approach carries less risk than a traditional Waterfall approach but is still far more risky and less efficient than a more Agile approaches. The focus is on delivering a sprint of work as opposed to a series of valuable/shippable features. The most commonly occurring issue in this type of scenario (in my experience) is bottle necking.” —agile101.net [...]

By: Dan

Dan — Wed, 25 Nov 2009 16:55:00 +0000

I like the lean method the most, but I would modify it to include a separate and longer “planning” section (requirements and such) at the beginning.

By: taraleewhitaker

taraleewhitaker — Wed, 28 Oct 2009 16:30:37 +0000

Hi Reow,

I’m not sure I follow your comment. Lean is anything but an ‘epic fail’… /

Could you elaborate?

Thanks,

Tara

By: Reow

Reow — Tue, 27 Oct 2009 23:59:17 +0000

Thanks for showing us that Lean = Epic Fail. I hadn’t realized till you pointed it out.

By: N GowriSankar

N GowriSankar — Mon, 26 Oct 2009 05:00:22 +0000

These pictures are very useful in getting the differences. i’m practicing scrum practices in my project, but was not able to tell the fine difference between the iterative waterfall and scrum models.

By: Ashley

Ashley — Thu, 08 Oct 2009 10:37:09 +0000

Hey man I must mention that I was very confusing and did not even understand the differences between Waterfall, its iterative type and Scrum. I am clear now. Though I was stuck in your text explanation, your pictures helped me to understand. Thank you very much buddy.

By: Jhon Williams

Jhon Williams — Wed, 07 Oct 2009 11:46:49 +0000

Good post… its very easy to understand and i liked your way of explanation.

By: Jef

Jef — Tue, 06 Oct 2009 15:11:47 +0000

Wow, great explanation, nice set of picture, this is exactly what I needed to show to people in my business the difference between the method. Thanks!

By: Different Flavours of Waterfall and Agile Development | Geek4Eva

Different Flavours of Waterfall and Agile Development | Geek4Eva — Mon, 28 Sep 2009 23:02:10 +0000

[...] Here’s a quick and simple overview of the main differences between Waterfall Development, Iterative Waterfall Development, Scrum/Agile Development and Lean by Agile101.net [...]

By: Douglas Stein

Douglas Stein — Fri, 18 Sep 2009 14:09:08 +0000

How to convince clients to use Agile while meeting their needs for predictability?

0) Make sure it’s a project which can use Agile. Web apps? Almost always. Embedded guidance software for a deep space probe? Almost never.

1) Propose a fixed burn-rate. That is, propose a team that is right-sized to the skills and scale of the project.

2) Propose a fixed sprint size (2 or 3 weeks is typical) if you’re a fan of Scrum; if you’re prefer Extreme you can propose 6-8 week releases composed of 3-4 2-week iterations.

3) Propose a contract where the client can change anything they want for the “next” sprint or iteration – and where they can accept/reject each story as it completes. In exchange, the client has to be sure there is a single voice (not a committee) who is available to (or embedded with) the team.

4) Propose that the client can cancel at the end of any sprint/release with no penalty and will be left with shippable software that has been accepted.

One Agile firm I’ve brought into clients has the data indicating that many times clients stop development at around 85-90% of the original budget because the product is good enough to ship and make money (or deploy internally and save costs for the company).

I’ve used this approach in some of my strategy engagements as well. It’s a good compromise between time-and-materials and fixed-price models. The client can very quickly receive value (and see the cost vs. value model emerge quickly from the results of each sprint/release); the consulting firm has some predictability in its revenues.

Hope this helps!

By: Herve Lourdin

Herve Lourdin — Mon, 14 Sep 2009 20:31:17 +0000

Nice pictures !!

To be perfect, it would be nice to show the pipeline kickoff of the lean approach. As is, we could have the feeling that each column is related to the same item (which is not as far as I know)

Herve

By: AgileLearner

AgileLearner — Mon, 14 Sep 2009 19:07:39 +0000

The Lean diagram shows many deployments. It seems to suggest that production deployments are increased whereas the features introduced are decreased. How do you deal with the inherent difficulties of taking down a system for so many production deployments?

By: Hannu Kokko

Hannu Kokko — Thu, 10 Sep 2009 10:25:12 +0000

I like the picture. I would put in both Scrum and Lean the build and test boxes together meshed so that they are really intertwined right from the start. This picture makes it look like they would be sequential.

By: Agile vs Waterfall vs Iterative vs Lean Software Development - In Pictures! | Scrum Head

Thu, 10 Sep 2009 09:27:56 +0000

[...] Take a closer look at it and read the explanation over on her blog, agile101.net… [...]

By: aaron

aaron — Wed, 09 Sep 2009 19:42:50 +0000

I like the pictures put together by Karl Scotland, which illustrate the points a little differently.
http://availagility.wordpress.com/2008/07/07/the-anatomy-of-an-mmf/
http://availagility.wordpress.com/2008/11/26/kanban-and-the-new-new-product-development-game/

By: Elsewhere, on September 9th - Once a nomad, always a nomad

Elsewhere, on September 9th - Once a nomad, always a nomad — Wed, 09 Sep 2009 18:26:45 +0000

[...] Shared The Difference Between Waterfall, Iterative Waterfall, Scrum and Lean (In Pictures!) | Project Manag…. [...]

By: Hector Hurtado

Hector Hurtado — Wed, 09 Sep 2009 08:54:16 +0000

Thank you for your post, as it is a good starting point to explain to clients the differences between these methodologies. I really like the textual explanations, the images don’t enhance your content any better, in my opinion.

@Paul Jackson: the conundrum is “without a fixed price and up front requirements analysis”. I strive towards agile methodologies, while still giving a fixed price. Granted, much more difficult to aim it right, and sometimes you win sometimes you lose, but you still give the client the confidence of the known bill. What are your thoughts on this?

By: Fabrice Aimetti

Fabrice Aimetti — Wed, 09 Sep 2009 06:05:19 +0000

Hi Tara, I've translated in French your excellent post : La différence entre les modèles de développement en Cascade, en Cascade itératif, Scrum et Lean (en images !) Regards, Fabrice

By: blerp

blerp — Wed, 09 Sep 2009 03:30:33 +0000

I think your diagrams are inconsistent. One axis is time, the other is ‘features’.

Iterative Waterfall makes it look like time is horizontal, but that’s not consistent with SCRUM or LEAN.

And, your description doesn’t make SCRUM and LEAN sound that revolutionary, they come out as just mini- and micro- Waterfalls.

By: Paul Jackson

Paul Jackson — Tue, 08 Sep 2009 17:41:23 +0000

I was asked about this by a client today so great timing!

The usual sticky point remains of how we convince a sceptical client that Agile development can provide enormous benefits without a fixed price and up front requirements analysis – the battle continues!