What is Impediment Removal
An impediment is anything that prevents a team from completing their work. In Scrum@Scale, impediments that cannot be resolved at the team level are escalated — first to the Scrum of Scrums Master (SoSM), and if needed, to the Executive Action Team (EAT). These teams are accountable for removing impediments that fall outside a single team's control.
In Scrum, the Scrum Master is accountable for removing impediments the team cannot resolve on its own. In Scrum@Scale, this accountability extends through the Scrum Master Cycle:
- The Scrum of Scrums Master (SoSM) removes cross-team impediments
- The Executive Action Team (EAT) removes organizational impediments
These layers ensure that problems are addressed at the right level of the system, enabling flow across a network of teams.
Why It Matters
Unresolved impediments slow delivery, reduce team effectiveness, and increase the cost of work over time. The longer an impediment remains in place, the greater its impact on the organization.
When impediments persist:
- Delivery slows
- Costs increase
- Transparency decreases
- Teams lose focus on the Sprint Goal
In an empirical system like Scrum, unresolved impediments reduce the ability to inspect and adapt effectively.
But escalation alone is not enough.
A poorly defined impediment is indistinguishable from noise. If the SoSM or EAT lacks context, they cannot act decisively. The result is predictable: delays, rework, and frustration.
Clarity is what enables action.
How It Works in Scrum
Impediments are treated as backlog items for the SoSM and EAT. Like any backlog item, they require enough context for the team to understand the work involved and prioritize accordingly.
At scale, impediments are treated as backlog items. Just like Product Backlog Items:
- They must be visible
- They must be understood
- They must be prioritized
The SoSM and EAT each maintain a backlog of impediments and organizational improvements, inspecting and adapting daily to improve system performance.
A Practical Pattern: The Five Whats
To ensure impediments are actionable, Scrum Inc. uses a simple intake pattern: The Five Whats.
This structure enforces clarity, reduces back-and-forth, and enables faster resolution.
Basic Information (Make It Actionable)
- Point of Contact — Who can clarify the issue
- Team(s) — Who is impacted
- Product Area — What value stream is affected
- Date Raised — Enables measurement of resolution time
This creates ownership, traceability, and a feedback loop for continuous improvement.
The Five Whats (Make It Understandable)
- What are you trying to do? Establishes context. Without this, the impediment has no meaning.
- What is in your way? Defines the actual constraint.
- What is the impact if unresolved? Quantifies cost of delay and informs prioritization.
- What have you tried already? Prevents duplication and accelerates problem solving.
- What does an ideal resolution look like? Treats the team as the customer and aligns the solution to their needs.
Common Mistakes
- Surfacing an impediment without context. Stating a problem without explaining the work it blocks, or the cost of delay, makes it difficult for the SoSM or EAT to act.
- Skipping the work context. Without work context, the impediment lacks meaning for the team responsible for removing it.
- Not tracking resolution time. Date raised should be used to measure how quickly impediments are cleared; this data supports continuous improvement.
- Treating escalation as the solution. Escalation is a handoff. Removal is the outcome.
Key Takeaways
- Only impediments that cannot be resolved at the team level must be escalated to the SoSM or EAT
- The SoSM and EAT operate from impediment backlogs, not ad hoc requests
- Escalation without context slows the system
- The Five Whats template provides a consistent structure for surfacing impediments with the information needed to resolve them
- Impediments should be tracked as backlog items, with resolution speed used as a metric
- The template can be integrated into tools like Google Forms to streamline intake and backlog population