This document will give over view about scrum master roles and benefits, And expected skill level, Common Pitfalls and few other links

1. Definition of Scrum Master
The scrum master is the team role responsible for ensuring the team
lives agile values and principles and follows the processes and practices
that the team agreed they would use.
The responsibilities of this role include:
● Clearing obstacles
● Establishing an environment where the team can be effective
● Addressing team dynamics
● Ensuring a good relationship between the team and product owner
as well as others outside the team
● Protecting the team from outside interruptions and distractions.
The scrum master role was created as part of the Scrum framework.
The name was initially intended to indicate someone who is an expert at
Scrum and can therefore coach others.
The role does not generally have any actual authority. People filling this
role have to lead from a position of influence, often taking a
servant-leadership stance.
Also Known As
Scrum master is typically the term used to refer to this role, even by
teams not explicitly following Scrum. Other terms used infrequently
include iteration manager, agile coach, or team coach.

2. Expected Benefits
The general benefit expected from having a scrum master on a team is
providing a self-organizing team with ongoing access to someone who
has used agile, and scrum in particular in another setting and can help
the team figure out the best way to apply it in their situation.
Another expected benefit is that the scrum master is someone that can
address distractions, disruptions, and obstacles so that the remainder of
the team is free to focus on the work of producing output that will
generate the desired outcome.
Common Pitfalls
While having a scrum master can provide several benefits, there are
also several problems that arise from improper application of the role.
Those problems include:
● Assuming that you can just slide project managers who are used to
command and control type leadership into a scrum master role and
expect them to be effective.
● Asking someone to fill the scrum master role without any
experience working in an agile setting
● Expecting the work load for a scrum master to be the same on
every team irrespective of how long the team has worked together,
their understanding of agile values and principles, and their
experience in the domain. A well functioning team will most likely
need much less coaching from a scrum master than a team new to
working with each other and in agile values and principles
To learn more about scrum master and product owner role & responsibility please click here.

3. Skill Levels
While there are no officially defined levels of skill for scrum masters, in
practice there are different levels of experience:
● Rotating scrum master – members of a team rotate scrum master
responsibilities (primarily the administrative ones) amongst each
other on a sprint by sprint basis
● Part time scrum master – one individual on the team takes on
scrum master responsibilities in addition to other responsibilities on
the same team.
● Full time dedicated scrum master – one individual’s sole
responsibility is as a scrum master for one time. This model is best
suited for a team learning agile
● Full time scrum master with more than one team – this model is
quite frequently applied where an individual’s sole responsibility is
to be a scrum master, but they work with more than one team
● Agile Coach – An individual does not have a specifically assigned
team but works with several teams and only on specific needs.
To learn more about scrum master and product owner role & responsibility please click here.