Scrum Masters: Evolve, or Become an Extinct Species

Last week, I facilitated my first workshop in almost two months. Every summer, Christiaan Verwijs and I block our calendars for reflection, innovation, and vacation. This session at Rabobank was the perfect way to kick off again. And yes, my facilitation skills were still there. The 20-ish Scrum Masters in the room sparked plenty of good conversations.

The theme was: “The evolving role of the Scrum Master”. I could (and probably will) write multiple posts about it. Here’s the first. And it begins with a simple observation:

👉 Apart from Scrum Masters (and trainers), nobody really cares about Scrum.

What people do care about:
✅ Building better products
✅ Delivering more value
✅ Enjoying their (team)work

Work together to make that happen.

Yes, Scrum can be a great enabler. But so can other approaches. Don’t get stuck in your Scrum bubble. If Scrum Masters want to stay relevant, paradoxically, they need to focus less on Scrum itself. Break free from the “Scrum-only” box. Don’t let the job title trap you into busywork that looks important but has little impact. 🤷‍♀️

Instead, team up with others to tackle the problems that truly matter, the ones that improve life for your team and the wider organization. That’s not always easy, but it’s where you’ll make the most significant difference.

Questions worth asking:

• How can we lift team morale?
• How can we improve productivity by focusing on value, not just output
• What’s driving high turnover in our team(s), and how can we reduce it
• Why are stakeholders dissatisfied, and what could we change?
• What support do teams get from management? Where’s the gap?
• How can we raise product quality while still releasing early and often
• How can we respond faster to real user feedback?
• Etc

These are the questions that matter. Not whether you should add another column to your board, rename a ceremony, or invent yet another burndown chart. 🙄

The future Scrum Master isn’t a framework expert; they’re team builders, change-makers, and problem solvers. Yes, problem solvers. Not “I only make problems visible”. Take some ownership to find a solution!

In short, evolve, or risk extinction. 🦕

Thoughts? How do you feel the Scrum Master role should evolve?