Cart
[Home] [By Thread] [By Date] [Recent Entries]
Marcus Carr writes:
> > In fact (in particular from the Extreme Programming point of
> > view), you should arguably *always* use it as a model for
> > software development.
>
> Yes, but they would all involve having fairly concrete vision of
> the endgame requirements during development.
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.
All the best,
David
--
David Megginson david@m...
http://www.megginson.com/
|
