Extreme Programming Explained: Embrace Change, 2nd Edition

About

Features

An updated look at the roots, philosophies, stories, and myths associated with Extreme Programming (XP).

° Five years later, a thorough and entertaining re-examination of XP that explains what's good, what still needs work, and where the methodology is headed

° New afterword recounts the author's experiences that led him to develop and refine XP -- an insightful section that should inspire any organization to adopt XP

° Product launch at October's OOPSLA in Vancouver, BC



Description

• Copyright 2005
• Dimensions: 7-3/8" x 9-1/4"
• Pages: 224
• Edition: 2nd

• Book
• ISBN-10: 0-321-27865-8
• ISBN-13: 978-0-321-27865-4

“In this second edition of Extreme Programming Explained, Kent Beck organizes and presents five years’ worth of experiences, growth, and change revolving around XP. If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book.”

—Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L.

“The first edition of this book told us what XP was—it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the ‘why’ of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the ‘what’ and the ‘why,’ we can now all set out to confidently work on the ‘how’: how to run our projects better, and how to get agile techniques adopted in our organizations.”

—Dave Thomas, The Pragmatic Programmers LLC

“This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there’s an excellent chapter on ‘primary practices,’ but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck’s book: ‘XP is about social change.’ You should do whatever it takes to ensure that every IT professional and every IT manager—all the way up to the CIO—has a copy of Extreme Programming Explained on his or her desk.”

—Ed Yourdon, author and consultant

“XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline.”

—Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software

“Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled ‘extreme.’...”

—Lou Mazzucchelli, Fellow, Cutter Business Technology Council

“If your organization is ready for a change in the way it develops software, there’s the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years.”

—Philippe Kruchten, UBC, Vancouver, British Columbia

“Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity.”

—Mary Poppendieck, author of Lean Software Development: An Agile Toolkit

“Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both easy and hard: It can be started with fewer practices, and yet it challenges teams to go farther than ever.”

—William Wake, independent consultant

“With new insights, wisdom from experience, and clearer explanations of the art of Extreme Programming, this edition of Beck’s classic will help many realize the dream of outstanding software development.”

—Joshua Kerievsky, author of Refactoring to Patterns and Founder, Industrial Logic, Inc.

“XP has changed the way our industry thinks about software development. Its brilliant simplicity, focused execution, and insistence on fact-based planning over speculation have set a new standard for software delivery.”

—David Trowbridge, Architect, Microsoft Corporation

Accountability. Transparency. Responsibility. These are not words that are often applied to software development.

In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process.

The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years. This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a program of continuous improvement based on:

• Five core values consistent with excellence in software development
• Eleven principles for putting those values into action
• Thirteen primary and eleven corollary practices to help you push development past its current business and technical limitations

Whether you have a small team that is already closely aligned with your customers or a large team in a gigantic or multinational organization, you will find in these pages a wealth of ideas to challenge, inspire, and encourage you and your team members to substantially improve your software development.

You will discover how to:

• Involve the whole team—XP style
• Increase technical collaboration through pair programming and continuous integration
• Reduce defects through developer testing
• Align business and technical decisions through weekly and quarterly planning
• Improve teamwork by setting up an informative, shared workspace

You will also find many other concrete ideas for improvement, all based on a philosophy that emphasizes simultaneously increasing the humanity and effectiveness of software development.

Every team can improve. Every team can begin improving today. Improvement is possible—beyond what we can currently imagine. Extreme Programming Explained, Second Edition, offers ideas to fuel your improvement for years to come.



Extras

Related Articles

Conventional Software Testing on an Extreme Programming Team

Getting Started with eXtreme Programming: Toe Dipping, Racing Dives, and Cannonballs



Sample Content

Online Sample Chapter

What is XP?

Sample Pages

Download the sample pages (includes Chapter 1 and Index)

Table of Contents

Foreword to the Second Edition.

Foreword to the First Edition.

Preface.

1. What is XP?

I. EXPLORING XP.

2. Learning to Drive.

3. Values, Principles, and Practices.

4. Values.

    Communication.

    Simplicity.

    Feedback.

    Courage.

    Respect.

    Others.

5. Principles.

    Humanity.

    Economics.

    Mutual Benefit.

    Self-Similarity.

    Improvement.

    Diversity.

    Reflection.

    Flow.

    Opportunity.

    Redundancy.

    Failure.

    Quality.

    Baby Steps.

    Accepted Responsibility.

6. Practices.

7. Primary Practices.

    Sit Together.

    Whole Team.

    Informative Workspace.

    Energized Work.

    Pair Programming.

    Stories.

    Weekly Cycle.

    Quarterly Cycle.

    Slack.

    Ten-Minute Build.

    Continuous Integration.

    Test-First Programming.

    Incremental Design.

8. Getting Started.

9. Corollary Practices.

    Real Customer Involvement.

    Incremental Deployment.

    Team Continuity.

    Shrinking Teams.

    Root-Cause Analysis.

    Shared Code.

    Code and Tests.

    Single Code Base.

    Daily Deployment.

    Negotiated Scope Contract.

    Pay-Per-Use.

10. The Whole XP Team.

    Testers.

    Interaction Designers.

    Architects.

    Project Managers.

    Product Managers.

    Executives.

    Technical Writers.

    Users.

    Programmers.

    Human Resources.

    Roles.

11. The Theory of Constraints.

12. Planning: Managing Scope.

13. Testing: Early, Often, and Automated.

14. Designing: The Value of Time.

    Simplicity.

15. Scaling XP.

    Number of People.

    Investment.

    Size of Organization.

    Time.

    Problem Complexity.

    Solution Complexity.

    Consequences of Failure.

16. Interview.

II. PHILOSOPHY OF XP.

17. Creation Story.

18. Taylorism and Software.

19. Toyota Production System.

20. Applying XP.

    Choosing a Coach.

    When You Shouldn't Use XP.

21. Purity.

    Certification and Accreditation.

22. Offshore Development.

23. The Timeless Way of Programming.

24. Community and XP.

25. Conclusion.

Annotated Bibliography.

Index.

Foreword

Download the Foreword file related to this title.

Index

Download the Index file related to this title.



Updates

Submit Errata

