Impediment Management in Scrum: How Scrum Masters Remove Obstacles
An impediment is anything that makes it harder for the Scrum Team to make progress toward its goals.
Impediments can be technical, organizational, process-related or caused by external dependencies.
What Is an Impediment?
An impediment is an obstacle that interferes with the team's ability to work effectively and deliver value.
Examples include:
- Blocked access to a required system.
- Dependency on another team.
- Unclear requirements.
- Technical problems.
- Delayed decisions.
- Unavailable environments or tools.
- Organizational policies slowing delivery.
Impediment vs Normal Task
What Is the Scrum Master's Role?
The Scrum Master helps the Scrum Team address impediments and improve the team's ability to work effectively.
This does not mean the Scrum Master must personally solve every problem.
Depending on the situation, the Scrum Master may:
- Facilitate conversations.
- Connect the right people.
- Help escalate organizational problems.
- Improve collaboration.
- Help the team identify the root cause.
Removing an impediment is not always about doing the work yourself. Sometimes the Scrum Master's most valuable action is helping the right people solve the problem.
Simple Example
A Developer needs access to a test environment, but the access request has been waiting for approval for three days.
The Scrum Master can help identify who owns the approval, facilitate communication and make the organizational impediment visible.
The objective is to help the team resume progress, not to become a permanent intermediary for every request.
Types of Impediments
Don't Just Remove the Symptom
A good Scrum Master also looks for recurring patterns.
For example, if the team repeatedly waits for security approval, solving one request may not be enough.
The Scrum Master can help the organization examine why the delay happens repeatedly and whether the process can be improved.
Fixing the immediate impediment is useful. Preventing the same impediment from repeatedly occurring is even more valuable.
How Should Impediments Be Tracked?
Teams may use an impediment list, board marker, Jira item or another visible approach when useful.
Scrum does not prescribe a specific impediment-tracking tool.
The important thing is that significant impediments are visible and receive appropriate attention.
Common Mistakes
Useful Questions for a Scrum Master
- What is preventing progress?
- Who can help resolve it?
- Is this a one-time problem or a recurring pattern?
- What is the impact on the Sprint Goal?
- Can the team resolve it themselves?
- Does the organization need to address the problem?
Key Takeaway
Effective impediment management is not about being the person who fixes everything.
It is about helping the Scrum Team and organization identify, address and learn from obstacles that reduce effectiveness.