This document discusses three types of lean reports that provide visibility into a workflow process: 1) Cumulative Flow Diagram (CFD) visually depicts work queues and completion trends over time to find and fix bottlenecks. 2) Process Control Chart identifies outliers in the process by plotting work item completion times to focus improvement efforts. 3) Average Cycle Time report identifies trends in delivery velocity by charting average completion times over time. The reports can be filtered and customized in various ways such as work item type, date range, assignee, and other attributes.

1. Examples of Lean Reports and Visibility EladAmit September 2010

2. 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

3. Cumulative Flow Diagram (a.k.a. CFD) End Report: Stacked area chart showing per stage, the total estimate for the items in that stage Y-axis total estimate of items X-axis Time (tick per day)

4. Cumulative Flow Diagram (a.k.a. CFD) Example (Day 13): Backlog – 5 Selected – 1 Develop Ongoing – 2 Develop Done – 1 Deploy – 1 Live - 4

5. 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)

6. Process Control Chart Purpose:Identify outliers in our process to focus improvement initiatives and reduce special cause variation

7. Process Control Chart End Report: 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 Y-axis Actual chronological time it took an item X-axis Time (tick per day)

8. Process Control Chart End Report: The upper control limit (mean +3 std.dev.) Outliers (anything above the upper control limit) clearly marked The mean cycle time for all of the items in the report The lower control limit (mean -3 std.dev.)

9. 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)

10. 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

11. Average Cycle Time Purpose:Identify trends in our delivery velocity

12. Process Control Chart End Report: Line chart with average cycle time per day Y-axis Average cycle time for all items finished on said day X-axis Time (tick per day)

13. 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)

14. Thank You and Good Luck 