This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: XP Refactored? Again?
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Cook Computing makes some good points about XP pitfalls, but makes the mistake of recommending this book. I've posted on this crap before - Rosenberg and Stephens know how to attack a strawman, but wouldn't know XP if it bit them in the posterior lobes. However, Cook makes some useful points on the subject:
I heard of one group who, when asked for the design documentation of their current project, replied "We don't have any documentation, we do XP". Needless to say they weren't really following any XP practices.
I suspect you need high-calibre motivated and disciplined developers to get XP to work and that development groups who struggle with more traditional development processes will struggle even more with XP. So examine why the current development process doesn't work well before jumping to XP. The same problems may well make XP even less effective.
Like any other popular tool or methodology, the number of camp followers who claim to be doing it will be much higher than the number of people actually doing it.
Previous Topic
