- Paperback: 288 pages
- Publisher: Inspect & Adapt Ltd; 1 edition (May 30, 2013)
- Language: English
- ISBN-10: 0957587406
- ISBN-13: 978-0957587403
- Product Dimensions: 6 x 0.6 x 9 inches
- Shipping Weight: 1.1 pounds (View shipping rates and policies)
- Average Customer Review: 32 customer reviews
- Amazon Best Sellers Rank: #143,548 in Books (See Top 100 in Books)
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 Mastery: From Good To Great Servant-Leadership Paperback – May 30, 2013
|New from||Used from|
Frequently bought together
Customers who bought this item also bought
About the Author
Geoff Watts is the founder of Inspect & Adapt Ltd and one of the most experienced and respected Scrum coaches in the world. Having started using Scrum at British Telecom, one of the first large-scale agile adoptions, he has since coached organisations large and small through their agile journeys.
An inspirational speaker at international conferences, he is at the cutting edge of the developments in the agile world. As well as his wealth of knowledge in the agile field, he is also passionate about promoting servant-leadership through his coaching practice.
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle edition for only $2.99 (Save 90%). Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Browse award-winning titles. See more
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Probably the most common problem of all are Scrum teams are team members showing up late for Scrum. Watts describes such a situation in one of the chapters. In the team’s retrospective, the team did not directly confront the team member, instead they kept to general statements and working agreements like “we should be on time to Scrum.” The “right answer” according to Watts would have been for the team to directly confront the team member. I wish he would have gone into detail how THAT went over. In my experience, most people would act defensive or overly emotional (for Americans maybe? Ha!). The only times I’ve seen this go over well is when a team member accepts the criticism, and that kind of emotional intelligence is not common. What is common, in my experience, is a reaction of stink eye looks and zombie impersonation. On occasion, cuss words combined with sarcasm explode like a door slamming in the center of a black hole in the middle of the universe.
Watts makes an astute observation that I don’t see acknowledged often in other agile books; “...each person either blocked or helped the problem solving process, whether intentionally or not”. Heavens to Murgatroyd! Do you ever notice how often this happens in Congress? When this happened in my own team, I used Watts’ words to describe my observation “Knocking down another person’s suggestion makes them less likely to offer one in the future.” In practice, I discovered that the teammate “getting knocked down” felt supported. And the person with the “yes, but…” tried to defend their position as well but offered more the second time around. It was a good tactic.
What I would like to see more from Watts is how to deal with difficult team members. He does say that by “make a hole [remove the difficult team member], to make [the team] whole”. I agree with this, but it’s not that easy to vote people off the island and out of the sprint team. One, there are HR policies in place to protect rights on both sides, the company and the person, and second, sometimes management just does not agree that the person IS a problem, especially if the person is a rock star. I would like to see more tactics from Watts how he deals with the zombies, the vampires, the werewolves and all the other devil advocates that contribute to software development. Just because someone is difficult to work with, does not mean they can’t make a great contribution to team. What are some exact tactics?
If I was a Scrum Alliance board member, I would make this required reading before giving out Scrum Master certifications. And then I would make everyone write an Amazon review on it; not to prove that they read the material but to prove they thought about it. It takes thoughtfulness how to deal with people and teams. For example, how one personality responses to a question will not be the same as another. The permutations of outcomes can be numerous, outrageous, and that is why Scrum Masters must learn to be more than just courageous. They must walk confidence. This book is just one of many tools to make Scrum Masters, true Masters.
This book tells Scrum Masters where to start and describes what a good Scrum Master looks like in multiple situations. It also goes on to describe the difference between a good Scrum Master and what separates them from good and great. It teaches them how to take their skills to the next level in order to build higher performing teams and organizations.
I recommend this book for Scrum Masters, Product Owners, Development Teams, and even Managers in agile organizations. This is the most powerful resource I have seen hit the market since I have been coaching.
Excellent job Geoff!