What is Work in Progress?
Quick definition
Work in Progress (WIP) refers to tasks or items actively being developed but not yet complete. WIP limits restrict the number of concurrent items in a workflow stage to improve flow and reduce bottlenecks.
Work in Progress (WIP) represents any task, feature, or item that has been started but not finished in a development workflow. In Kanban systems, WIP is typically visualized as cards in intermediate columns between "To Do" and "Done." Managing WIP effectively is crucial for maintaining flow efficiency, as excessive WIP can lead to context switching, increased cycle time, and reduced productivity.
WIP limits are constraints set on the maximum number of items allowed in a specific workflow stage simultaneously. For example, a development team might limit their "In Review" column to 3 items, forcing developers to complete code reviews before starting new work. These limits create a pull-based system where new work is only pulled into a stage when capacity becomes available, preventing work from piling up and improving overall system throughput.
In AI-agent workflows and agentic systems, WIP management becomes critical when coordinating multiple agents or tasks. Agents operating with WIP limits can better prioritize work, avoid overload, and maintain focus on completing high-value tasks. This principle applies whether you're managing human developers, autonomous coding agents, or human-in-the-loop hybrid teams working together on complex projects.
Example
How it shows up in practice
A development team sets WIP limits: Backlog (unlimited), To Do (8), In Progress (4), In Review (3), Testing (2), Done (unlimited). When the "In Progress" column reaches 4 items, developers must complete tasks before starting new ones, ensuring focused work and faster delivery.
In Kanboard
In Kanboard, WIP limits are enforced at the column level through the column settings. Each column can have a maximum WIP limit, displayed as a visual indicator (e.g., "3/5") showing current items versus the limit. When a column reaches its WIP limit, it signals to team members that work must be completed before new items are pulled in, promoting sustainable pace and reducing context switching.
Frequently asked questions
Why are WIP limits important in Kanban?
WIP limits prevent bottlenecks, reduce context switching, improve flow efficiency, and help teams maintain sustainable pace. They create a pull-based system where work is completed before new work begins, reducing cycle time and increasing throughput.
How do I set appropriate WIP limits for my team?
Start with team capacity: divide available hours by average task duration. Monitor metrics like cycle time and throughput, then adjust limits based on performance. Begin conservative and increase gradually as the team optimizes their workflow.
What happens when a WIP limit is exceeded?
When a column reaches its WIP limit, it signals a bottleneck. Work should pause in that stage, and team members should focus on completing existing items rather than starting new ones until capacity frees up.
How do WIP limits apply to AI-agent workflows?
In agentic systems, WIP limits prevent agent overload, ensure sequential task completion, and improve resource utilization. They help coordinate multi-agent systems by controlling concurrent work and maintaining orderly task execution.