Removing Impediments and Enabling Improvement
Impediments and Continuous Improvement
An impediment is anything blocking the team's progress or ability to self-manage. The Scrum Master's job is to help identify, prioritize, and remove impediments, escalating those beyond the team's authority. Improvement is continuous and most visibly driven by the Retrospective, which should produce a small number of actionable, owned improvements rather than a long wish list.
Root Cause and Experimentation
Effective improvement uses root-cause analysis (for example, the five whys or a cause-and-effect diagram) and treats changes as experiments with a hypothesis and a check. A trap offers adding more process or more reporting as the fix for a delivery problem; the better answer usually addresses the underlying cause and preserves empiricism.
Metrics That Help
Use metrics that inform adaptation, such as cycle time, flow, and progress toward goals, rather than metrics that punish or compare individuals. Velocity is a planning aid for a single team, not a productivity score for cross-team comparison.
Worked rule of thumb
For any improvement scenario, ask three questions: Is the impediment inside or outside the team's control? What is the root cause rather than the symptom? Is the proposed change an experiment with a way to check it? Answers that satisfy all three are usually correct.
Exam traps
- Removing every impediment for the team can erode self-management; coach where possible.
- Retrospective actions without owners or follow-up rarely count as improvement.
- Cross-team velocity comparison is a classic distractor.