What happens when the team gets all the training about Scrum, begins to kickoff the process but they don’t have a Scrum Master?
There are arguments (some legitimate and some not) to justify why Scrum will work without a Scrum Master. First, let me say that a Scrum Master is a role not a title so there really shouldn’t be any restrictions on who can fulfill the role. Second, someone should take on the role and really dedicate time and energy to give the team the support they deserve. Check out Mike Cohn’s blog about Rotating the Scrum Master Role.
So what work does a Scrum Master do that now needs to be covered by someone else or the team as needed? There have been a number of response to this question all over the internet and books so you’ve all probably heard that standard answers of remove impediments, champion the process, shields the team from outside interferences, etc. but I’d like to take it a step forward or maybe sideways.
Scrum Masters are champions for the team, their decisions, their delivery and even their failures. They are constantly looking at how the team operates from both an internal and external lens; one that the team members are very rarely able to use because they are in the thick of things and may not have the objective eye. When a Scrum Master is able to identify things that are impeding the team and help them discover it rather than point a finger, jump up and down and demand they fix it, a bond is developed between the team members that gives them the confidence and trust that someone is looking out for them and is there to help them achieve their next level of expertise.
Eventually, a Scrum Master should find that the team needs their guidance less and less over time. There are a few exceptions to that. Teams that are dispersed teams that gain new team members, teams that experience growth and then split (scaling scrum) will need more time and attention from their Scrum Master during these times. They may have been experts at their process and become self managing but anytime the dynamic changes, there will be more to talk about, more to decide on and generally shakes the team for a time.
Another thing to note is that Scrum Masters are not Project Managers or even Tech Managers in their primary role. There is a tendency to do this and it’s a dangerous thing because it can taint decisions and imply a level of power and control that should be absent from a Scrum Master. Members of a scrum team should continue to rely on their managers and peers to improve their level of skill and professional growth whereas a Scrum Master may notice and relay recommendations about team members to their manager as a way of keeping the health of the team and growth of the team moving in a positive direction.
Hope this helps some of you!