Stephen Fells

Scrum Masters are accountable for causing the removal of impediments that slow down or block the Scrum Team. Traditionally, this has meant watching for blockers during Daily Scrums, facilitating discussions with stakeholders and third parties, or helping the team resolve organizational roadblocks. But many impediments are subtle and easy to miss: creeping technical debt, unclear backlog refinement, overloaded communication channels, or even low team morale hidden behind polite silence.

Silence in a Scrum team doesn’t always mean harmony, it might mean disengagement. What if AI could help us hear what’s not being said? Scrum Masters are trained to observe, to listen between the lines, and to foster transparency. But let’s be honest: even the most attentive Scrum Master can miss signals especially in remote teams, large organizations, or cultures where direct feedback feels risky. Retrospectives don’t always surface truth. Anonymous surveys can fall flat.

Sprint Planning is one of the most collaborative events in Scrum, and one of the most misunderstood. When done right, it aligns the team around a shared Sprint Goal, a realistic plan, and clear priorities. When done poorly, it turns into a slog of guessing story points, debating vague backlog items, or nodding along to a plan no one really believes in.