Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!newsfeed.cit.cornell.edu!news.tc.cornell.edu!newsserver.sdsc.edu!news.cerf.net!usc!howland.reston.ans.net!ix.netcom.com!netcom.com!jnedzel
From: jnedzel@netcom.com (Jared Nedzel)
Subject: Re: SCRUM and Why the Waterfall Methodology is a Fool's Errand ...
Message-ID: <jnedzelDIEqwr.Kpr@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <30AF370B.1AE@vmark.com> <jzqcvc@bmtech.demon.co.uk> <48spd4$s30@ixnews4.ix.netcom.com>
Date: Tue, 21 Nov 1995 19:17:15 GMT
Lines: 33
Sender: jnedzel@netcom14.netcom.com

In article <48spd4$s30@ixnews4.ix.netcom.com> kentb@ix.netcom.com 
(Kent Beck ) writes:

>In <jzqcvc@bmtech.demon.co.uk> Scott Wheeler
><scottw@bmtech.demon.co.uk> writes: 
>>
>>In Article <30AF370B.1AE@vmark.com> Jeff Sutherland  writes:
>>>... the Waterfall Methodology is fatally
>>>flawed and doomed to failure....
>>
>>Is this news? I was under the impression that this had been generally 
>>accepted for at least 20 years.

>Then why do some of my clients (at least initially) think that
>"iterative development" means "an iteration for analysis, an iteration
>for design, ..."? Most development organizations still prefer a
>pile-of-paper-based illusion of control to active management of
>development risk.

My clients do the same.  They all talk about iterative development, but
then they create project plans with x weeks for analysis, y weeks for 
design, z weeks for development, and 1 week for testing.  Sure looks
like waterfall to me, warts and all.





-- 
-------------------------------------------------------------------------
Jared Nedzel  					jnedzel@netcom.com

Just because I'm paranoid doesn't mean there isn't someone out to get me
-------------------------------------------------------------------------
