9. Visualize
20"
19"
18"
17"
16"
15"
14"
13"
12"
11"
10"
9"
8"
7"
6"
5"
4"
3"
2"
1"
0"
Lead Time Distribution Chart
Average Lead Time
1" 2" 3" 4" 5" 6" 7" 8" 9" 10"11"12"13"14"15"16"17"18"19"20"21"22"23"24"25"26"27"28"29"30"31"32"33"34"35"36"37"38"39"40"41"42"43"44"45"46"47"48"49"50"51"52"53"54"55"56"57"58"59"60"61"62"63"64"65"66"67"68"69"70"
y = No. of Tickets finished
with lead time x
x = Lead Time
19. Manage Flow
Demand Analysis Capability Analysis
How much
demand do
we have?
What are the
sources of our
demand?
Do we have
seasonal
variance in
demand?
What are the risk profiles
that are attached to
different types of work?
What skills are
required for different
types of demand?
What are our
current lead times?
What is our
delivery rate?
What skills do
we have?
25. Manage Flow using Weibull
5"
4"
4"
3"
3"
2"
2"
1"
1"
0"
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
Bugs
Number of data points: 8
Shape parameter:
Scale parameter:
Average: 3.88
not enough data points,
but visualisation gives us
an idea of the shape
26. Manage Flow using Weibull
5"
4"
4"
3"
3"
2"
2"
1"
1"
0"
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
Bugs
Number of data points: 8
Shape parameter: looks like between 1.25 and 1.50
Scale parameter:
Average: 3.88
27. Manage Flow using Weibull and Forecasting Cards
k = 0.75
k = 1.25
k = 1.50
29. Manage Flow using Weibull and Forecasting Cards
5"
4"
4"
3"
3"
2"
2"
1"
1"
0"
98% of tickets finish in
12.4 days
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
30. Manage Flow using Weibull
Service Level Expectations (SLE) we can communicate
85% of all features can be expected in 13 days
Bugs can be expected to be delivered in between
3 (average) and 12 days (98%)
31. Manage Project Flow
Project Scope
Average Lead Time
Average Throughput
Average WIP
33. Manage Project Flow using Little’s Law
Calculate Project Lead Time
Project Lead Time = No. of Tickets
Average Lead Time
Average WIP
= 450
1.2
15
= 36 weeks
34. Manage Project Flow using Little’s Law
Calculate Project Budget
Average WIP = Average Lead Time
No. of Tickets
Delivery date in weeks
= 1.2
450
36
= 15 WIP
35. Manage Project Flow using Little’s Law
Project Scope
20% 60% 20%
End Date
2nd leg
1st leg
3rd leg
Delivery Rate
36. Metrics help you
to better understand your
demand and capability
37. Metrics help you
calculate Service Level Expectations (SLE)
for different work items
42. Survivability
What’s the purpose of the services we provide?
What criteria need to be satisfied
to call the service fit for this purpose?
43. Survivability
“Fitness Criteria are metrics that measure things
customer value when selecting a service again and
again.”
- Delivery Time
- Quality
- Predictiability
- Safety (or conformance to regulatory requirements
David J. Anderson
44. Survivability
Bugs per Week
60
45
30
15
0
31 32 33 34
SLA Compliance in %
100
75
50
25
0
April May June July
Lead Times
20
15
10
5
0
0 5 10 15 20
45. Ask your customer
what they care about!
Make it your core metric#
you always measure!
52. Metrics for improvements
"Sometimes, you just have to roll
back with your chair to take a
second look from the back and
make a good guess how the curve
will end up."
- Troy Magennis at LKCE13 reception
53. Metrics for improvements
"We do only this until we have
enough data to provide better
sample."
- Troy Magennis at LKCE13 reception
55. Metrics for improvements
WIP limit breach
defect rate
customer
satisfaction
employee
satisfaction
number of
blockers
time spent on “real
quick” work
time tickets were
blocked
time waiting for external
suppliers
rework
time spent on
white noise
…
57. Bob from Operations
Wanted Y
Took me 60min
#
Urheber Markus Beyer - Herzlichen Dank!
Joe from Marketing
Wanted Y
Took me 30min
Sue from Product
Wanted Y
Took me 15min
CEO
Wanted Y
Took me 6h
Joe from Marketing
Wanted Y
Took me 45min
59. chindōgu are sometimes described
as "unuseless" – that is, they
cannot be regarded as "useless" in
an absolute sense, since they do
actually solve a problem; however,
in practical terms, they cannot
positively be called "useful".
https://en.wikipedia.org/wiki/Chind%C5%8Dgu
60. to check if your service
is fit for purpose
Metrics help you
to evaluate your
changes
to manage your
projects
to manage Flow
61. to check if your service
is fit for purpose
Collect metrics now
to evaluate your
changes
to manage your
projects
to manage Flow
62. Thank you!
Wolfgang Wiedenroth
Mail: wolfgang.wiedenroth@it-agile.de
Twitter: @wwiedenroth