Do you have the same person acting as a Scrum master for every iteration in your team(s)? Or do different team members take the role on turns? I’d like to hear how you do it, what works for you, and why.
The Scrum master rol should be fixed *during* an iteration but it can change *over* the iterations. So for instance one team member can be Scrum master for iterations 1 and 2, then another team member for 3 and 4, then the first team member again for iteration 5 and 6, etc.
Having the same person for the Scrum master in every iteration is easy, and it makes things clear for everyone. Most teams do this, and it seems to work. So why would you rotate the Scrum master role?
One advantage of switching the Scrum master is that during an iteration the Scrum master can focus with the team on realizing the user stories from the ongoing iteration, while the Scrum master for the next iteration gives extra attention on grooming the backlog with the product owner, and having good user stories when the next iteration starts.
Another advantage of Scrum master rotation is that you have a backup in case the team’s Scrum master becomes ill, is away for a longer period or not available due to some other reason.
If there is more than one team members who acts as a Scrum master then they can support each other when things get tough. They can also learn from each other.
Have you rotated the Scrum master role? Or do you work with fixed Scrum masters? I would love to hear from you!