Blocker vs. Impediment: How do you escalate an impediment?
This tests your proactivity in removing systemic friction. Define a blocker (full stop) vs. an impediment (drag). Explain how you surface impediments in retros, track them in a backlog, and escalate systemic issues to leadership.
What's really being asked
This question assesses your grasp of fundamental Scrum concepts and your maturity as a leader. Interviewers want to see if you can distinguish between a tactical, immediate problem (a blocker) and a systemic, ongoing issue (an impediment). Your answer reveals your proactivity, problem-solving approach, and ability to influence beyond your immediate team. They are testing if you are a firefighter (only handling blockers) or a fire marshal (preventing fires by addressing impediments).
The full answer
A strong answer has two parts. First, clearly define the terms. A blocker is a specific issue stopping work on a task, like waiting for an API key. It's a full stop. An impediment is a broader condition that slows the team down, like chronic scope creep or slow CI/CD pipelines. It's a persistent drag on velocity. Second, describe a clear escalation process for impediments. This involves surfacing them during retrospectives, creating a dedicated impediment backlog to track and prioritize them, and then engaging leadership or other teams to resolve the ones the team cannot fix itself, treating them like small change initiatives.
The mistakes people make
A major red flag is using the terms interchangeably, which shows a superficial understanding of Scrum. Another weak answer is having no distinct process for impediments. Many candidates say they'd "bring it up in standup," but the Daily Scrum is for immediate blockers affecting the Sprint Goal, not for deep, systemic issues. A passive answer like "I'd tell my manager" without describing a process of tracking, prioritizing, and presenting the issue with data is also a sign of a less experienced candidate. A recurring blocker that isn't identified as a systemic impediment is a missed opportunity.
What usually comes next
"Tell me about a time you identified an impediment that the team had been tolerating. How did you get it resolved?" or "How do you decide which impediments to focus on if you have several?" or "What do you do when leadership is the source of the impediment?"
A concrete example
"In a previous role, our team's velocity was consistently 15-20% below forecast. During a retro, we identified that vague requirements from product were causing significant rework. This was an impediment, not a blocker, as work never fully stopped. I created an impediment entry, tracked the time lost to rework for two sprints (about 30 developer-hours), and presented this data to the Head of Product. We agreed to a new 'Definition of Ready' that required clearer acceptance criteria before a story could enter a sprint, which resolved the issue over the next quarter."
Interview question
A team's CI/CD pipeline consistently takes 45 minutes, slowing everyone down daily. What is the most effective first step to address this systemic issue?
- a.Privately ask your manager to fix the pipeline, since it is an infrastructure problem.
- b.Stop all work on new features until the pipeline speed is improved.
- c.Add it to the agenda for the next Sprint Retrospective to discuss its team-wide impact.Correct
- d.Announce it as a blocker in the next Daily Scrum to get immediate help.
Why? this is the answer
This is a systemic impediment, not a blocker for a specific task. The retrospective is the correct forum to surface, discuss, and create a plan to address such team-wide issues. The Daily Scrum is for immediate blockers affecting the Sprint Goal, not for deep, systemic problems.
Just read this? Test yourself on what you have been reading.
Read the original → artisanagility.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles