Home > Store

Extreme Programming Perspectives

Register your product to gain access to bonus material or receive a coupon.

Extreme Programming Perspectives


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2003
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-77005-9
  • ISBN-13: 978-0-201-77005-6

Extreme Programming (XP) has been established as a significant departure from traditional software development methods. The success of the XP 2001 and XP Universe 2001 conferences is no surprise; some of the brightest minds in software engineering gathered at these venues to discuss the discipline that is XP. These conferences showcase the continuously changing face of XP. Common programming practices will never be the same, and developers and business people alike need to bear this fact in mind as they plan for the future.

Inspired by the techniques and challenges explored at these conferences, Extreme Programming Perspectives presents 47 articles that represent the insights and practical wisdom of the leaders of the XP community. Encompassing a wide variety of key topics on XP and other agile methodologies, this book offers experience-based techniques for implementing XP effectively and provides successful transitioning strategies. Articles are grouped into six main sections: an overview of XP and agile methodologies; XP development practices; issues involved in transitioning to XP and agile methodologies; real-life experiences of working with XP; tools for facilitating XP development; and finally, ideas for expanding and extending XP.

You will find such outstanding articles as:

  • Circle of Life, Spiral of Death: Ways to Keep Your XP Project Alive and Ways to Kill It, by Ron Jeffries
  • Agile Software Development—Why It Is Hot!, by Jim Highsmith
  • An Introduction to Testing, XP-Style, by Don Wells
  • Increasing the Effectiveness of Automated Testing, by Shaun Smith and Gerard Meszaros
  • The System Metaphor Explored, by William Wake and Steven Wake
  • Pair Programming: Why Have Two Do the Work of One?, by Laurie Williams
  • A Metric Suite for Evaluating the Effectiveness of an Agile Methodology, by Laurie Williams, Giancarlo Succi, and Michele Marchesi
  • The Five Reasons XP Can’t Scale and What to Do about Them, by Ron Crocker
  • Keep Your Options Open: Extreme Programming and the Economics of Flexibility, by Hakan Erdogmus and John Favaro
  • Extreme Programming from a CMM Perspective, by Mark C. Paulk

    The contributions in this book comprise the best practices in Extreme Programming across a number of industries. Those already involved in XP development, or anyone interested in transitioning to this flexible approach, will find this book a fascinating and valuable resource for leveraging the power of XP and agile methodologies.


  • Sample Content

    Online Sample Chapter

    Which Agile Methodology Should You Use?

    Table of Contents


     1. XP in Thousand words-Don Wells.
     2. Agile Software Development-Why It Is Hot!-Jim Highsmith.
     3. Which AM Should I Use?-Michele Marchesi.
     4. Pair Programming: Why Have Two Do The Work of One?-Laurie Williams.
     5. The System Metaphor Explored-William C. Wake, Steven A. Wake.
     6. A Lightweight Evaluation of a Lightweight Process- Giancarlo Succi.
     7. Circle of Life, Spiral of Death: Ways to Keep Your XP Project Alive and Ways to Kill It.-Ron Jeffries.
     8. Hitting the Target with XP-Michele Marchesi.


     9. An Introduction to Testing, XP Style-Don Wells.
    10. Is Quality Negotiable?-Lisa Crispin.
    11. A Collaborative Model for Developers and Testers Using the Extreme Programming Methodology-Michael Silverstein and Mark Foulkrod.
    12. Increasing the Effectiveness of Automated Testing-Shaun Smith and Gerard Meszaros.
    13. Extreme Unit Testing: Ordering Test Cases to Maximize Early Testing- Allen Parrish, Joel Jones, and Brandon Dixon .
    14. Refactoring Test Code- Arie van Deursen, Leon Moonen, Alex van den Bergh, and Gerard Kok.
    15. Diagnosing Evolution in Test-Infected Code- Christian Wege and Martin Lippert.
    16. Innovation and Sustainability with Gold Cards- Julian Higman, Tim Mackinnon, Ivan Moore, and Duncan Pierce.
    17. Integrating Extreme Programming and Contracts- Hasko Heinecke and Christian Noack.
    18. Refactoring or Up-Front Design?- Pascal Van Cauwenberghe.
    19. A Methodology for Incremental Changes- Václav Rajlich.
    20. Extreme Maintenance- Charles Poole and Jan Willem Huisman.


    21. Bringing Extreme Programming to the Classroom- Owen L. Astrachan, Robert C. Duvall, and Eugene Wallingford.
    22. Teaching XP for Real: Some Initial Observations and Plans- Mike Holcombe, Marian Gheorghe, and Francisco Macias.
    23. Student Perceptions of the Suitability of Extreme and Pair Programming- Dean Sanders.
    24. Extreme Programming and the Software Design Course-David H. Johnson, and James Caristi.
    25. The User Stories and Planning Game Tutorial-Ann Anderson, Chet Hendrickson, Ron Jeffries.
    26. Continuous Learning-Joshua Kerievsky
    27. The XP Game Explained-Vera Peeters and Pascal Van Cauwenberghe.
    28. Mob Programming and the Transition to XP-Moses M. Hohman, Andrew C. Slocum.
    29. A Metric Suite for Evaluating the Effectiveness of an Agile Methodology -Laurie Williams, Giancarlo Succi, Milorad Stefanovic, and Michele Marchesi.


    30. Extreme Adoption Experiences of a B2B Start Up-Paul Hodgetts and Denise Phillips.
    31. Lessons Learned from an XP Project- Natraj Kini and Steve Collins.
    32. Challenges for Analysts on a Large XP Project- Gregory Schalliol.
    33. XP On A Large Project-A Developer's View. Amr Elssamadisy.
    34. A Customer Experience: Implementing XP- Ann Griffin.
    35. Learning by Doing: Why XP Doesn't Sell Kay Johansen, Ron Stauffer, and Dan Turner.
    36. Qualitative Studies of XP in a Medium-Sized Business- Robert Gittins, Sian Hope, and Ifor Williams.


    37. Automatically Generating Mock Objects-Asim Jalis and Lance Kind.
    38. Testing in the Fast Lane: Automating Acceptance Testing in an Extreme Programming Environment- Tip House and Lisa Crispin.
    39. Jester-a JUnit Test Tester-Ivan Moore.
    40. Stabilizing the XP Process Using Specialized Tools-Martin Lippert, Stefan Roock, Robert Tunkel, Henning Wolf.
    41. Holmes—A Heavyweight Support for a Lightweight Process-Giancarlo Succi, Witold Pedrycz, Petr Musilek, and Iliyan Kaytazov.


    42. Extreme Programming from a CMM Perspective- Mark C. Paulk.
    43. Keep Your Options Open: Extreme Programming and Economics of Flexibility-Hakan Erdogmus and John Favaro.
    44. Distributed Extreme Programming-Michael Kircher, Prashant Jain, Angelo Corsaro, David Levine.
    45. The Five Reasons XP Can't Scale and What to Do about Them-Ron Crocker.
    46. XP in Complex Project Settings: Some Extensions-Martin Lippert, Stefan Roock, Henning Wolf, Heinz Züllighoven.
    47. Building Complex Object-Oriented Systems with Patterns and XP-Eduardo B. Fernandez.
    Index. 0201770059T08092002


    Welcome to yet another book on Extreme Programming—and Agile Methodologies, of course!

    Writing a book about new software development methodologies can be a very easy and a very difficult task together.

    It could be very easy, as you could talk about very generic and high-level vaporware without ever entering details, and backing your approach with statements such as “it requires customization,” “no silver bullets,” and other politically correct statements.

    You could take the completely opposite approach, and still have a fairly easy task if you have ever run a project with your methodology. You could enter a detailed description of what you did, distilling a complete approach around your individual idiosyncrasies. Best would be if you add something esoteric, such as typing into the keyboard with only the right hand, and using the left to hold a silk napkin with whom you would clean your sweater every other minute.

    This is not because software authors are bad by nature. We should remember that in the early days of the studies in electronics, the equation for the resistor was awfully complex, with lots of terms which were really insignificant. Nowadays, it is a simple algebraic division: R=V/I.

    However, writing about a new methodology becomes dreadfully difficult if you aim at creating something really valuable for the reader, combining the limited theoretical understanding with the limited experimental evidence, and avoiding a terse language.

    This book takes this latter approach. We combine an overview of XP, from the hand of the people who proposed it, description of experiences in specific areas yet unclear and subject to debate, and an empirical evaluation of how XP projects are progressing in software companies.

    The first section is the overview of the methodology. We assume that you have already read the cult books, Kent’s, Martin’s, Ron’s, Jim’s, etc. So we summarize all the foundations in one chapter, by Don.

    In Chapter 2, Jim Highsmith presents the essence of “Agility.” This insightful chapter goes in the depth of Agile Methodologies and explains the rationale behind any agile proposal.

    The large number of Agile Methodologies may disorient software managers and engineers. To this end, Michele provides guidelines to select which among the several Agile Methodologies best suits your environment (Chapter 3).

    Most likely people thinking at XP, associate it to Pair Programming. Detractors say that it is only a fad, which wastes time and money of software companies. Supporters are convinced that it is the philosopher store of software development. In Chapter 4, Laurie discusses the principles of Pair Programming, details when and how to adopt it, and summarizes the expected benefits.

    An effective analysis in XP is centered in the ability to find a suitable metaphor. This is not an easy task, especially when the project gets larger and more complex. In Chapter 5, William and Steven Wake focus on the issue of metaphor. In particular, they detail their approach in finding a metaphor, in relating the objects of the system to it, and in evaluating whether there are “bad metaphors.”

    XP is not cowboy coding, neither completely uncontrolled development. It is the opposite of them. But how is it possible to couple an agile approach with measurements and process control? They look like an antinomy. In Chapter 6, Giancarlo discussed possible avenues to implement an agile measurement program, taking advantage of sources of data naturally available to software engineers and managers.

    What is the extent to which each individual practice of XP is useful? How much of them should we keep in our project for our project to be successful? What is the level of customization of the practices that we can safely have? In Chapter 7, Ron attempts to address these tricky issues that managers pose every day. He analyses the most relevant practices and concludes with a caveat toward to “agile” customizations.

    Last but not the least, Michele explains how it is possible to hit your targets using XP. He explains how to align business and technical goals, and outlines possible problems that you may face when implementing an XP project and how to solve them.



    Untitled Document



    Click below to download the Index file related to this title:


    Submit Errata

    More Information

    Unlimited one-month access with your purchase
    Free Safari Membership