This is probably the most useful book I’ve read in the last year. Anyone that works on an agile software team and has to deal with user stories in any way needs this book. Whether you’re on the owner side, the management side, or on the development team there’s a tremendous amount of detail in here.
One of the great things about this tiny manual is that it goes through each of the common pitfalls of writing user stories and connects appropriate solutions. It goes through the consequences of the various solutions because, unlike many books out there, this is written from a very “been there, done that” point of view.
The last thing I’d point out is that this is not a book for developers, managers, or CEO’s. It’s for all of them. I mean that the writers have taken the time to point out what every stake holder needs from user stories in order for the project to succeed. For instance, Adzic and Evans go through why owners love scope creep but then explain why and how it’s a healthy part of the cycle. While a lot of these books are about blame, this one is way more about reality and getting across the finish line without falling into common traps.