Scrum Master Roles and Responsibilities

Quick answer

A Scrum Master is responsible for establishing Scrum and for the Scrum Team's effectiveness, which the Scrum Guide breaks into services to three groups: the Scrum Team, the Product Owner and the organisation. For the team, you coach self-management, remove impediments and make sure events are useful and timeboxed. For the Product Owner, you help with Product Goal and backlog techniques. For the organisation, you lead and coach Scrum adoption and remove barriers between stakeholders and teams.

• Team: coaching, impediment removal, effective events, focus on Done Increments
• Product Owner: backlog techniques, clear backlog items, empirical planning
• Organisation: training, coaching and removing barriers to Scrum
• Daily work: facilitation, follow-ups, coaching conversations, process improvement
• Not your job: assigning tasks, owning scope or acting as the team's boss

Key takeaways

1. The Scrum Guide 2020 makes the Scrum Master accountable for establishing Scrum and for the Scrum Team's effectiveness (Scrum Guide, October 2026).
2. Your responsibilities fall into three groups: the Scrum Team, the Product Owner and the organisation.
3. In each event, you make sure it happens, stays positive and productive, and stays within its timebox.
4. Metrics such as velocity, burndown and cycle time are tools for team learning, not targets for managers.
5. As you become more senior, your focus moves from one team to many teams and then to the organisation.

1. Scrum Master responsibilities at a glance

Short answer: You are accountable for how well the team uses Scrum and how effective it becomes, and you deliver that through coaching, facilitation, impediment removal and organisational change.

The Scrum Guide (Scrum Guide 2020, checked October 2026) is the official definition of Scrum. It describes three accountabilities in a Scrum Team: Developers, the Product Owner and the Scrum Master. A Scrum Team is typically 10 or fewer people.

The Scrum Master is accountable for two big outcomes:

• Establishing Scrum by helping everyone understand Scrum theory and practice, inside the team and across the organisation.
• The Scrum Team's effectiveness by enabling the team to improve its practices within the Scrum framework.

Here is a one-table summary of the responsibilities you will read about below.

If you are completely new to the role, read our simple guide to what a Scrum Master is first.

2. Responsibilities to the Scrum Team

Short answer: You coach the team to manage itself, keep it focused on valuable Done work, get blockers removed and make sure every event is worth the time.

The Scrum Guide 2020 lists four services to the Scrum Team. Here is each one with what it means in practice.

Coaching self-management and cross-functionality

The guide expects the team to decide who does what, when and how. Many teams in India come from a command-and-control culture where a lead hands out tasks. Your job is to coach them out of that habit.

In practice, you:

• Ask the team to pull work from the Sprint Backlog instead of waiting for assignments.
• Encourage people to learn skills outside their speciality, such as a developer helping with testing.
• Step back from decisions the team should make itself.

Focusing on high-value Increments that meet the Definition of Done

A Sprint is only successful when it produces a usable Increment that meets the Definition of Done. You help the team avoid "90% done" work.

In practice, you:

• Help the team create and improve its Definition of Done.
• Point out when work is being started but not finished.
• Help the team keep the Sprint Goal visible all Sprint.

Causing the removal of impediments

An impediment is anything that slows the team and that the team cannot easily fix on its own. Note the guide's wording: you cause the removal. You do not have to fix everything personally, but you make sure the right person does.

In practice, you:

• Keep a visible impediment list.
• Follow up the same day on blockers raised in the Daily Scrum.
• Escalate organisational blockers, such as slow approvals or missing environments, to people who can fix them.

Making sure events happen and are useful

You make sure all Scrum events take place and are positive, productive and kept within the timebox. This is the most visible part of your job. Section 5 explains your duties in each event.

3. Responsibilities to the Product Owner

Short answer: You help the Product Owner with techniques for the Product Goal and the backlog, help the team see why clear backlog items matter, support empirical planning and bring stakeholders together when needed.

The Product Owner is accountable for maximising product value and managing the Product Backlog. You do not take over that accountability. You support it.

According to the Scrum Guide 2020, you serve the Product Owner by:

• Finding techniques for defining the Product Goal and managing the Product Backlog well, for example story mapping or impact mapping.
• Helping the Scrum Team understand the need for clear and concise Product Backlog items.
• Helping establish empirical product planning for a complex environment, where plans change as you learn.
• Facilitating stakeholder collaboration as requested or needed.

What this looks like day to day

• Running or facilitating backlog refinement sessions.
• Coaching the Product Owner to write a clear Product Goal and connect each Sprint Goal to it.
• Helping the Product Owner say no, or not now, to stakeholders when the backlog is overloaded.
• Showing the Product Owner how forecasts based on real team data are more reliable than fixed promises.

The Product Owner and the Scrum Master are separate accountabilities. Our guide to Scrum Master vs Product Owner explains how the two work together.

4. Responsibilities to the organisation

Short answer: You lead, train and coach the organisation in Scrum, advise on how to implement it, help people work empirically and remove barriers between stakeholders and teams.

The Scrum Guide 2020 lists four services to the organisation:

• Leading, training and coaching the organisation in its Scrum adoption.
• Planning and advising Scrum implementations within the organisation.
• Helping employees and stakeholders understand and enact an empirical approach for complex work.
• Removing barriers between stakeholders and Scrum Teams.

What this looks like day to day

• Running a short Scrum introduction for a new stakeholder group.
• Explaining to a senior manager why changing the Sprint Goal every few days hurts delivery.
• Working with other Scrum Masters to reduce dependencies between teams.
• Advising HR or leadership when performance reviews reward individual heroics over teamwork.

This part of the job grows as you become more senior. In large enterprises that use the Scaled Agile Framework, Scrum Masters also work within a wider team-of-teams structure. Scaled Agile describes its SAFe Scrum Master certification as a foundational course for people new to SAFe (Scaled Agile, October 2026).

5. Scrum Master duties in each Scrum event

Short answer: In every event, you make sure it happens, it has a clear purpose, everyone can contribute and it stays inside its timebox, while gradually coaching the team to run it themselves.

Timeboxes below are for a one-month Sprint, from the Scrum Guide 2020. For shorter Sprints, events are usually shorter.

The Sprint

• Help the team protect the Sprint Goal from mid-Sprint scope changes.
• Make sure the Product Owner and stakeholders understand that only the Product Owner can cancel a Sprint, and only if the Sprint Goal becomes obsolete.

Sprint Planning

• Make sure the Product Owner comes with a clear idea of how the product can increase its value.
• Help the team agree on a Sprint Goal, select work and plan how to deliver it.
• Watch for over-commitment and remind the team of its real capacity.

Daily Scrum

• The Daily Scrum is for the Developers. You make sure it happens and stays within 15 minutes.
• Coach the team to focus on progress toward the Sprint Goal, not on reporting to you.
• Take detailed problem-solving offline so the event stays short.

Sprint Review

• Help the team show working product, not slides.
• Make sure stakeholders give real feedback and that the Product Backlog is adapted.
• Keep the event collaborative rather than a one-way demo.

Sprint Retrospective

• Create a safe space for honest discussion.
• Vary formats so the event does not get stale.
• Help the team pick a few concrete improvements and follow up on them in the next Sprint.

Backlog refinement

Refinement is an ongoing activity, not a formal event. You help the Product Owner and Developers keep enough clear, sized items ready for the next Sprint or two.

6. Day-to-day tasks of a Scrum Master

Short answer: Your days mix the Daily Scrum, blocker follow-ups, refinement, coaching conversations, stakeholder talks and preparation for upcoming events.

Here is an illustrative timeline for a two-week Sprint. Exact timing varies by company.

Common recurring tasks

• Keeping Jira or Azure Boards tidy and transparent, without becoming the team's data clerk.
• Writing short notes after Retrospectives and tracking agreed actions.
• Onboarding new team members to the team's way of working.
• Meeting your manager or Agile Coach to discuss team health.
• Running one-to-one coaching conversations.

For the tools that support these tasks, read our guide to Scrum Master tools.

7. Responsibilities by seniority

Short answer: Junior Scrum Masters focus on running events well for one team, mid-level Scrum Masters coach teams to self-manage, senior Scrum Masters work across teams and with leadership, and Agile Coaches shape the whole organisation.

Pay grows with scope

AmbitionBox reports these averages for India (all October 2026):

• Scrum Master: ₹17.4 lakh a year, based on professionals with 5 to 14 years of experience.
• Senior Scrum Master: ₹25.4 lakh a year, based on 7 to 17 years of experience.
• Agile Coach: ₹29.3 lakh a year, based on 10 to 20 years of experience.

The jump in pay follows the jump in responsibility: from one team, to many teams, to the organisation.

8. Metrics a Scrum Master tracks

Short answer: Common metrics are velocity, Sprint burndown, release burnup, cycle time, lead time, Sprint Goal success and team health, used to help the team learn rather than to judge it.

The Scrum Guide does not prescribe metrics. It asks for transparency and empirical decisions. Metrics help with both, as long as the team owns them.

Rules for using metrics

• Do not turn velocity into a target. Teams can inflate estimates to look better, which destroys its value.
• Look at trends, not single Sprints. One bad Sprint is a data point, not a crisis.
• Share metrics with the team first. Metrics should spark questions in the Retrospective.
• Combine numbers with conversations. A falling burndown line does not tell you why.

9. What a Scrum Master is NOT responsible for

Short answer: You are not the team's manager, task assigner, Product Owner, project manager or note-taker, and you are not personally accountable for delivering the Increment.

Confusion about the role causes many problems in Indian companies. Here is what is outside your accountability under the Scrum Guide.

Grey areas you will meet

• Combined roles. Some companies hire a "Scrum Master cum Project Manager". If you take such a job, be clear with your manager about which duties are which.
• Admin work. You may be asked to book meetings or update reports. Do the minimum needed and coach the team to own its own board.
• Technical decisions. Even if you have a developer background, let the Developers make technical calls.

For how the Scrum Master role differs from a traditional manager, read our comparison of Scrum Master vs Project Manager.

10. Sample Scrum Master job description

Short answer: A good Scrum Master job description covers the purpose of the role, Scrum Guide responsibilities, required experience, skills, tools and certifications.

Use this sample as a template for hiring or as a guide for your own resume. Replace the bracketed details with your own.

Job title: Scrum Master

About the role: We are looking for a Scrum Master to serve (one or two) Scrum Teams building (product or domain). You will help the teams use Scrum well, become self-managing and deliver valuable Increments every Sprint.

Responsibilities:

• Facilitate Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective, keeping each event focused and within its timebox.
• Coach team members in self-management, cross-functionality and Scrum values.
• Identify impediments and cause their removal, escalating where needed.
• Support the Product Owner with Product Backlog management, refinement and a clear Product Goal.
• Help the team define and improve its Definition of Done.
• Track and share team metrics such as velocity, burndown and cycle time to support improvement.
• Work with other Scrum Masters and stakeholders to manage dependencies and remove organisational barriers.
• Promote Scrum and agile ways of working across the organisation.

Requirements:

• (2 to 5) years in an IT delivery role, with at least (1) year as a Scrum Master or in a Scrum Team.
• Strong knowledge of the Scrum Guide and agile principles.
• Excellent facilitation, communication and conflict-handling skills.
• Hands-on experience with Jira and Confluence or similar tools.
• A recognised certification such as CSM, PSM I or SAFe Scrum Master.

Nice to have:

• Experience with scaled frameworks such as SAFe.
• Background as a developer, tester or business analyst.
• Experience working with distributed teams across time zones.

When you write your own resume, turn these duties into achievements with real numbers from your work. Our Scrum Master resume guide shows how.

11. Common challenges in the role

Short answer: The hardest parts of the job are managers who expect status reports, Product Owners who are not available, teams that resist change and doing the role part time.

• "Agile in name only." The company uses Scrum words but keeps old habits. Start small: one event done well builds trust.
• An absent Product Owner. Without one, the backlog goes stale. Raise it early with leadership and show the impact on delivery.
• Pressure to report. Managers may want daily updates. Offer them the Sprint Review and a transparent board instead.
• Resistance from senior developers. Win them over by removing their biggest frustrations first.
• Too many teams. Serving more than two teams usually means you only have time to run events, not to coach.

12. How Brolly Academy helps

Short answer: Brolly Academy's 1-week Scrum Master course in Hyderabad trains you on Scrum roles, events, artifacts, burndown and burnup charts, agile estimation and Jira, so you can take on these responsibilities with confidence.

The Scrum Master training in Hyderabad runs in the classroom and live online. According to the course page (October 2026), it includes:

• 11 modules, including Scrum Roles, Scrum Ceremonies, Scrum Artifacts, Daily Scrum and Sprint Retrospective, Sprint Burndown Chart, Release Burnup Chart, Product Planning, Agile Estimation and Scaling Scrum.
• A 1-week plan that moves from foundations and roles to events and backlog with a capstone project, then Jira and team leadership, then CSM and PSM exam preparation, role plays and mock interviews.
• Tools: Jira, Confluence, Trello, Miro, Asana, Slack, Microsoft Teams, Zoom and Kanban boards.
• Placement support: ATS-friendly resumes, interview question banks, mock interviews and interview scheduling.
• Fees: Video Recording ₹5,000, Online Course ₹10,500 and Classroom Training ₹15,000, with EMI available. Certification exam fees are separate.

You can attend a free demo class before you decide.

Frequently asked questions