Bob, Who would be the one/two critics of the Agile Movement that would make you sit up and take notice of their criticisms ? I notice as time passes the numbers seem to be getting fewer and the term , Agile or Extreme, at least (if not the entire methodology), seems to be adopted now. (Sorry if this question doesn't relate to the book reviewed.) regards
The question does even less relate to this forum... Moving to the Process forum. Bob, you are of course invited to answer posts in that (and the other forums), too!
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
"Any one [XP] practice doesn�t stand well on its own (with the possible exception of testing). They require the other practices to keep them in balance.� � Kent Beck, Extreme Programming Explained, (Chapter 11) �Well, from my experience, most teams that say they're doing XP don't actually do the practices.� � Alistair Cockburn, http://c2.com/cgi/wiki?XpAndTheCmm �Houston, we have a problem.� � Jim Lovell, Apollo 13 Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly hyped Extreme Programming methodology. It explores some quite astonishing Extremo quotes that have typified the XP approach � quotes such as, �XPers are not afraid of oral documentation,� �Schedule is the customer�s problem,� �Dependencies between requirements are more a matter of fear than reality� and �Concentration is the Enemy.� In between the chuckles, though, there is a serious analysis of XP�s many flaws. The authors also examine C3, the first XP project, whose team (most of whom went on to get XP book deals shortly before C3�s cancellation) described themselves as �the best team on the face of the Earth�. (In a later chapter, the authors also note that one problem which can affect pair programmers is overconfidence � or is that �eXcessive courage�?). The authors examine whether the problems that led to C3�s �inexplicable� cancellation could also afflict present-day XP projects. In the final chapter (Refactoring XP) Matt and Doug suggest some ways of achieving the agile goals of XP using some XP practices (used in moderation) combined with other, less risk-laden methods.
Originally posted by HS Thomas: Bob, Who would be the one/two critics of the Agile Movement that would make you sit up and take notice of their criticisms ? I notice as time passes the numbers seem to be getting fewer and the term , Agile or Extreme, at least (if not the entire methodology), seems to be adopted now. (Sorry if this question doesn't relate to the book reviewed.) regards
Pete McBreen is a pretty sincere and honest critic. As for the "XP Refactored" book -- well -- Whatever.
---<br />Uncle Bob.
Joined: Jul 02, 2003
Originally posted by Thomas Paul: Whenever I see anyone respond to criticism of x with "you just don't understand x," I have to laugh. Maybe they understand it too well!!!
However, in this particular case, the authors do not understand it at all. IMHO.
Joined: Jul 02, 2003
Originally posted by HS Thomas: It's a pity Bob Martin missed this post. He must have come up against quite a few critics. Converted some too ? regards
More than a few. I don't mind honest criticism. There is no perfect process. I manage to convince some people that XP can help them, and some people manage to convince me that they don't need it. That's fine. What galls me is criticism from ignorance. There's just way too much of that.