0

How does this work in Kanban? I understand WIP is the maximum capacity in each swimlane but how is it estimated, is estimation done by the number of cards?

  • 1
    Why do you need to estimate work in progress? Why can't you simply count the number of work items in progress? – Thomas Owens Oct 15 '17 at 21:00
  • I thought that was how it works, it seems like a bit of a pointless exercise given that people are by default going to work on once card at a time? – bobo2000 Oct 16 '17 at 15:03
  • 3
    Why do you think that it's a default behavior to work on one card at a time? It's actually hard to get into that mindset. If people are blocked on a task, their tendency is likely to start more work until they are unblocked. With a WIP limit, the idea is to push things through to completion. That may mean working to resolve blockers or impediments to completing one task. And yes, that may mean that less stuff gets done. Definitely not a natural behavior for people, at least most people that I've worked with. – Thomas Owens Oct 16 '17 at 15:14
3

As Bart explained, it is not WIP but the WIP Limit that helps the team and the stakeholders define the maximum capacity of any workflow or value stream.

Typically, WIP Limits are defined for each stage (column) of the swim lane as the general situation is that different functions/ people work in the different stages of a swim-lane's workflow.

WIP Limits work as a constraint on the channel that is represented by the swim-lane. Thus they discourage multi-tasking and encourage Flow - the key performance metric in Lean/ Agile systems.

Most teams might start with no WIP Limits and as they understand their system's/ team's behavior/ performance, they then start to put them in. As described in this page, the great Don Reinertsen recommended during last year's Lean Kanban India conference that teams should initially observe the flow of work through their system. Once they have learned enough, they can start with WIP Limits equal to half the value of the average WIP (number of items in any stage at any given time). Most teams that I have interacted with place a WIP Limit of 1 to 1.5 cards per team member working at each stage. This is to encourage a "single-piece" flow as much as possible, but have some additional work at hand in case something gets blocked or stuck due to any reason.

While you could define WIP limits in units other than the number of cards (such as story points), the overall effort of WIP LImits is to reduce multi-tasking - helping team embers to work on one task at a time. To that extent, it is easier to define and work with WIP Limits in terms of the number of cards.

Hope this helps!

2

WIP stands for Work-In-Progress, which is just the number of work-items (cards) that are in a particular state (or column on the Kanban board). WIP is not estimated, but simply calculated.

In addition to WIP, there can be WIP Limits.
A WIP Limit is an agreement within a team that the number of cards in a particular state must not exceed a predetermined number. The WIP Limit indicates the maximum capacity of the team for a certain kind of work. If the WIP Limit is exceeded, then the efficiency of the team will go down, because team members need to work on multiple tasks in parallel, with the associated overhead of task switching.

  • Is there a particular type of reporting used to measure this? – bobo2000 Oct 16 '17 at 15:08
  • That depends on if you consider having a discussion within the team to be a type of reporting. – Bart van Ingen Schenau Oct 16 '17 at 16:34

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.