Elad Amit - Examples of Lean Reports and Visibility

Examples of Lean Reports and Visibility

Elad AmitSeptember 2010

Cumulative Flow Diagram (a.k.a. CFD)

• Purpose:Visually depict our work queues and completion trends to allow us to find and fix bottlenecks as well as predict completion velocity

Cumulative Flow Diagram (a.k.a. CFD)

• End Report:

Y-axistotal estimateof items

X-axisTime (tick per day)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 170

2

4

6

8

10

12

14

16

18

20

0 0 0 0 0 0 0 0 0 0 0

34

56

78

0 0 0 01 1 1 1 1 1 1

11

11

11

0 0 01

01 1 1

2 2 2

11

11

11

0 02

12

1 1 10 0 0

22

22

22

02

2 21 1 1

2 2 2 2

11

11

11

86

4

7 7 7 76 6 6 6

55

55

55

BacklogSelectedDevelop OngoingDevelop DoneDeployLive

Stacked area chart showing per stage,the total estimate for the items in that stage

Cumulative Flow Diagram (a.k.a. CFD)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 170

2

4

6

8

10

12

14

16

18

20

0 0 0 0 0 0 0 0 0 0 0

34

56

78

0 0 0 01 1 1 1 1 1 1

11

11

11

0 0 01

01 1 1

2 2 2

11

11

11

0 02

12

1 1 10 0 0

22

22

22

02

2 21 1 1

2 2 2 2

11

11

11

86

4

7 7 7 76 6 6 6

55

55

55

BacklogSelectedDevelop OngoingDevelop DoneDeployLive

• Example (Day 13):– Backlog – 5– Selected – 1– Develop Ongoing – 2– Develop Done – 1– Deploy – 1– Live - 4

Cumulative Flow Diagram (a.k.a. CFD)

• Filters:– Work item type (e.g. requirement, task, defect)

Only one type due to different stages per typeNote: in case of requirement, need to aggregate the estimates from the tasks

– Date range– Customer– Assignee– Severity– Priority– Etc...(preferably have the ability to filter on any

attribute of the selected work item type)

Process Control Chart

• Purpose:Identify outliers in our process to focus improvement initiatives and reduce special cause variation

Process Control Chart

• End Report:

Y-axisActual chronologicaltime it took an item

X-axisTime (tick per day)

A dot on the chart is a work item which finished on that date. Ex: the dot at the end of the arrow was finished on November 20th and took 20 days to complete

Process Control Chart

• End Report:

The mean cycle time for allof the items in the report

The lower control limit (mean -3 std.dev.)

The upper control limit (mean +3 std.dev.)

Outliers (anything above the uppercontrol limit) clearly marked

Process Control Chart

• Parameters:– What portion of the process we want to measure the cycle

time for (e.g. from defined to development done, from start of development to testing)

• Item Filters:– Work item type (e.g. requirement, task, defect)

Only one type due to different stages per type– Date range– Customer– Assignee– Severity– Priority– Etc...(preferably have the ability to filter on any attribute

of the selected work item type)

Process Control Chart

• RebasingNeed to allow rebasing of mean, upper and lower control limits to allow the chart to account for changes (e.g. more employees, changes in development processes)

Rebasing points due to changes

Average Cycle Time

• Purpose:Identify trends in our delivery velocity

Process Control Chart

• End Report:

Y-axisAverage cycle timefor all items finishedon said day

X-axisTime (tick per day)

Line chart with average cycle time per day

Process Control Chart

• Parameters:– What portion of the process we want to measure the cycle

time for (e.g. from defined to development done, from start of development to testing)

• Item Filters:– Work item type (e.g. requirement, task, defect)

Only one type due to different stages per type– Date range– Customer– Assignee– Severity– Priority– Etc...(preferably have the ability to filter on any attribute

of the selected work item type)

Thank Youand Good Luck