beyond wip limits (lean kanban tour edition)
TRANSCRIPT
Hi, I’m Pawel
VSoft http://vsoft.pl
Software Project Management http://blog.brodzinski.com
Twitter @pawelbrodzinski
Once upon a time…
Why?
100% utilization
Cost of multitasking
Source: Gerald Weinberg, Quality Software Management: Vol. 1 System Thinking
Time to market
Catching up UM… HOW DOES THIS DARN CODE WORK,
AGAIN?
More mistakes
Source: E. Ophir, C. Nass, A. Wagner: Cognitive control in media multitaskers
On a highway
In a call center
On a computer
At a conference
Ball Flow
Game
No WIP Limits
Using WIP Limits
Total time: 26% better
Average cycle time: 59% better
Predictability*: 89% better
*Standard deviation
Why something that intuitive seems so counterintuitive when we talk about management?
…and they lived happily ever after
5O
WIP limits!
Average cycle time: 50% better
Pessimistic scenario: 53% better
Predictability*: 65% better
*80th percentile
Why?
Slack time
Automation
Code quality
Simple configuration
Self-balancing team
Slack time introduced by WIP limits drives continuous
improvement
When introducing WIP limits start with 2x
average WIP
Don Reinertsen
Cost of blocked work: 1% worse
Cost of idle capacity: 1% worse
Average cycle time: 28% better
Source: Don Reinertsen, #lkce12 keynote
Are aggressive WIP limits useful?
2O
What’s the use of slack time?
Idle time only?
Help others
Learn
System improvements!
CO
ST O
F DEL
AY
VALUE
CO
ST O
F DEL
AY
VALUE
Project and product
work
CO
ST O
F DEL
AY
VALUE
Project and product
work System
improvements
Cost of blocked work: 1% worse
Cost of blocked work: 1% worse
What’s the value of blocked or rejected
work?
Cost of idle capacity: 1% worse
Cost of idle capacity: 1% worse
Is capacity wasted or used to do
something else?
Average cycle time: 28% better
Average cycle time: 28% better
What happens to cycle time thanks to
improvements?
CO
ST O
F DEL
AY
VALUE
Project and product
work System
improvements
Takeouts
100% utilization is a myth
1OO%
Introducing WIP limits results in improved efficiency
Slack time sets us on path of continuous improvement
Thank you
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski
Special thanks to Don Reinertsen