We do Scrum but…
Are you serious? — episode 34
A while ago someone told me this:
“No-one wants to be the Scrum Master in our team. That is why we decided to rotate. Every Sprint we switch the Scrum Master role.”
He said it like he had an epiphany to come with this solution for a problem. I found it quite unsettling though as this was a struggling team. I think I wouldn’t be bothered this much if the team was doing great.
Scrum Mastery
Because what is the role of the Scrum Master? This is the first thing you read in the Scrum Guide, which says it all:
“The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.” — SG
Helping everyone understand Scrum theory, practices, rules and values. This is asking a lot from someone. It does require at least a basic understanding of Scrum. And realistically it requires more. So how can it be that within a struggling team — having major issues with Scrum adoption — the Scrum Master changes so often?
Scrum Secretary
Well, maybe it is because the Scrum Master role is reduced to being the secretary, doing the administration of the team and planning the events? I can imagine you could rotate this role. The thing is: administration is not what a Scrum Master is supposed to do! That leaves planning the events:
“Facilitating Scrum events as requested or needed” — SG
So yes this is something that a Scrum Master could do, but it could just as well be done by someone else from the team. Because a Scrum Master facilitates ‘as requested or needed’.
The truth is that this Scrum Team has no clue what Scrum is about and what a Scrum Master’s role is here! For more on the Scrum Master’s role I recommend this read:
The Scrum Master
Road to PSM III — Episode 7, part 1.medium.com
Scrum Champions
On the other side of the spectrum is the team that lives and breathes Scrum. Scrum has few secrets for them. I could see how you could rotate the Scrum Master role if this is the situation. I have heard from people that they have worked like this, where the whole team would have a Scrum Master certification. But I yet have to see such a team while I have seen enough teams struggling because of lack of Scrum knowledge.
Dropping the ball
By switching the Scrum Master role often focus and commitment could be lost which can result into dropping the ball. For the rotation to be effective the new Scrum Master should be up to par with the old Scrum Master. This requires serious preparation. The question is if this is considered by teams that rotate the role because no-one wants to be the Scrum Master. The answer probably is ‘No’.
Bottom Line
Rotating the Scrum Master often (like every Sprint) could be a good idea if Scrum has few secrets for the team. But this requires true dedication to be effective.
But it doesn’t work for teams that are struggling with Scrum. They need stability and a Scrum Master who’s is willing to invest in the team and in herself or himself to be a better Scrum Master. That will allow a team to grow over time.
Thanks for reading. Feel free to bang that clap button. You can give up to 50 👏’s. Give it a try if you enjoy this article!
My twitter profile is https://twitter.com/WJAgeling