We teach a lot of public and on-site Agile and Scrum classes and one of the most frequently asked questions that people ask is “Who makes a good Scrum Master?” If it’s not that specific question, it’s usually a variant of it like “Does a QA engineer make a good Scrum Master” or “Does a Project Manager make a good Scrum Master”. The key to these questions is that they all have the same basic root question.
What ROLE THAT I UNDERSTAND would make a good ROLE THAT I DON’T UNDERSTAND?
I refer to these types of questions as “role mapping” questions. It means that students are basically trying to make sense of new information, in this case a role in Scrum, by trying to map the role to something they already understand well. It’s simply one of the ways us humans try to make sense of things. Is the information that was just presented the same or different than something I already know? If it’s the same, I get it and I nod knowingly. If it’s different, I put on a puzzled look while I try to map it to something I know. If I find something that sounds close, I raise my hand and ask a mapping question.
So how do I answer the question? Well, one of the techniques I use with a “role mapping” question in Scrum is responding with a metaphor question. For example, does a good catcher on a baseball team make a good goalie on a hockey team? Well, both athletes have a collection of gear needed to be safe and play well. They also both spend a lot of time squatting down low and stopping things that are coming at them very fast. The positions do, however, require some very different skills and training to perform them well. So even though catchers and goalies may share some outward similarities, what makes a good catcher doesn’t necessarily make a good goalie. And vice versa.
So what’s the learning I try to help them find? When thinking about who would make a good Scrum Master, think outside the “role box” and look at the skills needed to be a good Scrum Master. For example:
- Facilitates meetings effectively
- Practices situational leadership
- Spots and eliminates waste
- Exhibits servant leadership
- Helps navigate conflict
- Encourages self organization
- Champions collaboration
In other words, I believe “role mapping” questions can be answered by converting them to “skill mapping” questions. For example, “Who makes a good Scrum Master” becomes “What skills make a good Scrum Master.”
This is especially important when you’re really trying to identify a Scrum Master for a team. Why? Because Scrum Masters have a key role on teams and skill match is way more important than previous role. So what can you do when the team doesn’t possess a person with the right skills or interest in building those skills? Consider going skill fishing in a bigger pond. A lot of people with the skills it takes to be a good Scrum Master might live in other areas in your company. Besides, there’s no rule in Scrum that says a Scrum Master must come from the team. There is, however, a rule that says a team must have a Scrum Master.
Oh, yeah. While you’re at it, make sure they opt into the role. On the big list of things to NOT DO with Scrum, “anointing people with roles” comes right after “mandating Scrum on teams”.
Thanks for reading.
Comments are closed.