The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide.

As defined in the Scrum Guide, the role of a Scrum Master is responsible for promoting and supporting Scrum, by helping everyone understand Scrum theory, practices, rules, and values.

But in practice, we often see this important role as an "extended" role, an "additional" responsibility, usually played by project managers or any of the senior member of the team who is expected to "make things work". This role is often pushed into a dilemma between the "expectations" (to solve every other problem that the team faces) and "reality" (to take a step back and let the team get empowered to solve their own problems).

While the role includes facilitating a conducive work environment for the Scrum Team, guiding and teaching Scrum practices to everyone involved in the project and clearing impediments for the team, it also includes facing resistence from the teams, management, stakeholders and sometimes, probably of all them put together. The challenges could vary from "Time-boxing the Daily Scrum Meeting to 15 minutes" to "the extent of owing the team's deliverables on a whole".

This session aims to take a realistic look at the usual challenges (and probably any unusual ones too) that the Scrum Masters face and try to understand some best practices centered around this role as an outcome of the discussion.