A well designed software systems consists of well designed services, that provide a clear interface and documentation of how to use them. This guide should apply this idea to the Scrum Master Role by considering it as a Service that is available to the Development Team.
The role of a Scrum Master is easily described, but hard to applied in the real world. It’s a role that offers so much diversity. There is a lot to win, but also a lot that can be done wrong. A great Scrum Master is aware of that and knows when and how to apply the right methods, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better. [1]
Scrum Master Services
A Scrum Master is a servant leader, that provides some really valuable services to a development team:
- Scrum Master as Impediment Remover
- 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. [1]
- Scrum Master as a Mentor
- more about this soon
- Scrum Master as a Teacher
- more about this soon
- Scrum Master as a Facilitator
- more about this soon
- Scrum Master as a Coach
- more about this soon
- Scrum Master as a Servant Leader
- more about this soon
- Scrum Master as a Manager
- more about this soon
Where to go from here
Whatever management by numbers will tell you about Scrum Mastership: stay strong, explain them the real values and benefits of a Scrum Master. Maybe this article helps you.
See also Impediment Management as a great resource explaining how managing them will contribute a great valuable impact on the Development Teams performance.
Sources
[1] Scrum.org, https://www.scrum.org/resources/blog/scrum-master-impediment-remover, page viewed at 19.2.2019