Newsgroups: comp.lang.smalltalk,comp.lang.c++,comp.object
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.kei.com!newsfeed.internetmci.com!in2.uu.net!usc!math.ohio-state.edu!news.cyberstore.ca!skypoint.com!umn.edu!dialup-12-b-23
From: jhgreve@epx.cis.umn.edu (John Greve)
Subject: Re: SCRUM and Why the Waterfall Methodology is a Fool's Errand ...
Message-ID: <DJ3p0E.wK@news.cis.umn.edu>
Sender: news@news.cis.umn.edu (Usenet News Administration)
Nntp-Posting-Host: dialup-12-b-23.gw.umn.edu
Organization: University of Minnesota, Twin Cities
References: <30AF370B.1AE@vmark.com> <49ffbj$oon@dns1.mci.com> <49fk7a$jc@brtph500.bnr.ca>
	<49tb0a$4kt@news4.digex.net> <RMARTIN.95Dec4085604@rcm.oma.com>
Date: Tue, 5 Dec 1995 05:38:40 GMT
Lines: 20
Xref: glinda.oz.cs.cmu.edu comp.lang.smalltalk:31557 comp.lang.c++:163413 comp.object:42057

In article <RMARTIN.95Dec4085604@rcm.oma.com>,
   rmartin@oma.com (Robert C. Martin) wrote:
>In article <49tb0a$4kt@news4.digex.net> ell@access1.digex.net (Ell) writes:
>
>   : The reason requirements are unstable is that they are tied to
>   : money. And when the motivations of the industry change, the
>   : requirements have to change too, and quickly.  It does not matter how
>   : hard the software is to change, the price will either be paid, or the
>   : project will fail.  Thus there is a huge impetus behind the changing
>   : requirements, one that cannot be withstood.
>
>   But it must eventually be withstood, money behind it, or not.  That is if 
>   we want to serve user needs.
>
>Huh?  It is the user that is demanding the changes.  How can you serve
>the user if you "withstand" his demands?
It works for Microsoft.  :-)

John Greve
jhgreve@epx.cis.umn.edu
