Extreme programming eXplained : embrace change

I came across this book in the Bibliography section of Scott Berkun's "The art of Project Management". First, the structure. Well, this book is under 200 pages. So when Beck talks about keeping what is essential, he is surely applying it while writing books. Second, the content. The book takes the reader from understanding business risks associated with software development, to understanding the changing economics of software development & why XP can fit the demands of an ever changing business scenario. The book then establishes what XP is, what are its features, what are the activities, who are the X players & then links the roles, activities, & features together across each phase in a typical XP project. While Beck is persuasive about the usefulness of XP, he has also included a chapter at the end of the book which talks about projects where using XP may not be advisable. And yes, such a project is an outsourced development project. XP presents many interesting features. Traveling light - or code & tests together being all you need - sounds like a dream; nano-releases - or doing a daily or hourly build so that at any time you have a full system working, no matter the completeness of desired functionality - , building a system story by story, & going back & revisiting scope ever so often are all features that can be immensely valuable to the business & to the project team. As a result of all this, & more such practices, XP resembles to an extent Darwinian evolution in some ways. Trying many things & keeping what works, designing for today's needs & changing that with tomorrow's requirements tomorrow but not today can be seen as interesting commonalities between Darwinian evolution & XP! Overall, I think the book is great introduction to XP. I'd have liked case studies as well to understand how well good theory fits general projects of any kind, but this book does not cite too many such projects. Nevertheless, pick it up if you want to understand what the XP evolution is all about. S! 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. Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.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. Beck wants to encourage readers to re-examine their preconceptions of how software development ought to occur. He does just that in this overview of Extreme Programming, a controversial approach to software development which challenges the notion that the cost of changing a piece of software must rise dramatically over the course of time.