Do Less to Do More: Kanban WIP Limits
Have you felt like your team is always busy, but nothing is ever quite finished? With a constant stream of new requests from clients and management, it’s easy to jump from task to task without delivering results.
Kanban WIP limits stop too many tasks from getting stuck in the “Doing” stage – and get more Done. Apply them to your Kanban board to improve team focus, reduce cycle times and increase customer satisfaction.
What are Kanban WIP limits?
Work In Progress (WIP) limits are an essential component of the Kanban method. The name is self-explanatory – they are simply a limit on the number of tasks that can be “In Progress” at any one time. When processes have multiple possible workflow states – To Do, Ongoing etc – a WIP limit will be applied to each.
On a Kanban board, WIP limits are applied to every work in progress state. Once the Kanban WIP limit has been reached, no new work items should enter that state until one of the outstanding items is completed.
Why do you need WIP limits?
Kanban WIP limits keep tasks from getting stuck before completion. It’s an easy pitfall for a busy team. For example – a feature just needs one more tweak to be released, but other high priority tasks caused it to fall by the wayside, or an article needs to be reviewed before publishing, but the editor was on holiday and no one followed it up.
When outstanding tasks must be cleared first, the whole team is able to focus on resolving blockers. The visual nature of the Kanban board means blockers and bottlenecks can be spotted immediately.
Little’s Law and WIP Limits
Cycle Time = WIP/Throughput
For a team with consistent throughput, reducing the amount of work in progress means cycle times are reduced and work is delivered faster. Faster work delivery means higher customer satisfaction!
Why multitasking makes things worse
Little’s Law can seem obvious: of course you can do half the work in half the time! However, it doesn’t take into consideration how much time is wasted by multitasking. Team members don’t switch between tasks immediately – moving from one task to another repeatedly causes the team to lose focus and waste time.
Context switching is estimated to cause at least a 10% penalty per switch. Multiple switches quickly add up to huge losses in productivity. Multitasking makes your team members feel busier while delivering less. Giving a task undivided attention is a much more effective approach of completing it efficiently.
Choosing WIP limits
When confronted with longer-than-ideal cycle times, very often project managers feel that they are falling behind and begin working on more tasks. Their reasoning appears to make sense – surely if tasks are taking too long, they should be started earlier to give the team time to finish them regardless of the current work in progress. The true result is that team members are unable to fully concentrate on and complete each single task in a timely member because the team efforts are spread too thin.
So how do you select the optimum WIP limit for your Kanban team? The best WIP limits ensure that no team member has to multitask, and that everyone has something to do. The exact limit will depend on the number of people in your team, if your team is cross-functional and the size of your project tasks. A good starting point is 1-2 items less than the number of people in your team.
Tips for working with Kanban WIP Limits
If your team hasn’t limited WIP before, they may be resistant to the change – it can feel counterproductive! It’s important to resist the urge to take on more tasks at once. Here are some tips to help smooth the transition:
- Encourage idle team members to pair up with others or swarm outstanding tasks. This helps build cooperation and new skills.
- Consider Swimlanes to organise your Kanban board. Teams often have members who cannot collaborate on the same tasks – customer service and development, for example. In this case, Kanban swimlanes should be used to set individual WIP limits for these roles.
- Use Classes of Service to set WIP limit policies for priority tasks. One common example is an “Expedited” Class with a WIP limit of 1 to handle emergencies.
WE UNCOVER THE EFFICIENCY OF YOUR WORKFLOW
Optimise your performance with Kanban analyticsSee a dashboard with your data
Stop your team from being overwhelmed with unfinished tasks and focus on getting things done. Implement Kanban WIP limits to reduce cycle times, find and resolve blockers, and improve customer satisfaction.
Has reducing your WIP limit impacted your team productivity? How did your team find the change in working method? Did WIP limits help you deliver results to clients faster? Tell us about your experiences in the comments.
Meet the Author
Sonya Siderova is an independent consultant who helps organisations deliver successful projects as a Product Manager and Agile Coach. She is a proud mother of a daughter and a son, and enjoys good food and heavyweight boxing championships. Sonya is a regular blogger and founder at Nave.
Product teams often argue which is better, but the focus should be on how to merge Kanban and Scrum together to del… https://t.co/73wN6TLBjGFollow
Many project managers appreciate the benefits of Kanban, but don’t know how best to prioritise tasks. Learn how Kan… https://t.co/QncgNAWzq1Follow
When implementing Kanban, it can be difficult to know how much work has been done, and how well your team is perfor… https://t.co/4vfoeUrQ7WFollow
Find out how maintaining a Kanban pull system and using analytics to spot bottlenecks early, prevents project delay… https://t.co/7lXXwEA2u1Follow
Once your tools start getting blunt, it's time to inspect and sharpen them. Value stream mapping is a visual techni… https://t.co/N6b0RzROn2Follow
Predicting how long a task will take plagues project managers everywhere. Kanban cycle time is an easy way to work… https://t.co/EXcLqbMtRAFollow
Though it's easy to focus on less complex tasks first, neglecting work in progress can put your team at immense ris… https://t.co/4QIKnr9YyUFollow
In this infographic, we’ll be explaining how to identify bottlenecks and stabilise your workflow using the cumulati… https://t.co/73o6ry6qz3Follow
Kanban WIP limits stop tasks getting stuck before completion and reduce cycle times. Learn how WIP limits improve t… https://t.co/wnz22p7dQwFollow
Explicit Kanban rules reduce the risk of productivity breakdowns and escalations of work items. The more explicit y… https://t.co/9XPNlujZO8Follow
Are you always short on time and on budget? We know the feeling because we’ve been there. Learn how our team at Nav… https://t.co/yEELO8I9qrFollow
Making accurate delivery forecasts is essential to staying on track, meeting deadlines and keeping a high level of… https://t.co/KeCohiSZwPFollow
Are long cycle times holding your business back? By following these tips and integrating data-driven analytics into… https://t.co/qyupTsQky9Follow
Kanban metrics let you monitor your productivity and give you the information to make data-driven decisions. Spot f… https://t.co/7eykWvlYuXFollow
Reducing waste allows you to achieve more with your team, streamlining your processes and maximising your profits.… https://t.co/R5C2FJeeCwFollow
How did supermarket restocking techniques revolutionise project management? Learn the history of Kanban and how it… https://t.co/wOI4kdvDi9Follow
Project managers are ultimately assessed by how their team delivers. In Kanban, throughput is the key measure of te… https://t.co/VzePsy8jFrFollow
Large teams and complex projects face a common issue – the Kanban board becomes cluttered and hard to read. Learn h… https://t.co/DHhWEWHGiZFollow