Impediment
Any obstacle that slows or blocks a Scrum Team's progress toward its Sprint Goal, which the Scrum Master helps remove.
What it means
Impediments range from technical blockers, like a broken build, to organizational ones, like unavailable stakeholders or conflicting priorities from outside the team.
The Developers themselves resolve impediments they can control; the Scrum Master focuses on impediments that require organizational influence beyond the team's authority.
Common mistakes
Impediments raised at the Daily Scrum but not resolved quickly should be tracked visibly so they do not silently recur Sprint after Sprint.
Example
A shared staging environment is unavailable for two days; the Scrum Master escalates to the infrastructure team to restore access.
Types of impediment
- Technical, such as a broken build, a flaky test suite or an environment nobody can deploy to
- Team level, such as a missing skill, an unclear Sprint Goal or work that was never refined
- Organizational, such as a sign off that takes two weeks, a shared specialist who belongs to four teams, or conflicting priorities arriving from outside
- External, such as a vendor who misses a date or a compliance review with no fixed queue
Agile impediments versus normal friction
Not everything uncomfortable is an impediment. A disagreement inside the team is usually the work, not a blocker. A slow decision becomes an impediment only when the delay is now costing the Sprint Goal. The test is simple: name the progress being lost and name who can restore it. If the team can restore it themselves, they should.
How to remove an impediment
- Write it where the team can see it, with the date it appeared and the effect it is having
- Let the Developers clear what sits inside their control, so the Scrum Master is not the single route to every fix
- Take organizational impediments to the person who owns the constraint, with the cost expressed in delivery terms rather than complaint terms
- Review the list at the Retrospective and look for the same impediment appearing a third time, because repeats are a system problem rather than an incident