The Scrum Master is neither a project manager nor a team lead but a servant leader who supports the team in applying Scrum and removes impediments from their path. The role aims to foster the team’s self-organization, not to make decisions on the team’s behalf. Particularly during the introduction of Scrum, an experienced Scrum Master is critical because the framework only works when its principles are understood and lived.
In concrete terms, a good Scrum Master recognizes, for example, that a team is blocked by a dependency on another team and independently organizes a cross-team meeting to resolve the issue. They ensure that Scrum events fulfill their purpose rather than becoming empty rituals. They protect the team from scope changes during the Sprint and coach the Product Owner on backlog management. At the same time, they work at the organizational level to remove structural impediments.
The role is defined in the Scrum Guide and influenced by the concept of Servant Leadership that Robert Greenleaf articulated in 1970. A common mistake in practice is reducing the role to mere meeting facilitation.
Apply methods, don't just know them. View trainings and workshops
