AI Changed the Bottleneck. Your WIP Limits Should Change With It.
- Mary Iqbal
- 17 hours ago
- 3 min read
Updated: 5 hours ago
AI can generate code faster than your team can review it.
Especially with the latest iteration of Claude, the code comes packed with lengthy comments, voluminous release notes, and logic in a bunch of different places, all of which needs to be reviewed before it goes to production. The human in the loop remains essential for quality. But with so much work coming at us, we can quickly become a bottleneck, too.
The counterintuitive answer is to limit work in progress and focus on fewer things to get more done.
It starts with seeing where the work is piling up.
Visualize the work
You can't limit WIP unless you know what work is in progress.
Most teams already do this. They track every work item on a visible board, and work goes through steps like New -> In Progress -> Done or through a more detailed process like New -> Development -> Code Review -> Testing -> Ready for Deploy -> Done.
As teams visualize their work, it's important to ask the right questions:
Does the board reflect how work actually moves?
Do we have places (like a blocked column) that we think are helpful but are actually quiet ways to hide problems that end up breaking WIP limits?
Does each step have a WIP limit?
Does the team honor the WIP limits?
Is work always moving from left to right (and not the other way around)?
Where does work consistently stop and pile up?
That last question matters even more when AI is generating code. A developer may be able to produce several changes quickly, resulting in a larger pile up for code review.
When teams discuss these questions in the Sprint Retrospective, they can find the hidden ways that team members get overwhelmed with too much WIP.
When you limit WIP, you gain focus
Starting more work does not equal finishing more work. Limiting WIP is one of the simplest and most effective complementary practices a Scrum team can adopt.
When you limit work in progress, three essential things happen.
Better work output
When people multitask, they sacrifice the ability to focus deeply, resulting in less thorough and reliable work outputs. Let teams do one thing at a time, well.
Less context switching
Task switching wastes time as team members reorient between tasks, reducing productivity by as much as 40%.
Improved forecasting
Once the team experiences a stable flow under a given WIP constraint, forecasting becomes far more reliable.
And, most importantly, work gets done.
This focus on focusing is vital, for example, in code review. Lower WIP gives reviewers enough attention to understand AI-generated logic and catch problems before production.
Teams finish the work on hand before they start something else. They do better work, and they do it faster.
Identify bottlenecks
With the board and WIP limits in place, queues become visible.
Say “Code Review” has a WIP limit of two. Two items are already waiting for review, while AI-assisted development has produced three more.
The limit tells the team to stop feeding the queue.
Instead of starting another item, the team turns its attention to the constraint: helping with reviews, reducing oversized changes, improving AI instructions or finding ways to make generated code easier to verify (for example with lightweight checklists).
Without the WIP limit, the team could appear productive while the review queue quietly grows.
Set the limit. Clear the queue.
AI makes it remarkably easy to start more work. It does not make human review capacity unlimited.
Visualize the flow. Set WIP limits. When work piles up, stop feeding the queue and help clear the constraint.
WIP limits aren’t “just for Kanban.” They give Scrum teams a practical way to protect focus, expose bottlenecks and finish work sooner, especially when AI can generate new work faster than humans can responsibly review it.
Ready to set our WIP limits? Start here.
If your Scrum team is struggling with growing queues, competing priorities or AI-generated work piling up in review, the Professional Scrum with Kanban class gives you a hands-on way to practice these techniques. Through exercises and discussion, you’ll learn how WIP limits and flow management can help your team deliver value sooner.
