Blocker vs. Impediment: Definitions and Escalation
Tests your grasp of Scrum terms and escalation. A blocker stops work; an impediment slows it. A good answer defines both, then outlines an escalation path for impediments: visualize, quantify impact, and engage leadership.
This tests your practical Scrum knowledge and ability to escalate systemic issues. A great answer first defines a blocker as a full stop (e.g., broken dev environment) and an impediment as a drag on velocity (e.g., chronic scope creep). Then, it outlines a clear escalation process for impediments: 1) surface in a retro, 2) quantify the impact (e.g., "costs us 20 story points/sprint"), 3) propose a solution, and 4) escalate to the right forum with data. A red flag is treating them as synonyms or having a vague plan like 'I'd tell my manager'.
Read the original → artisanagility.com
- #agile
- #scrum
- #process
- #escalation
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.