From the course: Agile Software Development: Kanban for Developers

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Limit work in progress

Limit work in progress - Trello Tutorial

From the course: Agile Software Development: Kanban for Developers

Start my 1-month free trial

Limit work in progress

- [Instructor] Limiting work in progress is not so much about modifying the Kanban board, as it is about making a decision as a team. If you can't all agree on the amount of work that can be done at a sustainable pace and stick to it in the face of deadlines and managers who might not understand software development, then other Kanban practices won't be much help. I'll harp on this again and again until it becomes a mantra for you. Kanban only works if the whole team commits to it and they're allowed to follow through. The idea behind imposing a limit on work in progress is pretty simple. When you identify an area of your process that routinely bottlenecks with a pileup of work items, set a hard limit for how many are allowed in that column in the future. And it's important not to fall into the trap of thinking that people just aren't working fast enough at a certain step, and that's what's causing the bottleneck. It's much more likely that desired capacity at a certain step is higher…

Contents