Top Banner
Lead Time: What We Know About It And How It Can Help Forecast Your Projects Alexei Zheglov Lean Kanban Asia-Pacific Bangalore, December 2014
51
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Lead Time: What We Know About It...

Lead Time:What We Know About It

And How It Can Help Forecast Your Projects

Alexei ZheglovLean Kanban Asia-Pacific

Bangalore, December 2014

Page 2: Lead Time: What We Know About It...

Alexei Zheglov

connected-knowledge.com

[email protected]

Page 3: Lead Time: What We Know About It...

@az1

#lkapac

Page 4: Lead Time: What We Know About It...

“When a measure becomes a target,it ceases to be a good measure.”

Goodhart’s Law

Page 5: Lead Time: What We Know About It...

Kanban System Lead Time

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

Lead Time

The FirstCommitment

Point

AB

C

Discarded

D

Page 6: Lead Time: What We Know About It...

Ask Not

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

Lead Time

AB

C

Discarded

D

Not “how long will it take?”

Page 7: Lead Time: What We Know About It...

Do Ask

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

Lead Time

AB

C

Discarded

D

When should we start?

When do we need it?

Page 8: Lead Time: What We Know About It...

Decide

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

Lead Time

AB

C

Discarded

D

One eventprecedes (leads) another one

by this much

One eventprecedes (leads) another one

by this much

Page 9: Lead Time: What We Know About It...

Why?

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

Lead Time

The FirstCommitment

PointAB

C

Discarded

D

Includes the time the work item spent as

an option

Depends on the transaction costs (external to the

system)

Measures the true delivery capability

Page 10: Lead Time: What We Know About It...

Customer Lead Time

DeliveredIdeas Activity 1InputQueue

Output Buffer

∞???

Activity 2 Activity 3

?

Customer Lead Time

AB

Kanban system(s) lead time+

time spent in the unlimited buffer(s)

C

Discarded

D

Page 11: Lead Time: What We Know About It...

(Local) Cycle Time

DeliveredIdeas Activity 1InputQueue

Output Buffer

∞???

Activity 2 Activity 3

?

AB

C

Discarded

D

Cycle time is always localAlways qualify where

it is from and to

Often depends mainly on the size of the local effort

Page 12: Lead Time: What We Know About It...

Discussion 1: Gaming Metrics

• Given the goal to reduce the lead time (as we

have just defined it), what would you do?

• What would happen, good and bad?

• How can you game the local cycle time metric?

• Bonus question: if your delivery time metric

included the time before commitment, what

would you be motivated to do?

Page 13: Lead Time: What We Know About It...

Readyto Test

Flow Efficiency

F

E

J

GD

GYBG

DE NP

P1

AB

Customer Lead Time

Wait Wait WorkWork

IdeasReadyto Dev

5IP

Development Testing

Done

3 35

UATReady toDeliver

∞ ∞

Work WaitWork

Official training material, used with permission

Page 14: Lead Time: What We Know About It...

Readyto Test

Flow Efficiency

F

E

J

GD

GYBG

DE NP

P1

AB

Customer Lead Time

Wait Wait WorkWork

IdeasReadyto Dev

5IP

Development Testing

Done

3 35

UATReady toDeliver

∞ ∞

Work WaitWork

Official training material, used with permission

Work is waiting

Work is still waiting!Multitasking creates

hidden queues!

Page 15: Lead Time: What We Know About It...

Readyto Test

Flow Efficiency

F

E

J

GD

GYBG

DE NP

P1

AB

Customer Lead Time

Wait Wait WorkWork

IdeasReadyto Dev

5IP

Development Testing

Done

3 35

UATReady toDeliver

∞ ∞

Work WaitWork

Official training material, used with permission

%100time elapsedtime touch

efficiencyflow

Page 16: Lead Time: What We Know About It...

Readyto Test

Measuring Flow Efficiency

F

E

J

GD

GYBG

DE NP

P1

AB

Customer Lead Time

Wait Wait WorkWork

IdeasReadyto Dev

5IP

Development Testing

Done

3 35

UATReady toDeliver

∞ ∞

Work WaitWork

Official training material, used with permission

Timesheets arenot necessary!

Rough approximations (±5%) are often sufficient

In Aggregate

Sampling

Page 17: Lead Time: What We Know About It...

Readyto Test

Measuring Flow Efficiency

F

E

J

GD

GYBG

DE NP

P1

AB

Customer Lead Time

Wait Wait WorkWork

IdeasReadyto Dev

5IP

Development Testing

Done

3 35

UATReady toDeliver

∞ ∞

Work WaitWork

The results are often between 1% and 5%*

*-Zsolt Fabok, Lean Agile Scotland 2012, LKFR12; Hakan Forss, LKFR13

The result is not limited to the number!What did you decide to do?

Page 18: Lead Time: What We Know About It...

If the Flow Efficiency Is 5%...

If... Before After Improvement

Hire 10x engineers 100 95.5 +4.7%

The task is three times bigger 100 110 -9.1%

The task is three times smaller 100 96.7 +3.4%

Reduce delays by half 100 52.5 +90%

Page 19: Lead Time: What We Know About It...

Discussion 2:

Consequences of Low Flow Efficiency

(all positives, really)

• Why is lead time is hard to fudge?

• Why does lead time improve mostly due to

system-level improvements?

• How likely are the lead time data from your

previous projects to help you plan a new one?

Page 20: Lead Time: What We Know About It...

Measuring the delivery timecannot be separated fromunderstanding commitment.

Goodhart’s Law’s Corollary

Page 21: Lead Time: What We Know About It...

Start Measuring?

Page 22: Lead Time: What We Know About It...

Discussion 3: Measuring Lead Time

• Do you already collect lead time data?

• If not, do you already have these data available

somewhere, waiting for you to discover them?

• If not, would it be difficult or easy to start?

• What would you do differently in your company

with respect to lead time data after this

presentation?

Page 23: Lead Time: What We Know About It...

Deterministic approachto a probabilistic process?

probabilistic

!!!

Page 24: Lead Time: What We Know About It...

0

2

4

6

8

10

12

14

16

18

20

0-4 5-9 10-14 15-19 20-24 25-29 30-34 35-39 40-44 45-49 50-54 55-59 60-64 65-69 70-74 75-79 80-84 85-89 95-99 100-104

Example

Page 25: Lead Time: What We Know About It...

0

2

4

6

8

10

12

14

16

18

20

0-4 5-9 10-14 15-19 20-24 25-29 30-34 35-39 40-44 45-49 50-54 55-59 60-64 65-69 70-74 75-79 80-84 85-89 95-99 100-104

Example

Best-fit distribution:Weibull with

shape parameter k=1.62

Page 26: Lead Time: What We Know About It...

Heterogeneous Demand

DeliveredIdeas AnalysisInputQueue

Ready to Deliver

∞325

Development Test

3

AB

C

Discarded

D

E

G

F

H

Demand placed upon our system is differentiated

by type of work and risk

Page 27: Lead Time: What We Know About It...

Drill down by project type

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

0

2

4

6

8

10

12

14

16

18

20

Mixed data from different types of

projects

Page 28: Lead Time: What We Know About It...

4 types, 4 different distributions

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

0

2

4

6

8

10

12

14

16

18

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

75

-79

80

-84

85

-89

10

0-1

04

0

1

2

3

4

5

6

0-4

5-9

10

-14

15

-19

20

-24

25

-29

40

-44

55

-59

60

-64

65

-69

70

-74

75

-79

95

-99

...

...

Page 29: Lead Time: What We Know About It...

Delivery Expectations

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

Shape Average In 98%

1.62

1.23

1.65

3.22

In 85% of cases

30 d

35 d

40 d

56 d

<51

<63

<68

<78

<83

<112*

<110*

<99

Page 30: Lead Time: What We Know About It...

Delivery Expectations

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

0

5

10

15

20

0-4

5-9

10

-14

15

-19

20

-24

25

-29

30

-34

35

-39

40

-44

45

-49

50

-54

55

-59

60

-64

65

-69

70

-74

75

-79

80

-84

85

-89

95

-99

10

0-1

04

Shape Average In 98%

1.62

1.23

1.65

3.22

In 85% of cases

30 d

35 d

40 d

56 d

<51

<63

<68

<78

<83

<112*

<110*

<99

The averages are insufficientto specify delivery capabilities!

The average says nothing about variability! Needed:

the average and a high percentile (usually 80-99%)

Page 31: Lead Time: What We Know About It...

Another Example

0

2

4

6

8

10

12

0-2.5 2.5-5 5-7.5 7.5-10 10-12.5 12.5-15 15-17.5 25-27.5

Development

0

2

4

6

8

10

12

14

0-3 3-6 6-9 9-12 12-15 15-18

Support

Shape: 1.16 Shape: 0.71

Page 32: Lead Time: What We Know About It...

Weibull DistributionsOccur Frequently

Operations, support (k<1)New product development(k>1)

Page 33: Lead Time: What We Know About It...

Weibull DistributionsOccur Frequently

Operations, support (k<1)New product development(k>1)

The unique signature of your process

The unique signature of your process

Page 34: Lead Time: What We Know About It...

Bias

Feedback

How to “Read” a Distribution

Scale

Control

Expectations

Forecast

Page 35: Lead Time: What We Know About It...

Mode: how we rememberthe “typical” delivered work item.Trouble: it’s a very low percentile.

18-28% common.

Page 36: Lead Time: What We Know About It...

Median: 50% more, 50% less.Perfect for creating

very short feedback loops

Page 37: Lead Time: What We Know About It...

Average: we need it for Little’s Law

LeadTime

WIPteDeliveryRa

Little’s Law:handle with care

Page 38: Lead Time: What We Know About It...

The 63% percentile isthe best indicator of scale

Page 39: Lead Time: What We Know About It...

High percentiles (80th-99th):critical to defining

service-level expectations

High percentiles (80th-99th):critical to defining

service-level expectations

Page 40: Lead Time: What We Know About It...

Statistical process control:Sprint duration in iterative methods,

SLAs in Operations, etc.

Page 41: Lead Time: What We Know About It...

Forecasting Cards

Page 42: Lead Time: What We Know About It...

While I Was Preparing This Presentation, Somebody Sent Me This...

Page 43: Lead Time: What We Know About It...

Discussion 4:

Probabilistic or Deterministic?

• Would you describe the prevailing approach in

your organization as probabilistic or

deterministic?

• Is the expected answer to “how long will it take?”

a single number?

• Can you instead ask, “when do we need it?” and

“when should we start?”

• Can you make decisions given distributions of

probabilities?

Page 44: Lead Time: What We Know About It...

TestReady

S

RQ

P

ON

F

A Few Words About Projects…

E

I

G

D

M

DevReady

5Ongoing

Development Testing

Done

3 35

UATReleaseReady

∞ ∞

ProjectScope

Official training material, used with permission

Page 45: Lead Time: What We Know About It...

Delivery Rate

Lead Time

WIP=

Applying Little’s Law

From observed capability

Treat as a fixed variable

Targetto

achieve plan

Calculated based on known lead time

capability & required delivery rate

Determines staffing level

Official training material, used with permission

Page 46: Lead Time: What We Know About It...

Delivery Rate

Lead Time

WIP=

Applying Little’s Law

From observed capability

Treat as a fixed variable

Targetto

achieve plan

Calculated based on known lead time

capability & required delivery rate

Determines staffing level

Complicating factors here:Dark matter

“Z-curve effect”Scope creep

Complicating factors here:Variety of work item types and risks

Page 47: Lead Time: What We Know About It...

TestReady

S

RQ

P

ON

F

A Few Words About Projects…

E

I

G

D

M

DevReady

5Ongoing

Development Testing

Done

3 35

UATReleaseReady

∞ ∞

ProjectScope

Lead time data andobserved/measured delivery capability

at the feature/user story levelare critical to forecasting projects

The project initiation phase is a great time to builda forecasting model and

feedback loops

Page 48: Lead Time: What We Know About It...

New Kanban Book

Mike Burrows

Page 49: Lead Time: What We Know About It...

Influencers

Troy Magennis Dimitar Bakardzhiev David J Anderson

Dan Vacanti Dave White Frank Vega

Page 50: Lead Time: What We Know About It...

Discussion 5: What Now?

• What new ideas have your learned in this

session today?

• What will you do differently when you return to

your office tomorrow?

Page 51: Lead Time: What We Know About It...

Alexei Zheglov

connected-knowledge.com (blog)[email protected]

@az1