Measure Performance: Reports

Report: Velocity

How DevStride measures velocity per cycle, how to choose the cycles and the status that counts as done, and how to use the result for planning.

Velocity answers how much do we finish in a cycle? It draws one bar per cycle showing the items, hours, or points completed while on that cycle. Use the average of recent cycles to decide how much to plan into the next one.

Open and scope it

  1. Open Measure Performance and pick Velocity under Agile.
  2. Click Cycles (it reads Select Cycles until you choose) to open the Cycle Selector, tick the cycles to compare, and click Select Cycles. Until you pick at least one the chart reads No Cycles Selected.
  3. Leave Status on your Done status, or change it (see below).
  4. Choose Show: Count, Time Estimate, or Point Estimate. Time Spent is not offered here.
  5. Narrow with For and Filters. Team and Board filters are hidden because the cycles set the scope.

There is no Range: each cycle's own dates define it.

How velocity is calculated

An item counts toward a cycle when it moved into the selected completion status while it was on that cycle. Each item counts once per cycle, no matter how many times it was reopened and finished. With Show set to an estimate, the bar adds up the estimate each item carried at the moment it completed, so later re-estimates do not rewrite past cycles.

Work finished while the item sat in the backlog or on a different board is not credited to any selected cycle. Items created directly in the completion status are not counted, because they never moved into it.

Choosing the completion status

By default an item counts when it enters your organization's Done status. If your team does not consider work finished until it reaches a later status such as Released, click Status, pick that status in Select Status, and the chart, the per-cycle counts, and the Items tab all update. The choice is remembered per organization and saved with a view, so two saved views can use different definitions of done.

Only a status that counts as completed can be picked. A terminal status that ends work as Not completed, such as Cancelled, is refused with a message, so cancelled work never counts toward velocity.

Reading the chart

Each bar is one cycle, in the order you selected them; the bar height is the completed count, hours, or points. Hover a bar for the exact value.

Example. The last five sprints read 21, 24, 9, 23, 22 points. The 9 was a sprint with two people out; planning on it would be as wrong as planning on 24. Use the typical value (about 22) for the next sprint, and expect the real result to land anywhere between the low and high of recent healthy sprints. If instead the bars read 30, 26, 22, 18, 15, velocity is falling: check Cycle Carry-Forward to see whether unfinished work is rolling forward each sprint.

Items and Transactions tabs

The Items tab groups completed items by cycle, each header showing N completed. The Transactions tab lists the status moves that were counted.

Pitfalls

  • Velocity is only comparable within one team and one estimation scale. Adding teams' points together, or comparing a team that estimates in hours with one that uses points, says nothing.
  • Unestimated items read as zero when Show is an estimate. Switch to Count to confirm the items are there.
  • Items completed after the cycle ended but while still on it are credited to that cycle. Close out cycles by moving unfinished work on, which Cycle Carry-Forward then reports as carried forward.

Related: Throughput measures the same completions per calendar period instead of per cycle.