3. @dominicad
THIEF #1 – TOO MUCH WIP
When demand exceeds capacity
demand
capacity
8/8
hrs
4. @dominicad
WHY TOO MUCH WIP MATTERS
Effective
people say
yes
deliberately
Too much WIP delays work
which increases cycle time
(CT)and cost-of-delay.
CT – The elapsed time work
takes to flow from start to
finish.
.
5. @dominicad
WIP is a leading indicator
Ave Cycle time = Ave WIP
Ave Throughput
6. @dominicad
YOU KNOW THIEF #1 STEALS TIME WHEN...
Ø Context switching is common.
Ø We start new tasks before finishing
older tasks.
Ø Work gets neglected and ages.
Ø We say, “Yes, I’ll do that.”
Molecules
Of
Emo2on:
The
Science
Behind
Mind-‐Body
Medicine,
Candace
B.
Pert,
1999
Endorphins,
book
7. @dominicad
libera2ng
hGps://docs.google.com/spreadsheets/d/1UKjHHM7Y-‐
emzSo4p0RLhzLaIR4Yp3owWR3JdT5QghoY/edit#gid=0
delivered
Build/
fix
Study
Silver
Bullet
Team
work
feedback
Business
requests
cycling done
(5)
(3)
(1)
EXPOSE WIP
liberating
8. @dominicad
THIEF #2 – UNKNOWN DEPENDENCIES
Time delays due to:
Ø Tightly coupled architecture
Ø Bottlenecks from specialized skillset
Ø Work outside of our control
$23B
PR/MrktShr
10. @dominicad
WHY DEPENDENCIES MATTER
Every dependency increases the
probability that you will be
late by 50%.
Dependencies are asymmetrical
in their impact.
Troy Magennis
11. @dominicad
YOU KNOW THIEF #2 STEALS TIME WHEN...
Ø Coordination needs are high.
Ø People aren’t available when you need
them.
Ø A change in one part of the code
unexpectantly changes something else.
2
Pizza
teams?
13. @dominicad
THIEF #3 – UNPLANNED WORK
An Interruption –
usually to fix a
problem
Ex: Break fix,
expedites, incidents,
fires
14. @dominicad
WHY UNPLANNED WORK MATTERS
https://puppet.com/resources/white-paper/2016-state-of-devops-report
Unplanned work steals
time away from planned
work.
15. @dominicad
YOU KNOW THIEF #3 STEALS TIME WHEN...
Someone joins your slack channel and within 2
min, 4 people are sucked into the vortex.
unplanned
work
(failure
demand)
17. @dominicad
THIEF #4 – CONFLICTING PRIORITIES
Conflicting
priorities:
When people are
uncertain or
disagree on what
to work on.
13
à
7
ini2a2ves:
1
cause
of
too
much
WIP
is
failure
to
priori2ze
properly.
18. @dominicad
WHY CONFLICTING PRIORITIES MATTER
If people can’t prioritize
effectively, they try to
do too much at once.
Too much wip = longer Cycle Time.
It
could
be
19. @dominicad
YOU KNOW THIEF #4 STEALS TIME WHEN...
Ø When people ask, "When will it be done?”
Ø When you spend hours in meetings
discussing priorities
Ø When you work on new requests before
finishing old requests.
Ø “My thing is a high priority!”
20. @dominicad
EXPOSE CONFLICTING PRIORITIES
mainmnai
delivereddoingTo do
Expedites
validate
Project 1
work
Project 2
work
On-hold
work
Project 2
security
vulnerability
fix
de-‐priori2zed
b/c
merit
reviews.
Make
priori2za2on
policy
explicit.
FIFO,
FIFS,
WSJF
in
class.
21. @dominicad
THIEF #5 - NEGLECTED WORK
Neglected, often important work
sits idle when other work is
seen as a higher priority.
cousins
22. @dominicad
WHY NEGLECTED WORK MATTERS
Important work sits waiting – until it
eventually becomes an emergency.
seized
23. @dominicad
YOU KNOW THIEF #5 STEALS TIME WHEN...
“When are we going to finish x?”
“We can’t get to x right now,
because we’re working on y.”
24. @dominicad
EXPOSE NEGLECTED WORK
5
donedoingTo do
Expedites
Unplanned
work
validate
9 days 13 days
Revenue
protecting
Revenue
generating
27. @dominicad
5
resolvedfix watch
ALL THE TIME THIEVES EXPOSED
HIGH LEVEL RISKS & ISSUES BOARD
incoming
problem
triage
> 20 days
10-20 days
< 10 days
See
connec2ons
that
would
otherwise
be
scaGered
across
mul2ple
team
boards.
28. @dominicad
THE TIME THIEF O’GRAM
Unplanned
work
Unknown
dependencies
Conflicting
priorities
Neglected
work
Too much
WIP
20
10
5
15
1
33. @dominicad
TO RECEIVE THE FOLLOWING:
Ø A copy of this presentation
Ø A copy of the Kanban for ITOps white paper
Ø A copy of the Lean Kit Lean Business report
Just pick up your phone and send an email to:
dominica@leankit.com
Subject: Flow