Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Examples of lean reports and visibility

6,099 views

Published on

Published in: Business
  • Be the first to comment

Examples of lean reports and visibility

  1. 1. Examples of Lean Reports and Visibility<br />EladAmit<br />September 2010<br />
  2. 2. Cumulative Flow Diagram (a.k.a. CFD)<br />Purpose:Visually depict our work queues and completion trends to allow us to find and fix bottlenecks as well as predict completion velocity<br />
  3. 3. Cumulative Flow Diagram (a.k.a. CFD)<br />End Report:<br />Stacked area chart showing per stage,<br />the total estimate for the items in that stage<br />Y-axis<br />total estimate<br />of items<br />X-axis<br />Time (tick per day)<br />
  4. 4. Cumulative Flow Diagram (a.k.a. CFD)<br />Example (Day 13):<br />Backlog – 5<br />Selected – 1<br />Develop Ongoing – 2<br />Develop Done – 1<br />Deploy – 1<br />Live - 4<br />
  5. 5. Cumulative Flow Diagram (a.k.a. CFD)<br />Filters:<br />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<br />Date range<br />Customer<br />Assignee<br />Severity<br />Priority<br />Etc...(preferably have the ability to filter on any attribute of the selected work item type)<br />
  6. 6. Process Control Chart<br />Purpose:Identify outliers in our process to focus improvement initiatives and reduce special cause variation<br />
  7. 7. Process Control Chart<br />End Report:<br />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<br />Y-axis<br />Actual chronological<br />time it took an item<br />X-axis<br />Time (tick per day)<br />
  8. 8. Process Control Chart<br />End Report:<br />The upper control limit (mean +3 std.dev.)<br />Outliers (anything above the upper<br />control limit) clearly marked<br />The mean cycle time for all<br />of the items in the report<br />The lower control limit (mean -3 std.dev.)<br />
  9. 9. Process Control Chart<br />Parameters:<br />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)<br />Item Filters:<br />Work item type (e.g. requirement, task, defect)Only one type due to different stages per type<br />Date range<br />Customer<br />Assignee<br />Severity<br />Priority<br />Etc...(preferably have the ability to filter on any attribute of the selected work item type)<br />
  10. 10. Process Control Chart<br />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)<br />Rebasing points due to changes<br />
  11. 11. Average Cycle Time<br />Purpose:Identify trends in our delivery velocity<br />
  12. 12. Process Control Chart<br />End Report:<br />Line chart with average cycle time per day<br />Y-axis<br />Average cycle time<br />for all items finished<br />on said day<br />X-axis<br />Time (tick per day)<br />
  13. 13. Process Control Chart<br />Parameters:<br />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)<br />Item Filters:<br />Work item type (e.g. requirement, task, defect)Only one type due to different stages per type<br />Date range<br />Customer<br />Assignee<br />Severity<br />Priority<br />Etc...(preferably have the ability to filter on any attribute of the selected work item type)<br />
  14. 14. Thank You<br />and Good Luck <br />

×