[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: XP and fruit-picking (was Re: is that a fork in the road?)
- From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
- To: David Megginson <email@example.com>, firstname.lastname@example.org
- Date: Tue, 06 Mar 2001 09:02:09 -0600
That depends on a very smart endgame focused customer
and a contract that does not include maintenance or
enhancements. Good for some kinds of service-based
work but will not scale to large sales of standardized
or functionally stable software.
You guys learned absolutely nothing from the
Netscape debacle. Microsoft didn't have to
beat them; they only had to wait for the fruit
to rot on the vine and fall off.
Think Ford, not Ferrari.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: David Megginson [mailto:email@example.com]
On the contrary, the XP people grasp at the low-hanging fruit
precisely because they do not trust their knowledge of the endgame
requirements. They know that the requirements *will* change during
development, drastically and continuously, so they implement the bare
minimum necessary to meet their short-term goals (i.e. two- to
three-weeks) and give the customer a chance to have some hands-on
experience and (possibly) rewrite the requirements after each
iteration. Wild stuff.