Karl

I know its a bit rude for me to reply to my own post but I'd be interested in
your thoughts on a minimum WIP limit above 1. Although in theory we could get to
1, I suspect that in practice it is not possible or desirable and that there is
an optimal WIP limit above one.

It would be interesting to identify those factors that push that optimal above
one, one being fixed costs per resource. Others being.... ?

Chris


--- In kanbandev@yahoogroups.com, "chrismatts1968" <chrismatts1968@...> wrote:
>
> --- In kanbandev@yahoogroups.com, Karl Scotland <kjscotland@> wrote:
> > What if that team of 20 is so highly multi skilled that they were able to
> > swarm on a single MMF (using the term just to wind you up ;-) and get it
> > done immediately. Wouldn't that be a good thing?
> >
> >
> > > What happens when you are below the optimal number?
> >
> >
> > Is the optimal number now, the most optimal for the future? Can't we
> > improve?
>
> Ummmmm. I think there are a number of assumption you are making that need to
be considered.
>
> 1. The stated assumption that a team can swarm around a task without any loss
of performance. More on this later as you are ignoring the "fixed" costs here.
>
> 2. That if we draw a graph of average unit ( developer ) performance ( y axis
) against WIP limit ( x-axis ), that the graph is flat or downward sloping from
high at low WIP to low at high WIP. I suspect that the reality is that it is
humped. Low performance for low AND high WIP with an optimal performance at a
WIP limit just below ( or above ??? ) the number of developers.
>
> Even if we assume perfected swarming, the fixed transaction costs will result
in a degradation of throughput if the WIP limit is too low.
>
> I think an interesting question would be... What is the minimum WIP limit. OR
another way to look at it is.... What is the optimal batch size. ( The maths is
easier )
>
> Another question would be.... What is the optimal WIP limit and is it the same
as the minimum WIP limit?
>