Extreme Programming (xp) Was Conceived And Developed To Address The Specific Needs Of Software Development Conducted By Small Teams In The Face Of Vague And Changing Requirements. This New Lightweight Methodology Challenges Many Conventional Tenets, Including The Long-held Assumption That The Cost Of Changing A Piece Of Software Necessarily Rises Dramatically Over The Course Of Time. Xp Recognizes That Projects Have To Work To Achieve This Reduction In Cost And Exploit The Savings Once They Have Been Earned. You May Love Xp Or You May Hate It, But Extreme Programming Explained Will Force You To Take A Fresh Look At How You Develop Software.--jacket. Foreword -- Preface -- Chap. 1. Risk : The Basic Problem -- Chap. 2. A Development Episode -- Chap. 3. Economics Of Software Development -- Chap. 4. Four Variables -- Chap. 5. Cost Of Change -- Chap. 6. Learning The Drive -- Chap. 7. Four Values -- Chap. 8. Basic Principles -- Chap. 9. Back To Basics -- Chap. 10. Quick Overview -- Chap. 11. How Could This Work? -- Chap. 12. Management Strategy -- Chap. 13. Facilities Strategy -- Chap. 14. Splitting Business And Technical Responsibility -- Chap. 15. Planning Strategy -- Chap. 16. Development Strategy -- Chap. 17. Design Strategy -- Chap. 18. Testing Strategy -- Chap. 19. Adopting Xp -- Chap. 20. Retrofitting Xp -- Chap. 21. Lifecycle Of An Ideal Xp Project -- Chap. 22. Roles For People -- Chap. 23. 20-80 Rule -- Chap. 24. What Makes Xp Hard -- Chap. 25. When You Shouldn't Try Xp -- Chap. 26. Xp At Work -- Chap. 27. Conclusion. Kent Beck. Includes Bibliographical References (p. 167-176) And Index.
