A team's daily stand-up regularly surfaces blockers, but many of them linger unresolved for days. The scrum master wants a lightweight, visible mechanism to ensure impediments are tracked and actively worked until closed. Which practice best addresses this?

Question

Accepted Answer

Record each impediment in a visible impediment log/board with an owner and status until resolved; . An impediment log or board makes blockers transparent, assigns accountability, and tracks them to closure so they do not disappear after stand-up. Email hides the information, lengthening stand-up violates its time-box, and deferring to the retrospective means impediments block work for the whole sprint before being addressed.

A team's daily stand-up regularly surfaces blockers, but many of them linger unresolved for days. The scrum master wants a lightweight, visible mechanism to ensure impediments are tracked and actively worked until closed. Which practice best addresses this?

More Problem Detection & Resolution challenges