HOW TO KILL THE SCRUM MONSTER: QUICK START TO AGILE SCRUM METHODOLOGY AND THE SCRUM MASTER ROLE

by Bibik

Implement Scrum or improve how Scrum works in your team or organization using this concise, sharp, and programmatic book. You will quickly learn what you need to know without getting confused with unnecessary details.

What You'll Learn



Become familiar with Agile concepts and understand the path from Waterfall to the Agile Manifesto


Understand the most commonly used Agile methodology--Scrum--and how it relates to eXtreme Programming and Kanban as well as to Lean principles


Identify the challenges of the Scrum Master role and understand what this role is all about


Know the stages of Scrum team development
Embrace and solve conflicts in a Scrum team
Who This Book Is For
Anyone looking for a simple way to understand Scrum methodology

Paperback

Reviews

[John]

Full disclosure: There's a certain amount of irony that my comically sized Monster energy drink exploded on this book while it was in my backpack during a commute.

This books is pretty good for someone who has some familiarity with software project management; but for someone such as myself--who has project management experience but little software/tech background, it's still a bit wanting.

Ultimately, this isn't a cure all and I will need to supplement more books - but the scenario section is pretty good and helps wrap my head around it.

[Victor Velazquez · Rating 4 out of 5]

Quick guide for Agile Scrum Methodology and also with good real/fictional scenarios with possible solutions.

[Renato Barbieri · Rating 1 out of 5]

We need zero-stars ratings, guys. This one is just another example of a book that should be avoided at all costs. The cover is a hint that you shouldn't buy this book, as it states "Agile Scrum Methodology" -- Agile is a mindset, a philosophy, a movement; Scrum is a framework that adheres to the Agile movement values and principles; and stop using "methodology" when you mean "method". So, you see, that's a really bad start.

When discussing case scenarios, the author comes up with this "pearl of wisdom": "Have a retrospective meeting every second Sprint to reduce retrospective frequency." -- Wrong, wrong, wrong! Retrospectives are important events that should never be skipped, since this is part of the continuous improvement effort of a Scrum team (and indeed, any serious Agile team.)

Keep away from this stinker.

[Igal · Rating 5 out of 5]

Due to Corona lockdown, I have time now to read books I accumulated lately.
I did the Scrum Master role for a short time and got this book as a gift from a friend.
It said "How to kill the Scrum Master" on a sticky note.

I liked the book. It is not as pompous as similar books I tried to read and never finished.
The main Idea of this book: first understand why Agile/Scrum and then master the ideas; feel free to adjust it to your needs.
Shu Ha Ri.

Use cases at the end of the book also made me think that people are the same in every company.

I don’t think that Scrum enthusiasts that follow Scrum guidelines religiously will necessarily agree with this approach, and you can see this from other reviews, but personally I prefer to adjust things to my own needs.

[Katrin · Rating 5 out of 5]

This book is easy to consume, pragmatic, to the point and not overloaded.

[Bridget · Rating 4 out of 5]

Good primer. Appendix w case studies is awesome.

[Lauren Pybus · Rating 3 out of 5]

Some useful insights and explanations, I really liked the problems and solutions but I feel like it would be better if you were experiencing a really specific problem.

[Ghadeer Yehia · Rating 3 out of 5]

Good start to the new scrum master