Extreme Programming Refactored
The Case Against XP
Résumé
"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
“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.
Contents
- Part I Another Fine Mess You've Gotten Me Into (Laurel
and Hardy Take Up Programming)
- XP in a Nuthouse (Oops, We Mean Nutshell)
- Where Did XP Come From? (Chrysler Knows
- It Ain't Easy . . .)
- The Case Against XP
- Part II Social Aspects of XP (Mama Don't Let Your
Coders Grow Up to Be Cowboys)
- Extremo Culture
- The On-site Customer
- Pair Programming (Dear Uncle Joe, My Pair Programmer Has Halitosis)
- Oral Documentation (Oxymoronic, or Just Plain Moronic?)
- Part III We Don't Write Permanent Specs and Barely Do
Any Upfront Design, So
- Design After First Testing
- Constant Refactoring After Programming (If It Ain't Broke, Fix It Anyway)
- : User Stories and Acceptance Tests
- Part IV The Perpetual Coding Machine
- Software Is Never Done (The Schedule Does Not Exist Per Se)
- Emergent Architecture and Design
- Embracing Change (Embrace People, Manage Change)
- Part V The Big Picture
- Scalability
- Refactoring XP
- Conclusion: Neutralizing the Reality Distortion Field
L'auteur - Doug Rosenberg
Doug Rosenberg, of ICONIX Software Engineering, Inc., has been providing system development tools and training for nearly two decades, with particular emphasis on object-oriented methods. He developed a Unified Booch/Rumbaugh/Jacobson design method in 1993 that preceded Rational's UML by several years. He has produced over a dozen multimedia training courses on object technology, including COMPREHENSIVE COM and COMPLETE CORBA, and is the author of several Addison-Wesley titles.
Caractéristiques techniques
| PAPIER | |
| Éditeur(s) | Apress |
| Auteur(s) | Matt Stephens, Doug Rosenberg |
| Parution | 16/09/2003 |
| Nb. de pages | 400 |
| Format | 17,5 x 23,5 |
| Couverture | Broché |
| Poids | 690g |
| Intérieur | Noir et Blanc |
| EAN13 | 9781590590966 |
| ISBN13 | 978-1-59059-096-6 |
Avantages Eyrolles.com
Consultez aussi
- Les meilleures ventes en Graphisme & Photo
- Les meilleures ventes en Informatique
- Les meilleures ventes en Construction
- Les meilleures ventes en Entreprise & Droit
- Les meilleures ventes en Sciences
- Les meilleures ventes en Littérature
- Les meilleures ventes en Arts & Loisirs
- Les meilleures ventes en Vie pratique
- Les meilleures ventes en Voyage et Tourisme
- Les meilleures ventes en BD et Jeunesse
