- Series: Expert's Voice
- Paperback: 432 pages
- Publisher: Apress; Softcover reprint of the original 1st ed. edition (August 5, 2003)
- Language: English
- ISBN-10: 1590590961
- ISBN-13: 978-1590590966
- Product Dimensions: 7.5 x 1 x 9.1 inches
- Shipping Weight: 1.8 pounds (View shipping rates and policies)
- Average Customer Review: 34 customer reviews
- Amazon Best Sellers Rank: #2,645,635 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Extreme Programming Refactored: The Case Against XP Softcover reprint of the original 1st ed. Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
See the Best Books of 2018 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
There is no useful information in this book, just some fun poking at misleading interpretations of extreme programming.
If you are an ego filled, spaghetti coder, searching for an excuse to poke fun of the daring new generation of cooperative programmers stealing your job. This is your book.
Having practiced XP, I particularly like two chapters in this book, one on XP in a nuthouse which is a good read for someone who is new to XP to get a quick understanding of the XP concept and the next one is the chapter on XP refactored in which the authors point out good features of XP along with their own best practices added and ideas that may make XP better.
This book is an extreme view of Extreme programming. The authors have criticized almost every aspect of Extreme programming. Any developer thinking of following the methodology would be discouraged to do so if they came across this book first.
They take a very rigid stand on refactoring, picturing as if XP programmers are in a constant refactoring frenzy for no good reason. Lack of initial design has been pointed out as being responsible for lot of rework. Release early, release often concept has been shown to increase the developer's concern of whether it will integrate into the system and satisfy all the tests or not.
They point out that XP is not scalable and is only suitable for small projects. Though most of the XP projects are small, I know the above statement is not entirely true as I heard a success story of a big project which was migrating and had a strict production deadline to meet which it did.
The authors picked examples from instances where the coders did not take care of situations. For example, they comment on unit tests saying that unit tests are stand alone in XP and often left databases dirty. The developer in that instance may not have had roll back statements in the test which is why the database was left dirty and hence it is not a flaw with XP methodology but a flaw with the way it was implemented.
By the end of the book, the authors refactor XP and delineate the pros and cons of each XP component in which they mention the following points:
* Pair programming should not be constant or mandatory
* Programmers should design
* Programmers should write their own tests
* Instead of continuous design, we should follow frequent design
* 40 hr weeks are not feasible as sometimes developers have to work overtime to meet deadlines
* Coding, testing, listening and designing of XP are worth salvaging
* Iterations should be one month long
* Test first design should complement the design but should not drive it
* Use a combination of requirements and use cases instead of user stories
* Project velocity should be measured in terms of formal requirements completed per iteration rather than user stories per iteration
Overall, I thought it was a fairly good though quick read for me
Most recent customer reviews
Hoped to find something valuable here, but got very surprised instead...Read more
Does it contain sad attempts at comedy: yes
Does it have valid points to make: yes...Read more