Extreme Programming Installed

Foreword.


Preface.


1. Extreme Programming.


2. The Circle of Life.


3. On-Site Customer.


4. User Stories.


5. Acceptance Tests.


Sidebar: Acceptance Test Samples.


6. Story Estimation.


Interlude: Sense of Completion.


7. Small Releases.


8. Customer Defines Release.


9. Iteration Planning.


10. Quick Design Session.


11. Programming.


Sidebar: Code Quality.


12. Pair Programming.


13. Unit Tests.


Sidebar: xUnit.


14. Test First, by Intention.


15. Releasing Changes.


16. Do or Do Not.


17. Experience Improves Estimates.


18. Resources, Scope, Quality, Time.


19. Steering.


20. Steering the Iteration.


21. Steering the Release.


22. Handling Defects.


Sidebar: Advanced Issue: Defect Databases.


Sidebar: Advanced Practice: Tests as Database.


23. Conclusion.


Bonus Tracks.


24. We'll Try.


25. How to Estimate Anything.


26. Infrastructure.


27. It's Chet's Fault.


28. Balancing Hopes and Fears.


29. Testing Improves Code.


30. XPer Tries Java.


31. A Java Perspective.


32. A True Story.


33. Estimates and Promises.


34. Everything That Could Possibly Break.


Afterword.


Annotated Bibliography.


Index. 0201708426T04062001

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