The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better. Show
In a series of blog posts I will share the different stances I consider to be relevant for the Scrum Master. This blog post is about the Scrum Master as an impediment remover. I'll describe the most common definitions and examples of an impediment, the Scrum Master as an impediment remover and tactics to deal with impediments. Earlier blog posts in this series are:
What is an Impediment?By doing a bit of research I've found quite a few good definitions:
Some nice quotes about impediments are:
Examples of Possible ImpedimentsNow that you've read the most common definitions of an impediment, you probably want some tangible examples. Therefore you'll find some examples of possible impediments below
The Scrum Master as an Impediment RemoverAccording to the Scrum Guide one of the Scrum Master services to the Development Team is removing impediments to the Development Team's progress. As a servant leader, the Scrum Master guides the Development Team towards self-organization and cross-functionality. The Scrum Master encourages, supports and enables the team to reach their full potential and abilities. To achieve all this, the Scrum Master should make conscious decisions about removing impediments. Questions to consider are:
It's important to realize that the given examples of possible impediments don't have to be impediments. Something will only become an impediment when it exceeds the self-organizing capabilities of the team. Scarcity of skills might be become an impediment, but trust the self-organizing character of the Development Team to think off other options themselves. Maybe a team member is eager to learn the desired skills and sees this as a great opportunity. Also a conflict between team members doesn't have to be an impediment. Let them have an intense discussion with each other. It's up to the Scrum Master to lead the team through healthy conflict and debate. Eventually this will lead to an even stronger team. A Scrum Master should create an environment where the Development Team feels safe to raise impediments. Respecting the self-organizing capabilities of the team, the Scrum Master should encourage the team in trying to solve their own problems. Or even better, preventing something to become an impediment at all. Tactics for Removing ImpedimentsRemoving impediments can be a challenge. Below I've shared some tactics and ideas that a Scrum Master can consider when facing impediments.
ConclusionBy doing some research and thinking of my own I've created a brief description of the Scrum Master as an Impediment Remover. Given the amount of available material, it's clearly an important part of the Scrum Masters role. My main lesson learned is to respect the self-organizing capabilities of the Development Team. Considering every minor issue an impediment that needs to be resolved by the Scrum Master, doesn't help the Development Team grow as a whole. It's about continuously finding the right balance between preventing or fighting a fire. Who is responsible for removing impediments from the team?The Scrum Master's main responsibility is to identify, track and help remove impediments. Often, team members remove their own impediments. Sometimes, Impediments are beyond the ability of the Team to remove. In that case, the Scrum Master may have to get support from outside of the Team.
Who is responsible for tracking project impediments?Examples of Scrum impediments are listed in Table 1. The Scrum Master is responsible for tracking, monitoring and ensuring that impediments are removed. All Scrum Team members are responsible for continually identifying impediments for discussion during the Daily Standup Meeting.
Who is responsible for removing a Scrum team?The Scrum answer would be that the Scrum Team is responsible. The Scrum Guide says that Scrum Teams are self-managing, which means that "they internally decide who does what, when, and how".
Who is responsible for maintaining the teams Definition of Done?The Development Team defines the definition of "Done".
|