Definition
WIP Limit
A WIP (work-in-progress) limit is a cap on how many items may be active in a given workflow stage at once. By forcing a team to finish work before starting more, WIP limits expose bottlenecks, reduce context-switching, and shorten cycle time. They are the core mechanism that makes Kanban flow rather than pile up.
Key takeaways
- A WIP (work-in-progress) limit caps how many items may be active in a workflow stage at once.
- By forcing a team to finish work before starting more, it exposes bottlenecks, cuts context-switching, and shortens cycle time.
- The right limit is found by experiment — start near headcount, then tighten until flow is smooth but no one is idle.
- It's counterintuitive but reliable: limiting how much you start increases how much you finish.
Without a limit, an 'In Progress' column fills with half-done work. Each unfinished item carries cost: it occupies memory, blocks reviewers, and ages while attention is split. A WIP limit makes that cost visible and unavoidable — when a column is full, you cannot start something new, so the only way forward is to finish what is already in flight.
Setting the limit is an experiment, not a formula. Teams often start near their headcount and tighten it until flow is smooth but no one is idle. Too high and the limit does nothing; too low and people stall waiting for downstream work. The right number surfaces the real constraint in the system.
The payoff is counterintuitive: limiting how much you start increases how much you finish. By cutting multitasking and forcing the team to clear blockages collectively, throughput rises and cycle time falls.
Planoda lets you set a WIP limit per board column and flags it visually when it is exceeded, so the constraint stays in front of the team instead of buried in a process document.
Related terms
- KanbanKanban is a visual workflow method that maps work onto a board of columns representing stages — typically backlog, in progress, and done. Cards move left to right as work advances. It emphasizes continuous flow, making bottlenecks visible, and limiting work in progress rather than committing to fixed time-boxes.
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- TriageTriage is the process of reviewing newly reported issues and deciding what happens to each — accept and prioritize, request more detail, route to a team, or close. Borrowed from emergency medicine, it keeps the incoming flow of bugs and requests from overwhelming a team by quickly sorting signal from noise at the front door.