More Related Content
Similar to Eric Willeke - WIP: A Tragedy in 278 Parts
Similar to Eric Willeke - WIP: A Tragedy in 278 Parts (20)
More from AgileNZ Conference
More from AgileNZ Conference (20)
Eric Willeke - WIP: A Tragedy in 278 Parts
- 1. WIP: A Tragedy in 278 Parts
Eric Willeke (@erwilleke)
Rally Software
Your pic
- 3. Welcome!
Goal
Techniques
Improve service delivery
Optimize the right things
Avoid the tragedy of WIP
Keep your options open
www.rallydev.com ©2014 Rally Software Development Corp
- 5. How Long Does it Take?
Customer lead time
(Time to market)
Great
Idea!
I love it!
Time in process
We
should
get
started.
Ok, all
good!
Queue time
(waiting)
(TIP)
www.rallydev.com ©2014 Rally Software Development Corp
- 6. Whew!
Ship it!
How Long Does it Take?
Time in Process
(TIP)
What is
this
thing?
I think it
works.
Nope!
Now?
Yep!
www.rallydev.com ©2014 Rally Software Development Corp
- 7. How Long Does it Take?
Time in Process
(TIP)
Analysis & Design Code Test (and fix) Ship
Whew!
Ship it!
What is
this
thing?
I think it
works.
Nope!
Now?
Yep!
www.rallydev.com ©2014 Rally Software Development Corp
- 8. How Long Does it Take?
Time in process
(TIP)
= 18 days = 2 days
Wait time Touch time
Analysis & Design Code Test (and fix) Ship
www.rallydev.com ©2014 Rally Software Development Corp
- 9. How Long Does it Take?
Time in process
(TIP)
= 18 days = 2 days
Wait time Touch time
Touch time
Wait time + Touch time
Flow efficiency =
2d
= = 10% efficiency
18d + 2d
www.rallydev.com ©2014 Rally Software Development Corp
- 10. What is Your Goal?
I love it!
(Wow, that
was fast!)
I should get
started …
(but, I’m so
busy)
Flow efficiency “Resource” efficiency
10% efficiency 100% efficiency
Get things done Keep people busy
www.rallydev.com ©2014 Rally Software Development Corp
- 11. Your Goal
I love
it!
I love
it!
I love
it!
I love
it!
I love
it!
I love
it!
I love
it!
I love
it!
Keep value moving!
www.rallydev.com ©2014 Rally Software Development Corp
- 12. We Have Lots of Work!
(Don’t we have both efficiencies?)
- 14. The Tragedy of WIP
www.rallydev.com ©2014 Rally Software Development C©o2rp013
- 16. … and Impacts Throughput
WIP
Lead Time
TP =
You are here
www.rallydev.com ©2014 Rally Software Development Corp
- 18. How Much WIP is Bad?
www.rallydev.com ©2014 Rally Software Development Corp
- 19. Our Answer …
Between one and two work items per person
- closer to one!
See: http://www.rallydev.com/agilemetrics
www.rallydev.com ©2014 Rally Software Development Corp
- 21. But … but … how can we get there?
Only start the really important things
For every two items you finish, start one new one
For every “expedite,” pull an existing item out
Say “not yet” more
Be creative
www.rallydev.com ©2014 Rally Software Development Corp
- 22. Options and Commitment
Balancing expectations and flexibility
www.rallydev.com ©2014 Rally Software Development C©o2rp013
- 23. When do you Commit?
Customer Lead Time
(Time to market)
Queue Time
(waiting…)
Time in Process
(TIP)
When do your customers believe you?
www.rallydev.com ©2014 Rally Software Development Corp
- 24. Avoid Empty Commitments
An untrusted commitment has no meaning
(but lots of stress)
Treat work here as options
These are
committed
Changing our minds
here is cheap
Changing here
has a cost
www.rallydev.com ©2014 Rally Software Development Corp
- 25. Commit Later! (And Mean it)
Options have value
Options expire
Never commit early unless you
know why
Cover image courtesy Amazon.com, used with authors’ permission
www.rallydev.com ©2014 Rally Software Development Corp
- 26. Limit Commitments in Progress
Target Range
Commit to here
Not to here
www.rallydev.com ©2014 Rally Software Development Corp
- 27. Summary: Three Simple Guidelines
1. Keep work moving
2. Do less at once
3. Commit when it means something
www.rallydev.com ©2014 Rally Software Development Corp
- 30. Thanks for listening…
Eric Willeke
Rally Software
Follow me @erwilleke
Your pic
www.rallydev.com ©2014 Rally Software Development Corp