This book offers interesting view and the mindset about scrum workflow.
Author discuss the iterative process in Scrum, and how typical Scrum work group taking decisions.
I found interesting the description of challenges during scrum workflow and how to deal with it.
Especially dealing with bottlenecks, author provides solution how to avoiding such situations.
Author propose to find a balance and have a constant feedback loop from the decision makers and the end client.
I like idea of the book to deliver value to client the whole time.
The comparison between waterfall and Scrum is interesting, but I think that Scrum can and do more positive rather than old and not flexible waterfall approach.
I love how book author did described the definition of done.
For me definition of done: implementing user stories, which reflect client actual requirements, which is enough to deliver a final product.
Scrum is powerful, not only it allows responding to rapid change it allows seeing actual progress of work, where more classic workflow does not allow such transparency and most times not transparent.
Author Rubin discuss the grooming process, which is collaborative work of different involved parties.
I liked the part in this book about velocity, which describe how really to evaluate a velocity of typical scrum project.
Very interesting part of this book was tech debt.
Technical debt is big topic and this book goes into depth to describe how to repay the technical debt.
Another topic, which I really, really liked in this book the description of Scrum master role and how this role helps the team to deliver high value.
Even in the big organizations, Scrum can work and the book describes that process too.
Sure teamwork in Scrum is essential and even crucial for success.
Description about planning in SCRUM is must to read.
Finally, the author presents a real case about scrum project, which was a website for Scrum alliance.
Author describe the agile way of release plan.
Here I think, I would disagree with author about creating minimum releasable features, scope is good as a goal of achievement, but to have a fix deadline on fix scope is not agile workflow.
The scrum retrospective is important part of scrum workflow.Summary: After reading this book , definitely you understand more how to approach Scrum workflow !
Bottom line, Scrum is a iterative flexible workflow it highly depends on the team and the client collaboration, scrum master plays a crucial part which responsible for balancing both involved parties, if you as company struggle with Scrum look into people first, then when you know people , only then look into the workflow itself!
Way to many companies doing such mistake!
Whom I can recommend this book: Well any manager should read it, developers who plan to play the role of scrum master and even CEO of the company should look into it.
This book is a must have and must read if you are serious about using Scrum in your company.