Work-in-Progress (WIP) Limits in Kanban and Production Planning

Learn how WIP limits work in Kanban and production planning: cap active jobs, find bottlenecks, shorten cycle time and keep a detailing workflow moving.

9 min read0 views
— · 0 votes
Contents
  1. What a WIP limit actually is
  2. How limits work on a kanban board
  3. WIP limits in production planning
  4. Agile and Scrum: where limits fit
  5. The math behind the cap: Little's law
  6. Using limits to find bottlenecks
  7. Setting and adjusting the numbers
  8. Limits on a detailing job board
  9. Questions about WIP limits
  10. What does a work in progress (WIP) limit do in Kanban?
  11. How do work in progress limits help production planning?
  12. Do Scrum teams use work in progress limits?
  13. What is the German term for a work in progress limit?
  14. How does Little's law relate to a WIP cap?
  15. How do you choose the first WIP limit for a stage?

A work-in-progress limit is a cap on how many jobs may sit in one stage of a workflow at the same time. In Kanban and production planning, that cap forces the team to finish started work before pulling new work in. The result is a steadier flow, visible bottlenecks and fewer half-done vehicles or orders.

  • A WIP limit sets a number on each stage of the board, and no new job enters until a slot frees up.
  • Stopping starting and focusing on finishing is the behavior a limit enforces.
  • Little's law ties the amount of work in progress to cycle time and throughput.
  • A full column is information, not failure: it shows where the flow is blocked.
  • Limits work only when the team agrees on them and respects them under pressure.

What a WIP limit actually is

A work-in-progress cap is a fixed number of items allowed to be active in a workflow stage at one time. The Kanban method treats that number as a rule of the board rather than a suggestion. Each column or lane carries its own limit, so the cap applies where the work is done.

A WIP limit is not a target for output and not a measure of busyness. The cap constrains the amount of started work so that finishing becomes the priority. Started jobs that sit idle still consume capacity, and the limit keeps that idle work visible.

The German term for the concept is Work-in-Progress-Limit, and the term is used in that form in German-language lean material. The idea stays the same across languages: a number that blocks new intake. Teams write the number directly on the column so nobody has to remember it.

How limits work on a kanban board

Column limits on a kanban board show the cap beside each stage heading, such as a number in brackets after the column name. A job moves right only when the next column has a free slot. When a column is full, the team works on what is already there instead of pulling more.

Kanban WIP limits turn a board into a pull system. Work is pulled into a stage when capacity opens, not pushed forward by an upstream schedule. The board therefore shows the real constraint instead of hiding it behind optimistic planning.

A blocked column is a signal to investigate rather than a reason to raise the number. The team asks which task is stuck, why it is stuck and who can unblock it. Moving a job backward or splitting it can restore flow without breaking the cap.

  • Write the limit next to each column heading so it is visible to everyone.
  • Move a job right only when the receiving column has a free slot.
  • Treat a full column as a prompt to swarm on the blocked item.
  • Review limits when the workflow changes, not when a column feels busy.
  • Keep the number of active jobs per person visible as well as per column.

WIP limits in production planning

WIP limit production planning uses the cap to control how much material or work sits between process steps. Released orders are held back until the shop floor has room to absorb them. This protects the constraint from being buried under queued work.

Lean manufacturing treats excess work in progress as a waste that hides problems. Large queues stretch lead times and make defects harder to spot. A limit on queue size forces problems to surface while they are still small.

Planners pair the limit with a pull signal, so a new order is released only when a downstream slot frees. The scheduling rule then follows the constraint rather than the forecast. Capacity decisions rest on the real pace of the slowest step.

Agile and Scrum: where limits fit

Work in progress limits agile teams apply at the task level, often as a cap per person or per workflow state. The cap keeps a team from opening five tasks and finishing none. Scrum work in progress gets the same treatment on the sprint board.

Scrum does not prescribe a WIP limit in its framework, and teams add one as a working agreement. The sprint goal then guides what gets started, and the limit decides how much can be open at once. A team that respects the cap tends to finish more of what it commits to.

Agile coaches describe the practice as stopping starting and focusing on finishing. The phrase captures the shift from parallel effort to completed work. A team that finishes items early also frees capacity for the next pull.

The math behind the cap: Little's law

Little's law states that average cycle time equals the amount of work in progress divided by throughput. Raising the cap raises the amount started and stretches the time each job spends in the system. Lowering the cap shortens cycle time when throughput holds steady.

Cycle time measures how long one item takes from start to finish, and throughput counts how many items finish in a period. Flow efficiency compares the time spent actively working with the total time in the system. Waiting time is the gap that a smaller cap exposes.

The law gives planners a way to reason about a limit without inventing numbers. If throughput is fixed, the cap sets the waiting time the team should expect. A team that wants faster delivery reduces the work in progress rather than pushing harder.

Using limits to find bottlenecks

Bottleneck identification starts where the queue grows despite a limit in place. A stage that stays full while upstream stages wait is the constraint of the workflow. The cap makes that imbalance obvious because work piles up in one place.

The constraint dictates the pace of the whole system, so effort spent elsewhere adds to the queue. A detailer waiting on a drying bay shows the same pattern as a machine waiting on a tool. The limit directs attention to the slow step instead of the busy one.

Relieving the bottleneck may mean adding capacity, changing the sequence or moving work out of the constrained stage. A trained specialist should handle any change that affects equipment, electrical work or vehicle safety systems. The team then watches whether the queue shifts and adjusts the limit.

Setting and adjusting the numbers

A starting limit follows from the capacity of the stage and the work each item needs. The team counts how many jobs can be active without creating a queue at the next step. The first number is a hypothesis to test, not a permanent rule.

Watch the flow for a period that reflects the real variation in the work, then compare cycle time with the queue size. If a column is always full and the next step waits, the cap is too high for that stage. If people sit idle with a free column, the cap is too low.

Change one limit at a time so the effect is readable. Record the reason for the change and the result, so the team learns from it. Limits belong to the workflow and should move when the process moves.

SituationLikely causeAction
Column always full, next step waitsCap too high for the stageLower the cap or add capacity
People idle, column has free slotsCap too low or intake too slowRaise the cap or check the pull signal
Job stuck in one column for longLocal bottleneckInspect that step and unblock the item
Queues grow before one stage onlyConstraint at that stageFocus improvement there first

Limits on a detailing job board

Detailing job board WIP keeps the shop from accepting more vehicles than the bays and staff can process. Each stage, from wash to correction to final inspection, holds a set number of cars. A full correction column means no new car enters that stage until one leaves.

The cap protects the quality of each step because a crowded bay invites rushed work. It also keeps equipment from being tied up by jobs that cannot proceed. A car waiting on a part or a cure time occupies a slot and blocks the next pull.

The same discipline applies to the tools and the checklist for each job. A board that shows the limit and the checklist together keeps the workflow honest. The shop finishes cars in order instead of spreading effort across too many at once.

Questions about WIP limits

What does a work in progress (WIP) limit do in Kanban?

A work in progress limit in Kanban caps how many items may be active in a stage at one time. It blocks new work from entering until a slot frees, so the team finishes started items first. The cap makes queues and bottlenecks visible on the board.

How do work in progress limits help production planning?

Work in progress limits help production planning by controlling how much work is released to the shop floor. Released orders wait until a downstream stage has room to absorb them. This keeps the constraint from being buried under queued work and shortens lead times.

Do Scrum teams use work in progress limits?

Scrum teams can use work in progress limits as a working agreement even though Scrum does not require them. A cap per person or per board state keeps the sprint focused on finishing. The sprint goal then guides which items get started.

What is the German term for a work in progress limit?

The German term is Work-in-Progress-Limit, and German lean material also refers to the same idea as a limit on work in progress. The concept does not change with the language. The number still caps how much started work sits in a stage.

How does Little's law relate to a WIP cap?

Little's law links average cycle time to work in progress and throughput. With throughput steady, a higher cap lengthens the time each item spends in the system. A lower cap shortens cycle time by reducing the queue.

How do you choose the first WIP limit for a stage?

Choose the first WIP limit from the capacity of the stage and the work each item needs. Count how many jobs can be active without building a queue at the next step. Treat that number as a hypothesis, then adjust it as the flow data arrives.

Latest articles