Home › Agile glossary › WIP limit
WIP limit
A WIP (work-in-progress) limit caps how many items may sit in a column at once, forcing the team to finish something before starting anything new.
Unlimited parallel work feels productive and ships nothing: context-switching taxes every item, and ten things at ninety percent deliver zero value. A cap makes finishing the only way forward.
A decent first limit is n+1 per column, where n is the number of people who work it. The bottleneck it exposes — usually review, not development — is the actual finding.
In Flocci Projects
No numeric enforcement per column, but card counts are visible at a glance and the open-workload-by-assignee chart catches per-person overload the board would hide.
Related terms
See it on a free boardBrowse the whole glossary
- Agile
- Backlog refinement
- Blocker
- Burndown chart
- Burnup chart
- Cycle time
- Daily standup
- Definition of done
- Definition of ready
- Epic
- Kanban
- Lead time
- Planning poker
- Product backlog
- Product owner
- Retrospective
- Scrum
- Scrum master
- Sprint
- Sprint goal
- Sprint planning
- Sprint review
- Story point
- Swimlane
- Throughput
- User story
- Velocity