#157. Rethink the role of the scrum master. Two recent events—a thought-provoking article by agile coach Maarten Dalmijn and a leave of absence by Matthew, a beloved scrum master in my team—prompted me to question if scrum masters might be overrated.

Comparing scrum teams to sports teams like Ultimate Frisbee, where players self-regulate without referees. Imagine a world where your scrum team operates the same way, holding each other accountable and mastering the game without a dedicated scrum master.

You'll learn about Maarten's controversial stance: in startups and scale-ups with fewer organizational impediments, having a scrum master might be unnecessary overhead. Instead, Martin suggests that with a deep understanding of scrum, your team could self-manage effectively.

I share my own team's bold experiment—replacing a traditional scrum master with a hybrid scrum master-developer. Spearheaded by Sapan, who has extensive experience in both development and scrum, this experiment offers surprising results.

It's not a one-size-fits-all solution for all Power Platform teams. But it does highlight the importance of being open to new practices and continuous experimentation in agile development.

Keep experimenting 🧪

-Neil

RESOURCES

• Maarten Dalmijn on LinkedIn
• Maarten Dalmijn, 'Are Scrum Masters Too Much Overhead?'