Extreme Programming Explained Embrace Change

by Beck, Kent; Andres, Cynthia

• ISBN13: 9780321278654
• ISBN10: 0321278658
• Edition: 2nd
• Format: Paperback
• Copyright: 2004-11-16
• Publisher: Addison-Wesley Professional

Summary

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

Author Biography

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.

0

Table of Contents

Foreword to the Second Edition	xv
Foreword to the First Edition	xvii
Preface	xxi
What is XP?	1	(8)
Section 1 Exploring XP	9	(114)
Learning to Drive	11	(2)
Values, Principles, and Practices	13	(4)
Values	17	(6)
Communication	18	(1)
Simplicity	18	(1)
Feedback	19	(1)
Courage	20	(1)
Respect	21	(1)
Others	21	(2)
Principles	23	(12)
Humanity	24	(1)
Economics	25	(1)
Mutual Benefit	26	(1)
Self-Similarity	27	(1)
Improvement	28	(1)
Diversity	29	(1)
Reflection	29	(1)
Flow	30	(1)
Opportunity	30	(1)
Redundancy	31	(1)
Failure	32	(1)
Quality	32	(1)
Baby Steps	33	(1)
Accepted Responsibility	34	(1)
Practices	35	(2)
Primary Practices	37	(18)
Sit Together	37	(1)
Whole Team	38	(1)
Informative Workspace	39	(2)
Energized Work	41	(1)
Pair Programming	42	(2)
Stories	44	(2)
Weekly Cycle	46	(1)
Quarterly Cycle	47	(1)
Slack	48	(1)
Ten-Minute Build	49	(1)
Continuous Integration	49	(1)
Test-First Programming	50	(1)
Incremental Design	51	(4)
Getting Started	55	(6)
Corollary Practices	61	(12)
Real Customer Involvement	61	(1)
Incremental Deployment	62	(1)
Team Continuity	63	(1)
Shrinking Teams	64	(1)
Root-Cause Analysis	64	(2)
Shared Code	66	(1)
Code and Tests	66	(1)
Single Code Base	67	(1)
Daily Deployment	68	(1)
Negotiated Scope Contract	69	(1)
Pay-Per-Use	69	(4)
The Whole XP Team	73	(12)
Testers	74	(1)
Interaction Designers	75	(1)
Architects	75	(1)
Project Managers	76	(1)
Product Managers	77	(1)
Executives	78	(2)
Technical Writers	80	(1)
Users	81	(1)
Programmers	81	(1)
Human Resources	81	(1)
Roles	82	(3)
The Theory of Constraints	85	(6)
Planning: Managing Scope	91	(6)
Testing: Early, Often, and Automated	97	(6)
Designing: The Value of Time	103	(8)
Simplicity	109	(2)
Scaling XP	111	(8)
Number of People	111	(2)
Investment	113	(1)
Size of Organization	113	(1)
Time	114	(1)
Problem Complexity	115	(1)
Solution Complexity	115	(1)
Consequences of Failure	116	(3)
Interview	119	(4)
Section 2 Philosophy of XP	123	(38)
Creation Story	125	(6)
Taylorism and Software	131	(4)
Toyota Production System	135	(4)
Applying XP	139	(6)
Choosing a Coach	143	(1)
When You Shouldn't Use XP	144	(1)
Purity	145	(4)
Certification and Accreditation	146	(3)
Offshore Development	149	(4)
The Timeless Way of Programming	153	(4)
Community and XP	157	(2)
Conclusion	159	(2)
Annotated Bibliography	161	(14)
Index	175

Excerpts

The goal of Extreme Programming (XP) is outstanding software development. Software can be developed at lower cost, with fewer defects, with higher productivity, and with much higher return on investment. The same teams that are struggling today can achieve these results by careful attention to and refinement of how they work, by pushing ordinary development practices to the extreme. There are better ways and worse ways to develop software. Good teams are more alike than they are different. No matter how good or bad your team you can always improve. I intend this book as a resource for you as you try to improve. This book is my personal take on what it is that good software development teams have in common. I've taken things I've done that have worked well and things I've seen done that worked well and distilled them to what I think is their purest, most "extreme" form. What I'm most struck with in this process is the limitations of my own imagination in this effort. Practices that seemed impossibly extreme five years ago, when the first edition of this book was published, are now common. Five years from now the practices in this book will probably seem conservative. If I only talked about what good teams do I would be missing the point. There are legitimate differences between outstanding teams' actions based on the context in which they work. Looking below the surface, where their activities become ripples in the river hinting at shapes below, there is an intellectual and intuitive substrate to software development excellence that I have also tried to distill and document. Critics of the first edition have complained that it tries to force them to program in a certain way. Aside from the absurdity of me being able to control anyone else's behavior, I'm embarrassed to say that was my intention. Relinquishing the illusion of control of other people's behavior and acknowledging each individual's responsibility for his or her own choices, in this edition I have tried to rephrase my message in a positive, inclusive way. I present proven practices you can add to your bag of tricks. No matter the circumstance you can always improve. You can always start improving with yourself. You can always start improving today. 0321278658P11022004