Scrum Impediments
An impediment is anything that slows the team or blocks progress toward the Sprint Goal. A broken test server, a delayed approval, and an unclear requirement all qualify. Impediments waste time every day they stay unresolved, so Scrum teams surface them quickly and remove them without delay.
Impediment in Simple Words
Picture a delivery driver with a full truck and a closed bridge. The driver cannot control the bridge. Every hour of waiting costs money and delays customers. A Scrum Team faces the same situation when something outside its control stops the work. The sooner the team reports the closed bridge, the sooner someone finds a new route.
Common Types of Impediments
| Type | Typical Example | Who Usually Helps |
|---|---|---|
| Technical | Test environment crashes every afternoon | Operations team |
| Organizational | Approval takes two weeks | Department manager |
| Knowledge | Nobody understands the old payment module | Expert or trainer |
| Dependency | Another team has not delivered an interface | Both teams and Scrum Masters |
| People | Two members clash over design choices | Scrum Master coaching |
| Product | Requirement changes daily | Product Owner |
Who Owns Impediments
Every team member spots impediments. The Scrum Master takes responsibility for helping remove them. A good Scrum Master solves what the team can fix on its own and escalates the rest to the right person. The Scrum Master never hides a problem, and never solves a team's problem in secret.
Impediment Handling Flow
Team member notices a blocker
│
▼
Raise it (Daily Scrum or board)
│
▼
Can the team solve it today?
│ │
Yes No
│ │
▼ ▼
Team fixes Scrum Master escalates
│ │
└──────┬───────┘
▼
Track on the impediment list
▼
Confirm resolution, then close
Impediment Board Example
A team building a ticket-booking website keeps a small board beside the main Sprint board. Each card records the blocker, the date, the owner, and the status.
| Blocker | Raised | Owner | Status |
|---|---|---|---|
| No access to payment sandbox | Day 2 | Scrum Master | Waiting for vendor |
| Unclear refund rule | Day 3 | Product Owner | Resolved Day 4 |
| Build takes 40 minutes | Day 4 | Developers | In progress |
The visible list keeps everyone honest. A card that stays open for many days signals that escalation is overdue.
Steps to Manage Impediments Well
- Encourage the team to name blockers in the Daily Scrum without fear.
- Record each blocker with a clear description and an owner.
- Ask what the blocker costs in hours or delayed value.
- Resolve what the team controls within one day.
- Escalate what the team cannot control, and attach the cost estimate.
- Close the card only after the team confirms the problem is gone.
- Review patterns in the Retrospective to prevent repeats.
Warning Signs
- The same blocker appears in Daily Scrums for several days.
- Team members stay silent about delays.
- Work items sit in "waiting" columns without owners.
- The Scrum Master spends more time reporting than removing.
Example: The Missing Access Rights
A new developer joins a team that builds a clinic appointment app. On day one, the developer cannot open the code repository because access has not been granted. The request sits in a queue for three days. The Scrum Master records the impediment, estimates the cost at twenty-four lost hours, and escalates with that number. Access arrives the next morning. In the Retrospective, the team creates a checklist so that future members receive access before their first day.
Preventing Impediments
Many impediments repeat. Teams that study repeated blockers find root causes. A team that waits weeks for environment access might request permanent access. A team that suffers unclear requirements might hold more backlog refinement. Prevention saves more time than constant firefighting.
The Scrum Master's Toolkit
- Facilitation skills that help groups reach decisions
- Relationships across departments
- Data that shows the cost of delay
- Courage to challenge organizational habits
Removing impediments protects the team's momentum. Teams that handle blockers well deliver steadily and enjoy their work more.