Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.kei.com!newsfeed.internetmci.com!vixen.cso.uiuc.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!rfenney.slip.netcom.com!user
From: rfenney@directnet.com (Robert J. Fenney)
Subject: Re: SCRUM and Why the Waterfall Methodology is a Fool's Errand ...
Message-ID: <rfenney-281195180038@rfenney.slip.netcom.com>
Followup-To: comp.lang.smalltalk,comp.lang.c++,comp.object,comp.client-server
Sender: netnews@mork.netcom.com
Nntp-Posting-Host: rfenney.slip.netcom.com
Organization: FenTek
References: <30AF370B.1AE@vmark.com> <jzqcvc@bmtech.demon.co.uk> <48spd4$s30@ixnews4.ix.netcom.com> <30B34179.66AF@oma.com> <49ffbj$oon@dns1.mci.com>
Date: Wed, 29 Nov 1995 02:04:23 GMT
Lines: 16

In article <49ffbj$oon@dns1.mci.com>, tuttor@velveeta.enet.dec.com ()
wrote:

The reason that iterative approaches work in the real world and waterfall
doesn't is that you never understand the problem domain upfrunt and I will
guaranty that the domain will change as you implement as apposed to design.
I have never seen a user base that does not refine their view of the world
as they see what can be done. The problem that most users find is that they
have to scale back their expectations because they know they will be lucky
to get anything let-alone something new and wonderfull. The challenge of
iterative development strategies is to now when to cut off the current
iteration and deliver something and  when to keep iterating.  BTW this
whole discussion has very little to do with OOP/OOA as it does with just
plain design in general.

Robert
