From: Christopher Smith <[EMAIL PROTECTED]>
Ironically, I also suspect this was one of the reasons why Beck pushed for
"Extreme" adoption of best practices. By taking out notions of compromise,
middle ground, etc., you leave little cover for slacking off or breaking
discipline
The exact opposite- by pushing everything to the extreme you garuntee that
people will break discipline, because people won't put up with it.
(keep in mind that the project had been a walking disaster for over a year,
so bad habits were deeply ingrained). Not necessarily the best way to solve
it, but undoubtedly effective.
Seeing as the project never made it to completion, there's a hell of a lot
of room to doubt their effectiveness. XP was a failure there as well. Some
of the ideas of agile work well, but the XP "goes to 11" philosophy without
exception bends them so far that they're counterproductive. Throwing out
design entirely doesn't work. Getting rid of all foresight and coding only
whats needed in the next week doesn't work. Forcing everything to be broken
into 1 week blocks rarely works. Pair programming not only doesn't find
more bugs, but it drives the programmers insane. Some of the ideas these
are based on (unit tests, avoiding the waterfall, demoing, and code reiews)
work well, but not in the insane form XP uses them.
Especially pair programming. I'm personally willing to give an awful lot at
least a try, but if you tell me I'm going to have someone standing over my
shoulder all day, I'm quitting on the spot, no 2 week notice.
Gabe
_________________________________________________________________
Get the latest Windows Live Messenger 8.1 Beta version. Join now.
http://ideas.live.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
