Что такое Scrum Master?

Scrum Master Role

Scrum Master is a key role in Scrum methodology that is often confused with Project Manager, but they are very different roles.

Definition

A Scrum Master is a servant leader who facilitates the Scrum process and removes obstacles (blockers) that prevent the team from achieving their goals. The Scrum Master does not manage the team, but serves it.

Main Responsibilities

1. Facilitation of Ceremonies

• Sprint Planning: determining what work will be done in the sprint
• Daily Standup: 15-minute synchronization meetings
• Sprint Review: demonstration of completed work to stakeholders
• Sprint Retrospective: analysis of what went well and what can be improved
• Backlog Refinement: preparing stories for upcoming sprints

2. Removing Blockers This is the most important responsibility. When the team is blocked:

• If a developer is waiting for product feedback, the SM gets the product manager
• If there is no access to production server, the SM gets access from DevOps
• If a task depends on another team, the SM coordinates across teams

3. Coaching

• Teaching the team how to use Scrum correctly
• Coaching on Agile principles and values
• Conducting workshops on estimation, definition of done, etc.

4. Protecting the Team

• Protection from unnecessary interruptions
• Protection from scope creep
• When a CEO wants to add urgent features mid-sprint, the SM explains why this breaks the sprint

5. Metrics and Process Improvement

• Tracking team velocity
• Analyzing burndown charts
• Identifying trends and recommending improvements

Scrum Master vs Project Manager

This is a critical distinction that people often confuse:

Project Manager manages scope, schedule, and budget. They are accountable for project results and have hierarchical authority.

Scrum Master facilitates the Scrum process as a servant leader. They have no hierarchical authority and focus on helping the team self-organize.

In my experience, I often combined both roles, but it is important to understand the difference.

Practical Example

One team was blocked because they needed access to an API from a third-party provider. I, as Scrum Master, contacted the provider, obtained credentials, and delivered the information to the team. This is classic Scrum Master work: removing a blocker.

Key Mindset

A good Scrum Master is a servant leader who listens to team feedback and adapts the process accordingly. If the team can function without the Scrum Master, then the SM has done excellent work by teaching the team independence.