- Format: Kindle Edition
- File Size: 617 KB
- Print Length: 119 pages
- Publisher: Pashun Publishing Press; 1 edition (12 Aug. 2014)
- Sold by: Amazon Media EU S.à r.l.
- Language: English
- ASIN: B007YUNT5C
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Average Customer Review: Be the first to review this item
- Amazon Bestsellers Rank: #446,888 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Scrum, The Complete Overview and Guide (Boxset), For the Agile Scrum Master, Product Owner, Stakeholder and Development Team (inspired by Ken Schwaber, Mike Cohn, Jeff Sutherland) Kindle Edition
Customers who bought this item also bought
Would you like to tell us about a lower price?
What other items do customers buy after viewing this item?
|5 star (0%)|
|4 star (0%)|
|3 star (0%)|
|2 star (0%)|
|1 star (0%)|
Most helpful customer reviews on Amazon.com
The book could easily serve as a guide to the SCRUM test but for me it will be a manual that I look back to while working with SCRUM. This book is a great reference to have in my digital library. I recommend this book as a good read.
For example, it says that the Product Owner role is usually played by a Product Manager and that the ScrumMaster is played by a Project Manager. All descriptions of requirements discussions reflect that orientation: all requirements are written, and the place of dialog with the Product Owner is minimized.
While being faithful to some of the Scrum definitions, it fails on the deeper foundations. Rather than focusing on team Kaizen, it allocates all impediment removal to the ScrumMaster. It waffles about the Definition of Done and, in the end, gets it wrong. It emphasizes that the team comprise "domain experts" and fails to drive at team learning. It says little or nothing about scaling and cross-team coordination, most likely because they are outside the scope of the author's experience.
And in some places it is unfaithful to any conscionable definition of Scrum: It says that the team does not commit to the Sprint Goal (it does); in release planning it makes no mention of velocity variance (this is a standard Project Manager failure); it allows "small" amounts of Product Owner interference during the Sprint (none is allowed).
In the final analysis, you can download this book from the web at no cost, and I can attest that, from that source, it's worth every penny.