View and work with the built-in team velocity chart

VSTS | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

Teams track their velocity to help them determine how much work they can perform sprint-over-sprint. The built-in team velocity chart provides an indication of how much work a team can complete during a sprint. The chart is only available for the product backlog and is based on the sum of estimates made to Effort (PBIs), Story Points (user stories), or Size (requirements). Velocity calculations rely on the team's ability to estimate backlog items.

Example Velocity chart from the work tracking data store
3 sprint velocity chart

Use this topic to learn:

  • How to view and work with the Velocity chart (work tracking datastore)
  • Required and recommended team activities to support velocity tracking

Once your team has completed a few sprints, they can use their velocity to forecast how much of the backlog they can finish within upcoming sprints. For usage guidance, see Velocity metrics and usage guidance.


In addition to the built-in velocity chart, VSTS accounts have access to the Velocity widget. The Velocity widget enables you to view more sprints and additional information than that provided by the velocity chart.

Work with the built-in team velocity chart

Velocity provides a useful metric for gaining insight into how much work your team can complete during a sprint cycle. Each team is associated with one and only one velocity chart.

Velocity will vary depending on team capacity, sprint over sprint. However, over time, the velocity should indicate a reliable average that can be used to forecast the full backlog.


The images you see from your web portal may differ from the images you see in this topic. These differences result from updates made to your web app, options that you or your admin have enabled, and which process was chosen when creating your team project—Agile, Scrum, or CMMI.

  1. From the backlog page, open the velocity chart.

    Click the the velocity chart in the upper right area of the page

    For charts to appear, your team must perform these activities:

    • Select sprints for your team
    • Assign backlog items to sprints
    • Estimate backlog items by defining the Effort, Story Points, or Size.
  2. The chart tracks your estimated backlog work (sum of Effort, Story Points, or Size) that your team has completed (green) in the previous sprints, or that are still in progress (blue).

    As this chart shows, velocity will fluctuate from sprint-to-sprint for a variety of reasons. However, you can quickly determine the average velocity by averaging the values shown in green for each sprint. You can then plug the average into the Forecast tool.

    Web portal, Velocity chart showing seven sprints of in progress and completed work


    Work items based on the Scrum process get counted in the chart once their State is set to Committed, whereas items based on the Agile and CMMI processes get counted once their State is set to Active. This behavior is set through the workflow states to category state mappings.

For your team to gain the greatest utility from the velocity chart, follow these required and recommended tasks.


  • Define sprints for the team project - Sprints should be of the same duration.
  • Select sprints for each team
  • Define and estimate backlog items. If you work from your team's backlog, the items you create will automatically be assigned to the current sprint (Iteration) and to your team's default Area Path.
  • Update the status of backlog items once work starts and when completed. Only backlog items whose State maps to a metastate of In Progress or Done will show up on the velocity chart or velocity widget.


  • Define and size backlog items to minimize variability.
  • Determine how your team wants to treat bugs. If your team chooses to treat bugs like requirements, bugs will show up on the backlog and be counted within the Velocity chart and forecasting.
  • Set your team's area path. The forecast tool will forecast those items based on your team's default settings. These settings can specify to include items in area paths under the team's default or exclude them.
  • Don't create a hierarchy of backlog items and bugs. The Kanban board, sprint backlog, and task board only show the last node in a hierarchy, called the leaf node. For example, if you link items within a hierarchy that is four levels deep, only the items at the fourth level appear on the Kanban board, sprint backlog, and task board.
    Instead of nesting requirements, bugs, and tasks, we recommend that you maintain a flat list─only creating parent-child links one level deep between items. Use Features to group requirements or user stories. You can quickly map stories to features, which creates parent-child links in the background.
  • At the end of the sprint, update the status of those backlog items that the team has fully completed. Incomplete items should be moved back to the product backlog and considered in a future sprint planning meeting.

Add other teams

If you work with several teams, and each team wants to work with their own backlog view, velocity chart, and forecast tool, you can add teams. Each team then gets access to their own set of Agile tools. Each Agile tool filters work items to only include those whose assigned area paths and iteration paths meet those set for the team.

Try this next