Cycle and flow times

The trigger for calculating and storing the cycle time for each phase is the transition out event of an item from the phase. For example, the number of days an item spent in the In Progress phase is only calculated after the item moves to In Testing.

Note:

• Items with the phase time of less than an hour are not included in the phase's average calculation. Also, if an item's phase is incomplete, the calculation of the average phase time is not precise.
• Items that have not reached their end phase or have skipped their start phase, as defined in the widget scope, are not included in the average cycle time calculation.
• Items in the Done metaphase with zero cycle time are not included in the average cycle time calculation. This may happen when an item moves from metaphase New directly to Done, skipping the In Progress or In Testing metaphase.

The cycle time includes a sum of all days that an item spent in each phase included in the cycle. For example, if a feature was in the In Progress phase, moved to the In Testing phase, moved back to In Progress, and out again, the cycle time includes all days of the In Progress phase, even though they were not sequential.

In summary, a work item's cycle time is the sum of all the days spent in each of the item's phases, from start to end phase.

Note: If an item moves back to the phase that is not included in the cycle, the time spent in that phase is not considered. For example, if a feature's start phase is In Progress, and it has spent some time in this phase, but then moved back to New, the time spent in New is not included.

When calculating cycle time in a given scope, such as a release, milestone, or sprint, there may be items that are missing data.

Missing data may be a result of:

• Unfinished items, such as backlog items, that have not reached their final phase.
• Backlog items that are missing measurements from some phases, due to the way the workflow was designed.

Note: If an item's phase time is missing, or the phase is incomplete, cycle time widgets do not consider this item for calculating the average cycle time.

Include the following fields in the item's form and in grids:

• Cycle time (available for epics, features, and other backlog items)

• Flow time (available for features and other backlog items)

  Note: If your workflow does not include phases in the In Delivery metaphase, or an item has not reached this metaphase yet, the feature flow time is equal to its cycle time.

In the Gantt chart for your work items, hover over a timeline bar to view the item's cycle time for that specific phase the bar represents.

The Cycle time dashboard widgets help you track the average cycle time for your features, user stories, and quality stories.

An item's average cycle time is the average time that all the work items spent in a range of phases included in the release cycle. For details, see Features average cycle time widgets.

You can customize the phases to include in the cycle time separately in each widget.

The widgets include insight cards that provide additional analytics. These analytics help you identify correlations, anomalies, trend behavior, and bottlenecks. For details, see Insight cards.

The Work item flow time trend widget helps you understand the trend of your workflow efficiency, based on the features' average flow time in scope.

The widget displays the average time it takes to deliver a feature, from the moment the work on an item starts until the item is in production. For details, see Work item flow time trend.