I’ve seen teams implementing the idea of Sprint Sheriff (AKA Officer, Keeper and probably few other names). What it means, that for each sprint (which is usually 1-2 weeks) a different team member would be responsible for all or a subset of the following activities:
- running daily meetings,
- preparing & facilitating retrospective,
- presenting team’s achievements during demo,
- taking care of production issues
This approach has some serious advantages over the fixed team roles. First, all team members learn all the details of various team activities and practice the skills required to perform them. Second, no one feels overburdened & bored with going through the same activities week by week.
A nice trick is to create an alias on your Slack channel so that people don’t need o know who is the sheriff right now – they always contact @sprint-sheriff or sth. similar.
I wonder if you have worked in such (or similar) settings and could share some of your experience. Would be great if you could comment on this.
P.S. See also Tai Tsao “Why You Need To Be Rotating Meeting Roles” for a nice explanation of what you gain by rotating meeting roles.
I can see this working great in teams where there is a sense of shared code ownership and responsibility.
That’s most teams.
Or at least some teams…