Lead Time and Cycle Time widgets

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

The Lead Time and Cycle Time widgets indicate how long it takes for work to flow through your 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 or Resolved state category to entering a Completed state category. For more information, see About workflow states in backlogs and boards.

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. We recommend that your team check the lead time and 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.

For more information, see Cumulative flow, lead time, and cycle time guidance.

Prerequisites

• Access:
  • Be a member of a project with at least Basic access.
  • To add a widget to a team dashboard, be a member of the team.
• Permissions: Be a team administrator or project administrator, or have specific dashboard permissions granted to you.
• Feature enablement: Have Boards enabled. If disabled, none of the work tracking Analytics widgets display. To re-enable it, see Turn a service on or off.
• Task awareness: Be aware of the required and recommended tasks, listed later in this article.

Add the widget to your dashboard

1. Configure your team's board, if you haven't already.

   • Define the columns and swimlanes that support your workflow processes.

2. Add the widget to your dashboard. There are two widgets: Cycle Time and Lead Time. Select the one you want to display and configure. For more information, see Use

Configure the Cycle Time and Lead Time widgets

The Configuration dialog is the same for the Cycle Time and Lead Time widgets. Configure these widgets for a team. For more information, see Create or add a team.

1. Select the context menu icon and select Configure to open the configuration dialog.

2. Modify the title, and then select the values you want to monitor:

   • Team
   • Work items
   • Swimlane
   • Field criteria
   • Time period

   

   To select a Swimlane, you must select Backlog.

   Note

   You can only select work item types that have been added to a backlog. To add work item types to a backlog, see Customize your backlogs or boards (Inheritance process). For On-premises XML process, see Process configuration XML element reference.

3. To further filter the work items used to calculate the lead or cycle time, specify the Field Criteria. For example, all the work items whose Release field is set to Milestone 1.

   

   Note

   Supplying no values to the filter might lead to selection of all work items, or might be an invalid filter argument depending on type of filter criteria.

4. For a continuous flow, select Rolling period and specify the number of days you want to view on the chart.

   Or, for a fixed scope view, select and specify the Start date. Select 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 provides information of scope change in most cases.

5. Select Save when you're done. The following image shows an example Lead Time chart showing 60 days of data.

   

   For your lead time and cycle time charts to provide useful data, your team must quickly update the status of 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 and provide several interactive elements.

Example Lead Time widget

The chart dots represent completed work items, and their position on the horizontal axis represents the date the team completed them. Their position on the vertical axis represents the calculated lead time or cycle time.

• Larger dots represent multiple work items with the same lead time or 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

• Days on average (average lead time or cycle time) for the main work item types configured for the chart. This number might not be equal to the average cycle time or lead time of all work items. It depends on configurations you use for the widgets. The average number is calculated based on each day the team takes time for work item.
• The number of backlog work items used in the chart calculations. If there are more than three types of work items, you 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

• Hover over any dot to see which work items contributed to the data point and the lead time or cycle time for those items.
• Select a dot to open the work item or query that lists the work items.
• Filter the chart by selecting a work item type in the legend ( , , 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. 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 = five days. 20% of 30 days is six days rounded down to the nearest odd number, which is five.

• The moving average window for April 10 corresponds to the previous five days. So, the April 10 moving average is the average of all data points that fall on April 5 through April 10.

  If you don't have data points that fall within the moving average window, the chart doesn't show a moving average line. This scenario can occur if you're 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.

Use a REST API to add a widget

To programmatically add a widget, use the following API endpoint:

   POST https://dev.azure.com/{organization}/{project}/{team}/_apis/dashboard/dashboards/{dashboardId}/widgets?api-version=7.1-preview.2

For more information, see REST API - Get widget.

Related articles

• Get guidance on cumulative flow, lead time, and cycle time
• Learn about Kanban boards
• View and configure a Cumulative Flow Diagram
• Understand workflow states in backlogs and boards
• Explore Agile, Scrum, and CMMI processes