Strengthen backlog refinement, so work is ready before it starts.
Improve production stability (fewer bugs/incidents driving surprise work).
Introduce WIP limits to avoid over commitment.
Create clear policies: what interrupts the team vs what waits. Which can be a political minefield.
Introduce roles like a rotating “on-call” or “expediter” - we had a support person per week who worked on lower level items that could be dropped if needed.
Reduce context switching (a major hidden cost)
The biggest shift: stop treating these percentages as a people problem.
AKA W. Edwards Deming - most issues are caused by the system, not the individuals.
@afuerstenau Scrum Master answer #1 "It Depends" 😜
It depends on the level of work and types of work, so @gdinwiddie picure is a good one.
If planned work is only 40%, your system is overloading the team
Fixes include:
More realistic forecasting
Explicit capacity allocation (e.g., reserving space for unplanned work)
Better stakeholder expectation management
And if you have time to take on other things, nice one, and readjust the forecast for the next time.