Examples of lean reports and visibility
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Examples of lean reports and visibility

  • 4,369 views
Uploaded on

 

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,369
On Slideshare
4,369
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
17
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 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 