Extreme Programming (XP) is a revolutionary lightweight methodology that's supercharging software development in organizations worldwide. Perfect for small teams producing software with fast-changing requirements, XP can save time and money while dramatically improving quality. In XP Installed , three participants in DaimlerChrysler's breakthrough XP project cover every key practice associated with XP implementation. The book consists of a connected collection of essays, presented in the order the practices would actually be implemented during a project. Ideal as both a start-to-finish tutorial and quick reference, the book demonstrates exactly how XP can promote better communication, quality, control, and predictability. An excellent complement to the best selling Extreme Programming Explained , it also works perfectly on a standalone basis, for any developer or team that wants to get rolling with XP fast .
Per some requirements at work to assist everyone with a common understanding of Agile/XP development, it was requested that we all read this book. I had no problems with the request and gratefully accepted the free material. However, I was a bit critical in my initial judgment as I glanced through the chapters and noticed that there were a lot of dumb-looking sketches. The book is 244 pages long, and contains 34 chapters. So there's at least 34 pages of goofy art.
So overall I think this is a great book about becoming familiar with some of the ideologies of EXtremete Programming. The book is great about identifying common project/coding practices that often lead to inefficiencies or error. Lots of suggestions and supporting anecdotes about embracing XP styles. They (authors) are big on pair programming and testing-before-developing methodologies. I found myself agreeing with a lot of what they had to say, and the reading gave me many ideas to consider.
An overall good explanation of XP fundamentals is seen here (taken from the last page), "Quite simply, I think that XP works because it is validation-centric rather than product-centric...validation means that somebody other than the producer analyzes the product and assures that it satisfies its purpose...Are we developing the right software? Are we developing the software right?"
In my opinion, the book is not worth $29.95, but maybe worth $15. If you want some new ideas about fixing coding/project methodologies, this book will prime your mind with possible new approaches.
It's a _little_ more specific than _Extreme Programming Explained_. It helps understand the concepts and goes into some details, most notably regarding TDD, with examples of simplistic classes and tests. In Smalltalk, which I guess wouldn't be too hard to understand - except I don't care to learn that programming language, and the meaning of the included code is not as obvious as the author would like to think.
However, many areas lack concrete, real-world examples - or don't pursue them into fully-developed real-world situations. That's what this book seemed to promise, but does not deliver.
The Addenda is perhaps the best part of the book. It contains several real-world stories that ARE very helpful in getting a feel for working on an XP team.
Sadly what shines out in this book is the fact that others have made better contributions to the canon of agile knowledge. Particularly time has bitten into the value of the Java coverage as well as the way the team aspect of development is approached. I'd say now buy XP Explained and leave this book as a historical artefact.