Roman Pichler

The book doesn't add much to the current literature.
Most of it can be found in most other agile project management books. During all the time I was reading it, i was wondering whether the target audience was product managers/owners or scrum masters!
What is not in other agile development books can be found in other product management books/blogs/articles or even in the Pragmatic Marketing framework.

To summarize I fully agree with TadAd: There just isn't enough to justify purchasing this… (meer)

The book is 118 pages long. When I think about the duplication in various sections of it, there's probably around half that many pages of content.

I'd divide that content into two type of material. The first is the same introductory information that you'd get if you downloaded Schwaber and Sutherland's overview of Scrum from scrum.org. The second type of material consists of discussions about pitfalls in implementing Scrum, pitfalls in management practices, as well as a very brief look at things like burndown charts and different ways of slicing a development project.

That first type of material is available for free; this book is $35...you do the math on that one. The second type of material isn't weighty enough to carry the price load—I really see it as a 25 page introductory chapter in a larger book that provides some real meat.

There just isn't enough here to justify purchasing this. Put the money toward something that provides more depth.… (meer)