Extreme Programming Explained Embrace Change

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.

Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.

Cynthia Andres holds a B.S. in psychology with advanced work in organizational behavior, decision analysis, and women’s studies. She has worked with Kent on the social aspects of Extreme Programming since its inception. She is also affiliated with Three Rivers Institute.

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.