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

    InformIT Promotional Mailings & Special Offers

    I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


    Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

    This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

    Collection and Use of Information

    To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

    Questions and Inquiries

    For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

    Online Store

    For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


    Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

    Contests and Drawings

    Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


    If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

    Service Announcements

    On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

    Customer Service

    We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

    Other Collection and Use of Information

    Application and System Logs

    Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

    Web Analytics

    Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

    Cookies and Related Technologies

    This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

    Do Not Track

    This site currently does not respond to Do Not Track signals.


    Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


    This site is not directed to children under the age of 13.


    Pearson may send or direct marketing communications to users, provided that

    • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
    • Such marketing is consistent with applicable law and Pearson's legal obligations.
    • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
    • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

    Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

    Correcting/Updating Personal Information

    If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


    Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

    Sale of Personal Information

    Pearson does not rent or sell personal information in exchange for any payment of money.

    While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

    Supplemental Privacy Statement for California Residents

    California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

    Sharing and Disclosure

    Pearson may disclose personal information, as follows:

    • As required by law.
    • With the consent of the individual (or their parent, if the individual is a minor)
    • In response to a subpoena, court order or legal process, to the extent permitted or required by law
    • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
    • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
    • To investigate or address actual or suspected fraud or other illegal activities
    • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
    • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
    • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


    This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

    Requests and Contact

    Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

    Changes to this Privacy Notice

    We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

    Last Update: November 17, 2020