A scrum master servant leader can lead his team to greatness with this advice from Geoff Watts’s wonderful book Scrum Mastery.
The following is a guest post by Charlie Davidson.
Please see the Editor’s note below regarding the variation in spelling of the term Scrum Master.
Scrum’s framework is easy to understand but hard to master.
The ScrumMaster role is no different.
Let’s spend some time exploring the challenges ScrumMasters face and how to overcome them. Especially in the role of Scrum Master as a Servant Leader.
It’s important to say this leans on the teachings of Geoff Watts and his brilliant book Scrum Mastery. The good versus great concept is one he frequently uses, and I’ve purposely quoted him throughout this post to give it structure.
But we get ahead of ourselves.
What is SCRUM and a Scrum Master?-
I’ll keep this light, as I’m sure many of you are familiar with the framework.
If you’re not, check out some of the more basic guides first. I’d suggest the official guide as a good starting point.
Related reading: Scrum Master vs Project Manager: What’s the Difference?
Scrum is the most commonly used agile delivery method in the world.
It’s a lightweight framework that empowers teams to build quickly through iterative design. An iterative approach means delivering part of a product, getting feedback, and then adapting the product and the team based on that feedback.
Scrum teams regularly build better products faster, while being happier too.
Scrum Masters: Team Servant Leaders-
The Scrum Master is a servant leader role that helps the team, and the broader company, understand the Scrum theories, practices, rules, and values.
This role is often mistakenly seen as a junior position. In reality, it requires maturity, influence, and creativity to support the Scrum framework effectively. The Scrum Master servant leader has a big role in a scrum team’s success.