This post originated from an RSS feed registered with Java Buzz by Michael Cote. Original Post: XP, Pair Programming Negative Chatter Feed Title: Cote's Weblog: Coding, Austin, etc. Feed URL: https://cote.io/feed/ Feed Description: Using Java to get to the ideal state. Latest Java Buzz Posts Latest Java Buzz Posts by Michael Cote Latest Posts From Cote's Weblog: Coding, Austin, etc.

Check out this entry and comment from "Mr Ed." It's a well done anti-XP discussion.

In another (this time, pro) XP/Agile post, there's a good quote on the need for business to re-jiggering how success is determined when Agile methods are adopted,

Agile approaches excel in volatile environments in which conformance to plans made months in advance is a poor measure of success. If agility is important, then one of the characteristics we should be measuring is that agility. Traditional measures of success emphasize conformance to predictions (plans). Agility emphasizes responsiveness to change. So there is a conflict because managers and executives say that they want flexibility, but then they still measure success based on conformance to plans. Wider adoption of Agile approaches will be deterred if we try to "prove" Agile approaches are better using "only" traditional measures of success.