Battlecard: WIP Limits Slow Us Down
Respond to WIP-limit objections using flow, Sprint Goal, and evidence-based improvement language.
The team is adding WIP limits to a Scrum board and someone argues that limits will slow people down. WIP limits just make people wait. We need everyone coding if we want to finish the sprint. I do not want idle people either. I want fewer idle cards. Let's test a limit for one sprint: when Review reaches two, we stop starting and help finish. At retro we inspect review age, Done items, and defects returned. If flow gets worse, we change the policy. The response acknowledges the productivity concern, shifts the unit of optimization from individual busyness to value…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in