Summary

Extreme Programming Installed is a short presentation of the core practices composing the emerging discipline of Extreme Programming (XP). The book is a connected collection of essays by experienced users of XP, and the material is presented in the order in which it should be implemented in a development project. The authors' unique approach allows this book to be used in a tutorial/user guide fashion, while the individual essays can be continually accessed as a quick reference to specific aspects of XP. The result is a book that allows the reader to improve the quality of their software development efforts with XP.

Author Biography

Ron Jeffries was the on-site XP coach for the original Extreme Programming project, a large financial system for a major automotive manufacturer. An independent consultant who has been involved in eXtreme Programming for over more than four years, he has presented numerous talks and published several papers on the topic. Ron has been a systems developer for more years than most of you have been alive, and his teams have built operating systems, compilers, relational database systems, and a wide range of applications. He has not, as yet, run out of new ways to make mistakes (and resolve them). Ron has recently joined forces with Object Mentor, Inc., to help more people improve their software process.

Ann Anderson is an independent consultant engaged full time in coaching XP and in teaching and using Smalltalk for financial applications development. Ann was a team member on the large payroll system that was the original proving ground for Extreme Programming. Throughout her career she has been involved in object-oriented projects spanning control systems, insurance, tax, and finance.

Chet Hendrickson is a systems architect at ThoughtWorks, Inc, where he makes sure that programmers and customers know and understand their rights. Previously, Chet was a senior software systems specialist at a major automobile manufacturer, where he worked on a large operational finance system that was the test bed for Extreme Programming. He was the winner of the Project Manager Game at OOPSLA'99 (although he thinks it might have been rigged).

0201708426AB05082001

Foreword

xiii

Preface

Extreme Programming

(12)

The Circle of Life

(4)

On-Site Customer

(6)

User Stories

(8)

Acceptance Tests

(6)

Sidebar Acceptance Test Samples

(2)

Story Estimation

(12)

Interlude Sense of Competion

(4)

Small Releases

(6)

Customer Defines Release

(6)

Iteration Planning

(8)

Quick Design Session

(2)

Programming

(16)

Sidebar Code Quality

(4)

Pair Programming

(6)

Unit Tests

(14)

Sidebar xUnit

105

(2)

Test First, by Intention

107

(14)

Releasing Changes

121

(6)

Do or Do Not

127

(4)

Experience Improves Estimates

131

(4)

Resources, Scope, Quality, Time

135

(12)

Steering

147

(4)

Steering the Iteration

151

(6)

Steering the Release

157

(4)

Handling Defects

161

(10)

Sidebar Advanced Issue: Defect Databases

165

(4)

Sidebar Advanced Practice: Tests as Database

169

(2)

Conclusion

171

(6)

Bonus Tracks

175

(2)

We'll Try

177

(8)

How to Estimate Anything

185

(4)

Infrastructure

189

(4)

It's Chet's Fault

193

(2)

Balancing Hopes and Fears

195

(4)

Testing Improves Code

199

(4)

XPer Tries Java

203

(8)

A Java Perspective

211

(14)

A True Story

225

(4)

Estimates and Promises

229

(4)

Everything That Could Possibly Break

233

(10)

Afterword

243

(2)

Annotated Bibliography

245

(16)

Index

261

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

Preface How much would you pay for a software development team that would do what you want? Wait, don't answer yet--what if they could also tell you how much it would cost, so that you could decide what to do and what to defer, on your way to your deadline? You also get quality software, a robust array of tests that support the project through its entire lifecycle, and an up-to-date, clear view of project status. Best of all, you get the ability to change your mind about what you want, at any time. There aren't any silver bullets in software development, and there probably never will be. However, Extreme Programming is a simple set of common-sense practices that, when used together, really can give you much of what you just read in the paragraph above. In this book, we tell you what the XP practices are, and how to install them in your project. We are software developers. We have been involved in many successful projects, and even in some that weren't so successful. The successful ones were a lot more fun, for us, and for our customers. The unsuccessful ones have taught us a great deal about software development. We have had the privilege of working on a great project, with a great teacher, Kent Beck. We helped shape the software process named Extreme Programming, XP for short. Since then, we have been helping everyone who will listen to learn from our experience. The first book in the Extreme Programming series,Extreme Programming Explained ,covers the reasoning behind the XP process. Based on our experience on the original XP project (and others), this book describes what makes XP work, day to day and month to month. Successful software development is a team effort--not just the development team but the larger team consisting of customers, management, and developers. Extreme Programming is a simple process that brings these people together and helps them to succeed together. XP is aimed primarily at object-oriented projects using teams of a dozen or fewer programmers in one location. We would use XP for both in-house development and development of shrink-wrapped software. The principles of XP apply to any moderately sized project that needs to deliver quality software rapidly and flexibly. XP is about balancing the needs of customers with the abilities of programmers, and about steering (managing the project to success). If you're a customer, a programmer, or a manager, here's what this book offers you: Customers--who have software that needs to be developed: you will learn simple, effective ways to communicate what you need, to be sure that you are getting what you need, and to steer the project to success. You will learn that you can change your mind and still get what you need on time. Programmers--who, on an XP project, define the architecture, design the system, and write the tests and the code that support them: you will learn how to deliver business value quickly, how to deal with changing requirements, and how to build customer confidence and support. You will learn to build for tomorrow by building only what you need today. Managers--who control the project resources: you will learn how to measure project progress, how to measure quality, and how to answer the all-important question, "When will you be done?" You will learn an important truth of management--to use the programmers' actual performance to predict completion. Customers, programmers, and managers must all work together to build the system that's needed. Chapter 1,Extreme Programming, will describe the roles, rights, and responsibilities, and provide a road map for the book. Dig right in. We're sure that the XP practices can improve your projects, as they have ours. 0201708426P04062001