How do you handle removing impediments as a Scrum Master?

Question

Accepted Answer

An impediment is **anything slowing the team that the team cannot easily resolve itself**. The Scrum Master's job is to make impediments visible, decide who is best placed to remove each one, and follow through — coaching the team to clear small ones on its own.

## A simple workflow

```text
1. SURFACE   capture impediments (standup, board, retro)
2. TRIAGE    team-solvable? coach them. Org-level? escalate.
3. OWN       assign an owner and a next action with a date
4. TRACK     keep an impediment log; review until cleared
5. PREVENT   feed recurring blockers into the Retrospective
```

## Concrete example

A team is blocked because access to a third-party API takes the security team two weeks. The Scrum Master escalates to the engineering manager, negotiates a fast-track, and meanwhile helps the team reorder work to stay productive.

## Common pitfalls

- Solving everything yourself, so the team never learns to unblock itself.
- Tracking blockers nowhere, so they quietly recur every Sprint.
- Escalating trivial issues the team could handle, eroding your credibility.

## Why it matters

Impediment removal is one of the most concrete ways a Scrum Master adds value — it directly protects the Sprint Goal and the team's flow.

Distinguishing what to coach from what to escalate is the skill: it builds team capability while still clearing organizational blockers fast.