Get All Materials From Our Trainings — For Free
Тренинги, Курсы, Обучение — Agile, Scrum, OKR
Тренинги, Курсы, Обучение — Agile, Scrum, OKR
Тренинги, Курсы, Обучение — Agile, Scrum, OKR
31 October, 2022 г.
1 отзыв, в среднем 5 из 5

How to set Kanban WiP limits / Work in Progress?

Kanban WIP limits are a way to manage work-in-progress (WIP) in a Lean/Agile process. WIP is the number of tasks that are actively…

How to set Kanban WiP limits / Work in Progress?

Kanban WIP limits are a way to manage work-in-progress (WIP) in a Lean/Agile process. WIP is the number of tasks that are actively being worked on at any given time by workers.

As a general rule, you want to keep your WIP low because it helps reduce bottlenecks, which can cause problems like delays and lost focus. However, there are times when it's OK to allow more work in progress than usual—for example, when you're waiting for results from a different project.

The limit for the Work in Progress (WiP) is a value that helps you define how many tasks should be handled by your team at any given time. If you don’t set a WiP limit, then your team will not know when to stop working on new tasks and start focusing on the ones that are more important.

Setting WIP limits is a great way to help you manage your workflow. Setting them too low will slow down your team, but setting them too high could lead to a bottleneck in your process. Here's how to set WIP limits in Kanban.

There are two types of WiP limits:

  1. Time-based limits — when you set a particular date and time for your team to finish a certain amount of work. For example, one week from this moment, we want you to finish 100 tasks.

  2. Quantity-based limits — when you tell your team that they need to complete X number of tasks before they can start working on Y number of new ones. For example, we want you to complete 150 tasks before starting any new projects or features.