Practise the standard verbs for managing a Kanban WIP limit effectively.
0 / 5 completed
1 / 5
Fill in: 'We ___ a strict WIP limit on the in-progress column, rather than letting everyone start work nobody actually finishes.'
We 'enforce a limit' — the standard, simple collocation for applying a Kanban work-in-progress cap. The other options are less idiomatic here.
2 / 5
Fill in: 'Ignoring the WIP limit during a crunch can ___ every task half-finished with nobody actually shipping anything.'
We say an ignored limit will 'leave' every task half-finished — the standard, natural collocation for the resulting thrash. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the WIP limit to the team's actual throughput, rather than a number nobody's actually calibrated against real capacity.'
We 'calibrate a limit' — the standard, simple collocation for tuning WIP caps to real team capacity. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every column against its limit before pulling new work, rather than starting a task nobody's actually confirmed there's room for.'
We 'check a column' — the standard, simple collocation for confirming capacity before pulling new work. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ limit breaches during retro, rather than letting a recurring overload go unaddressed that nobody's actually flagged.'
We 'discuss breaches' — the standard, simple collocation for reviewing WIP limit violations in retro. The other options aren't idiomatic here.