In my previous blog post, I talked about how I believe a Scrum Master should be trying to put him or herself out of a job. Put another way, we should master the art of actively doing nothing. Some agreed; some didn’t. Some thought the language was too strong. Others thought it was just right. However, let’s put the debate aside for the moment and discuss what it means. How can a Scrum Master hand his or her responsibilities to the team? What responsibilities? When should this begin? First, let’s start with why. Why should a Scrum Master want to hand responsibility for the team to the team:
- To allow additional time to address organizational impediments.
- To cultivate an environment where team members are responsible and accountable to one another.
- To minimize the bus factor and create T-shaped people within the team.
As far as when, I think LeSS illustrates it best in this graph. At first, a Scrum Master spends a great deal of time with the team and Product Owner. However, as the team matures, he or she peels away to assist the organization in other ways. To read more about how LeSS views the Scrum Master role, click here and here.