In my blog post, “Growing and Improving as a ScrumMaster,” I wrote: So, how do I know if my ScrumMaster is effective? Consider these three questions: Are we making the same mistakes time and time again?– A good ScrumMaster will work with the team to ensure that once a mistake is made, that the team […]
In my blog post, “Growing and Improving as a ScrumMaster,” I wrote:
So, how do I know if my ScrumMaster is effective? Consider these three questions:
- Are we making the same mistakes time and time again?– A good ScrumMaster will work with the team to ensure that once a mistake is made, that the team develops practices to ensure they do not continue repeating the same error. Mistakes are things the team does that does not have the outcomes or consequences they intended.
- Are we encountering the same issues time and time again?– A good ScrumMaster works with the team so that when issues arise, the teams can recognize issues as they arise and will put in practices to ensure that those issues are effectively dealt with going forward. Issues are problems that arise that the teams did not directly create.
- Are we getting better over time or are we stuck where we are? – The concept of having highly effective teams versus ineffective teams is relative. What we really want is that our team is getting better over time.
If we see that our teams are not repeating the same mistakes, that our teams recognize issues as they arise and are able to effectively deal with those issues, and that our teams are constantly improving, then that’s a signal that we have an effective ScrumMaster. If these things are not true, that’s a sign that your ScrumMaster needs to improve their abilities to work through these issues with their team.
To expand on this concept, one of the key goals of the ScrumMaster is to ensure their team is continuously working through problems and improving. To aid with this, I have created a checklist for ScrumMasters that are potentially stuck on one issue and unsure how to proceed.
Note the first four items above are part of the team’s retrospectives to address the problem. Items 5, 6, and 7 are discussed in the subsequent retrospectives to see if the problem is addressed.
If we have a Scrum team that is continuously experiencing the same problem, I would pose these seven questions to the ScrumMaster. Any ScrumMaster that’s fumbles and bumbles in answering these questions is probably a ScrumMaster who’s still a bit green and working through their ability to help the team work through their issues.
For information on how to improve as a ScrumMaster, see Growing and Improving as a ScrumMaster.
Put as simply as possible, Scrum is a methodology that helps teams work better together....
Why were A-CSM and CSP-SM created? Created by the Scrum Alliance and started in 2002,...
On Scrum teams, velocity represents how much work a team can do each sprint. For...