Skip to main content
Apress

Extreme Programming Refactored

The Case Against XP

  • Book
  • © 2003

Overview

  • Cuts through the hype and tells "the other side of the story" about Extreme Programming

  • Provides a thorough and systematic analysis of XP practices and separates the "agile" from the "fragile"

  • Distinguishes useful XP techniques (e.g. use of automated unit testing tools) from questionable ones (e.g. oral documentation)

This is a preview of subscription content, log in via an institution to check access.

Access this book

eBook USD 34.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 44.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (16 chapters)

  1. Another Fine Mess You’ve Gotten Me Into (Laurel and Hardy, Take Up Programming)

  2. Social Aspects of XP (Mama Don’t Let Your Coders Grow Up to Be Cowboys)

  3. We Don’t Write Permanent Specs and Barely Do Any Upfront Design, So.

  4. The Perpetual Coding Machine

  5. The Big Picture

Keywords

About this book

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.

About the authors

A bio is not available for this author.

Bibliographic Information

Publish with us