Measure Performance: Reports

Report: Cycle Time

Measure how long items take to move from one status to another, read the scatter plot and trailing average, and understand exactly which status changes are timed.

Cycle Time answers how long does an item take to get from here to there? You choose the two statuses; DevStride times every item that made the trip and plots each one as a dot. Use it to find your typical turnaround, spot outliers, and see whether a process change made work flow faster.

Open and scope it

  1. Open Measure Performance and pick Cycle Time under Agile.
  2. Set From and To in the toolbar. From defaults to your New status and To to your Done status, which measures the whole lifecycle. Set From to In Progress to measure active work time instead, or To to Ready for Release to measure development only.
  3. Set the Range. Items are included when they reached the To status inside the range; when they entered From does not matter and may be long before the range.
  4. Narrow with For and Filters as usual. There is no Show selector; the report always measures elapsed time.

How cycle time is measured

For each item that entered the To status during the range, DevStride takes the first time it entered To in the range and the most recent time it entered From before that moment, and reports the calendar time between the two. Items created directly in the From status count their creation as entering it. An item that never passed through From is not plotted.

Time is wall-clock time, including nights and weekends, and includes time spent in any statuses between From and To, so an item that bounced back to In Progress twice is measured from its last entry into From, not its first.

Reading the chart

The chart is a scatter plot: one point per completed item, placed by Completion Date along the x-axis and cycle time up the y-axis. Hover a point for the item number and its time, for example ITEM-123: 2 days.

  • Cycle Time: the green points, one per item.
  • Trailing Avg: a dashed gray line. Items completed on the same day are first averaged into one daily value, then each point on the line averages the daily values from the previous three axis intervals (three days, three weeks, or three months depending on the range's granularity). It follows how cycle time is changing rather than giving one flat number.

The y-axis unit is chosen from your largest value and always starts at zero: under 2 hours plots in Minutes, up to 72 hours in Hours, up to 60 days in Days, beyond that in Weeks. One very old item can push the whole axis into weeks; use Y-Axis Max under Options to cap the axis and see the rest of the points clearly.

Below the chart, three tiles summarize the plotted items: Avg. Time, Min. Time, and Max. Time.

Example. Most points sit at 2 to 4 days but a dozen sit at 3 to 6 weeks, all from one team. The average (9 days) describes nobody. Filter to that team and set From to In Progress: if the long times vanish, the items waited in the backlog or in review, not in development, and the fix is intake or review capacity rather than engineering speed.

Items and Transactions tabs

The Items tab lists the plotted items grouped by completion period, with Item and Cycle Time columns and a count in each header. The Transactions tab shows the status changes behind them.

Pitfalls

  • Skipped statuses hide items. An item dragged straight from Backlog to Done never entered In Progress, so it is absent from an In Progress → Done report. If many items are missing, the team is skipping the From status.
  • Both statuses must exist on the items' boards. If the Board filter limits you to boards whose workflow lacks the chosen status, the report is empty.
  • Reopened items. An item reopened and finished again is plotted once, at its first completion in the range.
  • Average versus points. The Trailing Avg smooths daily averages, so a day with one 30-day outlier moves the line less than a day with ten 3-day items moves it.

Related: Throughput shows how many items finish; Cycle Time shows how long each one took.