Removing Impediments Fast: A Field Checklist for Scrum Masters

In Scrum, an impediment is anything that is slowing the team down or preventing them from completing their Sprint Goal that the team cannot resolve themselves within the Sprint. The Scrum Master is responsible for identifying impediments and removing them -- or escalating them to someone with the authority to remove them. Impediments that are surfaced but not removed quickly become chronic -- the team stops believing the Scrum Master will act, stops surfacing impediments, and starts working around them instead, creating waste and technical debt.

Checklist Part 1: Identifying Impediments Reliably

1. Ask specifically about impediments at the Daily Scrum. The three questions of the Daily Scrum ('what did I do yesterday?', 'what will I do today?', 'are there any impediments?') often produce silence on the third question because teams learn that impediments are not removed quickly. Consider replacing the third question with 'what is slowing you down?' or 'what do you need that you do not have?' -- which often surfaces impediments that the standard question does not.

2. Keep an impediment register. An impediment register -- a visible list of all open impediments, with owner, date raised, and current status -- makes the impediment backlog visible and creates accountability for removal. In the absence of a visible register, impediments are often forgotten after they are raised.

3. Distinguish impediments from information requests. Not every Daily Scrum concern is an impediment. 'I am not sure how to implement this' is an information request -- the team can resolve it themselves. 'The deployment environment has been unavailable for three days and the infrastructure team has not responded to our tickets' is an impediment that requires Scrum Master action.

Checklist Part 2: Removing Impediments Quickly

1. Act on the same day. Impediments raised in the Daily Scrum should be acted on the same day -- even if the action is only an email to the relevant owner with a request for an update. Waiting until the next Daily Scrum to take action signals that impediments are not urgent.

2. Know your escalation path. Every Scrum Master should know in advance who can resolve the most common impediment types: infrastructure dependencies, external team dependencies, budget or procurement holds, stakeholder decisions, and organisational policy blockers. Knowing the escalation path in advance reduces the time spent figuring it out when an impediment is raised.

3. Make escalations formal when necessary. If an impediment cannot be resolved informally, escalate formally in writing -- an email that names the impediment, describes the impact on the Sprint, and requests a decision by a specific date. Formal written escalations create a record, make the impact visible to senior stakeholders, and set expectations about response time.

Checklist Part 3: Preventing Recurring Impediments

• Review the impediment register at the Sprint Retrospective. Recurring impediments -- those that appear multiple times across Sprints -- are systemic issues, not one-off problems. They should be addressed at the process or organisational level, not managed one occurrence at a time.

• Track the time-to-resolution for impediments. If the average time from when an impediment is raised to when it is resolved is more than two days, the impediment removal process is not working effectively. Use the data to identify where the bottlenecks are.

• Report impediment metrics to the organisation. If the Scrum Master consistently removes impediments quickly, organisational stakeholders rarely see evidence of what they are doing. Reporting on impediment volume, types, resolution time, and escalation path makes the Scrum Master's contribution visible.

XNM provides Scrum coaching and agile delivery advisory to public-sector organisations. Reach out to XNM's program & project delivery advisory team to discuss Scrum implementation and impediment management for your organisation.