Lead time and cycle time widgets

Azure DevOps Services | Azure DevOps Server 2019

Both lead time and cycle time widgets are extremely useful to teams as they indicate how long it takes for work to flow through their development pipeline. Lead time measures the total time elapsed from the creation of work items to their completion. Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.

The following diagram illustrates how lead time differs from cycle time. Lead time is calculated from work item creation to entering a completed state. Cycle time is calculated from first entering an In Progress state to entering a Completed state.

Conceptual image of how cycle time and lead time are measured

These measures help teams plan, spot variations in efficiency, and identify potential process issues. The lower the lead and cycle times, the faster the throughput your team has.

In this article you'll learn:

  • How to install and configure the Lead Time and Cycle Time widgets (Analytics)
  • How to interpret the scatter-plot control charts
  • How moving average and standard deviation are calculated in the charts

To learn more, see Cumulative flow, lead time, and cycle time guidance.


  • You must be a member of a project. If you don't have a team project yet, create one.
  • If you haven't been added as a project member, get added now.
  • To add a widget to a team dashboard, you need to be a member of the team. You must have Basic access or greater, have dashboard permissions, or be a team admin or project admin. Default settings provide all team members with permissions.
  • Boards must be enabled. If disabled, none of the work tracking Analytics widgets will display. To re-enable it, see Turn an Azure DevOps service on or off.

Add the widget to your dashboard

  1. (Optional) If you haven't yet configured your team's Kanban board, do that now. Define the columns and swimlanes that support your workflow processes.
  2. If you haven't yet added the widget to your dashboard, do that now.
  1. If you haven't yet enabled or installed Analytics], do that now.
  2. (Optional) If you haven't yet configured your team's Kanban board, do that now. Define the columns and swimlanes that support your workflow processes.
  3. If you haven't yet added the widget to your dashboard, do that now.

Configure the Cycle Time and Lead Time widgets

The Configuration dialog for the Cycle Time and Lead Time widgets is the same. You configure these widgets for a team. To learn more about teams, see Add teams.

  1. Choose the Actions icon actions icon and choose the Configure option icon to open the configuration dialog. Modify the title, and then select the team, backlog level, swimlanes, and time period you want to monitor.

    Configure dialog, Lead Time widget
  2. For a continuous flow, choose Rolling period and specify the number of days you want to view on the chart.

    Or, for a fixed scope view, choose and specify the Start date. Choose this view if your team employs a Scrumban process or follows a standard sprint process.

    The main difference between these two types of charts is that the fixed scope chart will provide information (in most cases) of scope change.

  3. Choose Save when done. The following image shows an example Lead Time chart showing 60 days of data.

    Example CFD chart, rolling 30 days

    For your lead/cycle time charts to provide useful data, your team must Update the status in a timely manner those work items that the widgets track.

Interpret the scatter-plot control charts

Both Lead Time and Cycle Time widgets display as scatter-plot control charts. They display summary information as well as provide several interactive elements.

Example Lead Time widget
Cycle Time widget

The chart dots represent completed work items where their position on the horizontal axis represents the date they were completed. Their position on the vertical axis represents the calculated lead time or cycle time.

  • Larger dots represent multiple work items with the same lead/cycle time
  • Dot color corresponds to the work item type displayed in the legend
  • Dark gray dots correspond to a mix of work item types.

Summary elements include:

  • Days on average (average lead time or cycle time) for the main work item types configured for the chart
  • The number of backlog work items used in the chart calculations; if there are more than three types of work items, you'll see a summary for Other
  • The black trend line indicates the moving average
  • The band around the trend line shows the standard deviation.

Interactive elements include:

  • Hover over any dot to see which work items contributed to the data point and the lead/cycle time for those items
  • Choose a dot to open the work item or query that lists the work items
  • To filter the chart, choose a work item type in the legend (backlog item icon,bug item icon, or other icon) to filter on that type; to return to the original chart, refresh the dashboard.

Moving average and standard deviation calculations

The daily moving average value corresponds to the average of data points that fall within the moving average window. The time-based moving average window is calculated based on the current day and previous N days, where N corresponds to 20% of the number of days the chart displays, rounded down to the nearest odd number.

For example, if the chart displays the last 30 days, then N=5 days (20% of 30 days=6 days, rounded down to 5). The moving average window for April 10th corresponds to the previous 5 days. Therefore, the April 10th moving average is the average of all data points that fall on April 5th through April 10th.

If there are no data points that fall within the moving average window, the chart doesn't show a moving average line. This can happen if you are starting out and there aren't enough days to calculate a moving average.

The standard deviation appears as a band that encompasses the moving average. Standard deviation is calculated based on all data points falling within the same moving average window. Like moving average, if no data points fall within the moving average window, the chart doesn't plot standard deviation.

We recommend your team review the lead/cycle time charts before or during each retrospective. Use lead time to help estimate delivery times and track service level agreements (SLAs). Use cycle time to identify potential process issues, spot variations in trends, and help with planning.