See how metrics can be used with your Kanban System for managing flow, your project and changes.
At least three practices of the Kanban Method imply the use of metrics. Metrics can be powerful tools. Sadly most kanban systems don’t make use of them and miss out on a big chance to make things easier. Metrics can help us with lots of different things we encounter in business like finishing projects on budget and on time, fighting for survival in the market, and continuous change to adapt in this complex world. Learn how metrics can help you and how to choose the right metric for your situation.
8. That’s the opposite of Flow
it’s called Christmas holidays
Cumulative Flow Diagram
9. 0"
2"
4"
6"
8"
10"
12"
14"
16"
18"
20"
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 in days
Average Lead Time
Lead Time Distribution Chart
19. Capability Analysis
Demand 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?
22. How fast can we deliver?
0"
2"
4"
6"
8"
10"
12"
14"
16"
18"
20"
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"
Mode = most common lead time
Median = 50%
Average = 11 days
80% of all tickets will finish in x
90% of all tickets will finish in x
98% of all tickets will finish in x
Weibull with
shape parameter k = 1.5
24. 0"
1"
2"
3"
4"
5"
6"
7"
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"71"72"73"74"75"
How fast can we deliver features?
25. Features Q(p;k, λ) = λ( - ln(1 - p))1/k
Number of data points: 59
Shape parameter (k): 1.54
Scale parameter (λ): 12.69
Average: 11.92
0"
1"
2"
3"
4"
5"
6"
7"
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"71"72"73"74"75"
How fast can we deliver features?
26. 0"
1"
2"
3"
4"
5"
6"
7"
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"71"72"73"74"75"
How fast can we deliver features? Weibull with
shape parameter k = 1.5
Mode = most common lead time
Median = 50%
Average = 11 days
80% of all tickets will be finished in around 17 days
90% of all tickets will be finished in around 22 days
98% of all tickets will be finished in around 30 days
27. How fast can we fix bugs?
0"
1"
1"
2"
2"
3"
3"
4"
4"
5"
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
28. 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
0"
1"
1"
2"
2"
3"
3"
4"
4"
5"
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
How fast can we fix bugs?
between 1.25 and 1.50
31. 0"
1"
1"
2"
2"
3"
3"
4"
4"
5"
1" 2" 3" 4" 5" 6" 7" 8" 9" 10" 11" 12" 13" 14" 15"
How fast can we fix bugs?
98% of bugs
are fixed in 12.4 days
Weibull with
shape parameter k = 1.25
32. Features are expected to be finished in 17 days with probability
of 80%
Bugs are expected to be fixed in between
3 (average) and 12 days (98%)
SLEs you can communicate to your customer
46. What do customers using this service
care about?
Make these your fitness criteria!
47. Fitness Criteria
“Fitness Criteria are metrics that measure things
customer value when selecting a service again and
again.”
- Delivery Time
- Quality
- Predictiability
- Safety (conformance to regulatory requirements)
David J. Anderson
58. Troy Magennis at LKCE13’s speaker dinner
"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."
59. "We do this only until we have
enough data to provide better
sample."
Troy Magennis at LKCE13’s speaker dinner
61. Example metrics to evaluate change
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
…
your fitness
criteria