Buy new:
-27% $32.92$32.92
FREE delivery December 9 - 11
Ships from: Pharos Bookstore Sold by: Pharos Bookstore
Save with Used - Very Good
$9.97$9.97
FREE delivery December 4 - 9
Ships from: ThriftBooks-Phoenix Sold by: ThriftBooks-Phoenix
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Extreme Programming Refactored: The Case Against XP Softcover reprint of the original 1st ed. Edition
Purchase options and add-ons
Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly-hyped extreme programming (XP) 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.
- ISBN-101590590961
- ISBN-13978-1590590966
- EditionSoftcover reprint of the original 1st ed.
- PublisherApress
- Publication dateAugust 5, 2003
- LanguageEnglish
- Dimensions7.5 x 0.98 x 9.1 inches
- Print length460 pages
Editorial Reviews
About the Author
Product details
- Publisher : Apress; Softcover reprint of the original 1st ed. edition (August 5, 2003)
- Language : English
- Paperback : 460 pages
- ISBN-10 : 1590590961
- ISBN-13 : 978-1590590966
- Item Weight : 1.55 pounds
- Dimensions : 7.5 x 0.98 x 9.1 inches
- Best Sellers Rank: #4,380,824 in Books (See Top 100 in Books)
- #95 in Ada Programming Language
- #609 in Compiler Design
- #653 in Software Programming Compilers
- Customer Reviews:
About the author

Matt Stephens is a software consultant with a financial organization based in Central London. He's been developing software commercially for nearly 30 years, and has led many agile projects through successive customer releases. He has spoken at a number of software conferences on OO development topics, and his writing appears regularly in a variety of journals and websites, including The Register and ObjectiveView.
Catch Matt online at:
https://medium.com/@SoftwareReality
And at the Domain Oriented Testing group on LinkedIn:
https://www.linkedin.com/groups/13804489/
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Consider the source of so much of their information, the C2wiki. This is a discussion group! People who have no knowledge of Extreme Programming make outrageous statements and they are quoted in this book. Furthermore that discussion group's format is such that any comment can be changed by anyone. I noticed a mistake while reading this book so I went over to the source at C2.com and changed it! That is how fragile the so called facts are that this book is based on.
Much of this book is based on projects that neither Matt nor Doug actually participated in. It isn't hard to imagine that they get the facts wrong.
One would expect from the name of this book that Matt and Doug will tell us ways to change XP to meet problems that are faced on projects. There is only a very thin section of a couple pages that deals with this. Almost the entire book is devoted to showing that XP should not work.
Then Matt describes a project he runs using XP and guess what? It works! He uses the core of XP with a couple peripheral changes. He changes the twice per day integration to once per day. He scales back on pair programming. He uses use cases instead of user stories. He spends extra time creating design documents. The core of XP is still intact and it works.
How to refactor XP should have been the focus of this book. What ideas can you take from XP that will help your project now? What can you change from standard XP and still survive? Do you need a book that is 50% song lyrics, 45% misquotes, and only 5% useful information?
One thing that is continually reinforced by the example projects in this book is that XP is very different from traditional processes and you must understand the differences to do well with XP. You can not learn anything about XP from this book because it promotes and glorifies a misunderstanding of what makes XP work. There are now two ways to develop software and a good understanding of both and when to use one or the other is vital information. You won't get that from this book because the authors chose a format that isn't informative.
If you want some good satire you should read Mr. Bunny's Big Cup O' Java. If you want to learn something about Extreme Programming get a different book.
It's easy by the way: just lie and tell everyone what they want to hear. People want to believe you have a magic solution to their problems so they won't examine your trite, off-the-cuff replies claiming to answer their questions.
Amusingly, a couple of years after this book became popular, I noticed that it's web site had been merged with the main XP promoting website. Apparently, the author of the book was willing to sell out for a buck. By having his website included with the main site, he could get more traffic and make more book sales.
The main XP site now has a long section that claims to address the issues that this book brings up. You'll have to read it for yourself and see if they have really been able to answer the author's original claims.
If you care about the software development process, buy this book. Understand it's arguments, then check out the main XP website.
Top reviews from other countries
I find it useful to apply a dogma, like XP, to extremes of project, to see how they fare. Take a payroll app (an example of XP success, or failure, depending upon who you believe) and a chess-playing program. I have some problems applying XP to the latter, whilst the former is likely to be more successful. If my example makes sense,then XP is just one a sensible set of choices for your project, depending on risk, staff, constraints and all the other things that mature PMs take into account. Tub thumping, folksy style makes for an easy read, but does not lend itself to serious analysis.
In the end, with the songs, the excessive quotes and the style of the book I found it very tedious. The McConnell approach to these subjects is preferred (at least by me)
