What this screen is for
These are two different measurements and the page shows both. Lead time counts from the moment an item was created to the moment it was completed — the whole wait, including the time it spent queuing. Cycle time counts only from the point work actually began. A long lead time with a short cycle time means items sit untouched before anyone picks them up.
Two figures head the page, a chart ranks the slowest items by lead time, and a paged table lists each completed item with its reference and title, who raised it, who closed it, when it last moved, and both its lead and cycle times. You choose a project and a window of the last 30, 60, 90 or 180 days.
When to use it
Use it when you need to answer "how long does work take here?" with a number, and to find the outliers behind a poor average.
What you see on this screen
Two figures head the page: Avg Lead Time (Created to Done) and Avg Cycle Time (In Progress to Done). Both are measured in hours and shown in the largest sensible unit — minutes under an hour, hours under a day, days above that — and both cover every completed item in the window, not just the ones charted.
The chart is a horizontal bar chart:
- The vertical axis lists work items, one per row, by title.
- The horizontal axis is Hours.
- Lead Time (hrs) is the blue bar and Cycle Time (hrs) the green one. Where an item has no recorded moment of starting, the two bars are the same length.
- Only the fifteen slowest by lead time are drawn, which the heading states along with how many completed items sit behind the averages.
The table lists #, Task, Status, Lead Time and Cycle Time, with who created the item, who finished it and when it last moved beneath each title.
Filters and actions
Pick a project and a period — Last 30 days, Last 60 days, Last 90 days or Last 180 days, starting at ninety — which is measured on when items were completed. The table pages at 10, 25, 50 or 100 rows, and paging never changes the averages or the chart.
Related
- Cumulative Flow — where in the process work is queuing
- Team Workload — how work is spread across people