Skip to main content
System StatusContact Support Agility Community

Velocity Trend Report

This feature is available in all editions.



The Velocity Trend report shows a team's historical velocity over a set period of time. This report keys off the story-level estimate and averages what the team has actually been able to deliver per sprint/iteration (indicated by the blue line).


By default, this report includes all sprints and are not grouped. Using the report filters below, you can specify the starting sprint and how the results are grouped.


  • All Agility trend reports require at least two data points. If not enough data is available, the report may be blank.  Depending on the duration you select in the filters, at least one complete period of data must be available to draw a trend line. When selecting days, this means that the minimum duration is actually 2 days, which will include 2 data points.

  • Your Show Weekend report settings may affect how much data is selected.  For example, if you choose two days as duration and one day is a Saturday or Sunday, and you have elected to not Show Weekends, then you may not have sufficient data to show a trend.

Viewing the Velocity Trend Report

  1. On the main menu,  choose any of the following paths:

    • Click the Reports icon reports_icon.png on the side bar and click All Reports. In the Planning Reports or Project/Release Reports sections, click Velocity Trend Report, or

    • On the main menu, click Team > Detail Planning or Member Planning or Detail Tracking or Member Tracking.
      Click the Reports icon reports_icon.png on the side bar and click Velocity Trend from the On This Page section.
  2. Select any of the following report filters and click Go.

Report Filters/Parameters

  • Team: Shows Team-specific data for the project or program. The default value is "All" or "Blank".
  • Backlog Group: Shows data assigned to the selected backlog group.
  • Start Sprint/Iteration: The first sprint/iteration you want to include in the report.
  • End Sprint/Iteration: The last sprint/iteration you want to include in the report.
  • Workitem: Shows data for a specific work item type: All (all workitems), StoriesDefects, or Testsets. The default option is "All".
  • Aggregation Type: Determines how the data is aggregated.  Valid values are:
    • Total Estimate - Sum the Estimate values. 

    • Workitem Count - Count of work items regardless of estimate value.

  • Show Active: Show active items on the report.

Understanding this report

  • Velocity (for the selected project). Depending on the Aggregation Type selected, this value will be the sum of all Estimate values, or the number of Work  Items, that  were completed within each iteration/sprint.

  • Velocity (for other projects). Depending on the Aggregation Type selected, this value will be the sum of all Estimate values, or the number of Work Items, that were completed in projects that share the same iteration/sprint schedule and are not in the selected project.

  • Average. A calculated average of all velocity data points for each iteration/sprint in the currently selected range that ended before the current date. This value does not include data from other  projects that share the same schedule. 

  • Target Estimate Points (Green Diamond). The Target value, if set for each iteration/sprint. Because this value is set on the iteration/sprint level, it can vary by sprint. Use the Target value to note differences in the expected capacity of a team due to vacations, holidays, or other time away.

  • Green bars indicate closed work in the current project.

  • Red bars indicate closed work in other projects.

  • Light Blue bars indicate open work in the current project.

  • Dark Blue line indicates the Average

  • If Show Active is selected, velocity bars show active and closed values (including backlog with values in future sprints).

  • Aggregation Type allow you to determine if Velocity values are calculated as the sum of the Estimate values or the count of Work Items that are completed in an iteration/sprint.


When calculating the average, the formula does not consider leading sprints with no delivery.  This is done to avoid penalizing teams as they ramp up in an existing set of work.