begin quoting Tracy R Reed as of Fri, Dec 08, 2006 at 01:23:15AM -0800:
> Also known as "XP". Is it yet another programming fad? I think probably
> so. No silver bullets etc.
The way a lot of people seem to implement it, yah, it's a fad. But
most of 'em miss the point of XP as well ('cuz to do it all, right,
is still hard), so if you'd do it right, then yes, it's something
different.
But it's not a silver bullet. It's merely an approach.
The gain is that you have a team that can better handle ill-defined
requirements (i.e., the customer doesn't quite know exactly what they
want), and can determine, early on, if what the customer thinks they
need isn't really what is needed.
This stands in stark relief to "standard" process-oriented development,
which depends a lot more on up-front analysis. (And requires some
serious discipline to avoid falling into the waterfall model of
development.)
Nothing in XP is actualy new -- what's new and interesting about XP is
how each technique complements other techniques.
[chop]
--
_ |\_
\|
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
