1 Minute: 3 types of Scrum Masters

Scrum is a framework for managing software development. It is designed for teams of three to nine developers (I recommend 5–7) who break their work into actions that can be completed within fixed duration cycles (called “sprints”), track progress and re-plan in daily 15-minute stand-up meetings, and collaborate to deliver working software every sprint.

We have 3 Roles in Scrum: Product Owner, Scrum Master, and the Development Team (see picture above).

The 3 types of Scrum Masters:

Good

This is a servant-leader and facilitator, 100% totally dedicated to making sure that the Team lives with the values, principles, and practices of scrum. The Scrum Masterdoes anything possible to help the team perform at their highest level. This involves removing any impediments to progress, facilitating meetings, protect the team from interferences and doing things like working with the product owner to make sure the game backlog is in good shape and ready for the next sprint.

Ugly

He is a Scrum Master + Developer = It’s not dedicated so he, not performing well in both roles.

Bad

He is a Scrum master + PO = He acts as a Boss, as a leader, and as a manager, likes to command not to serve. One of the ways the scrum master role differs from a project manager is that the latter may have people management responsibilities and the scrum master does not. Scrum does not formally recognize the role of project manager, as traditional command and control tendencies would cause difficulties.