Most helpful positive review
3 of 3 people found the following review helpful
Excellent overview of Agile in software development, and the different methods
on 3 February 2012
Barry's extensive experience and knowledge of the Agile software development process really shows in this book. He covers off the reasons why Agile (XP) was created in the first place, why it should be used, and most importantly, how it's been derailed and bastardized by all the agile hangers-on.
The book covers a lot of the history if agile, mostly focusing on eXtreme Programming, being that's where it all started, and to a lesser extent, why things like Pair Programming, Test First Development (and Test Driven - not the same), Continuous Integration and Customer Collaboration are not just desirable things in software, but a requirement if you are "doing agile".
Later in the book, he looks at a lot of different "styles" and rates them with out useful, or not, they are. Included in this (in my experience, correct) critique are User Stores, Lean, Scrim, XP, PRINCE2, DSDM and Kanban.
I think he's correct on all of them, and he's not at all pulling punches. Possibly, the "review" of XP is a little flourishing, but it is still honest - it just shows his knowledge and passion on the topic.
The book rounds out with observations on the whole software development practice, from an agile perspective.
All up, I enjoyed this book. It was a fairly easy read, tho a little slow to get started (esp the first chapter). But once into it, it's excellent advice for anyone running or participating in an Agile team, or anyone thinking about "doing agile" and wondering what it is, and more importantly, what Agile is NOT.
(side note: I think most people will find what they are doing is NOT agile, and not even "Agile". It's just "random". Possibly still better than waterfall, tho!)