Configure the Velocity widget


Teams track their velocity to help them determine how much work they can perform sprint-over-sprint. Velocity provides an indication of how much work a team can complete during a sprint based either on a count of work items completed or the sum of estimates made to Effort (PBIs), Story Points (user stories), or Size (requirements).

Example Velocity widget showing six sprints of velocity
6 sprint velocity widget


Feature availability: The Velocity widget is available only for VSTS at this time. For on-premises TFS, you have access to the velocity chart provided by the work tracking datastore.

Use this topic to learn:

  • Install and configure the Velocity widget available from the Analytics service
  • 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.

There are two velocity charts, the one you access by adding the Velocity widget to a dashboard, and the one viewed from the backlog of a team. The Velocity widget enables you to view more sprints and additional information than that provided by the velocity chart.


In order to add a Velocity widget to a dashboard, you must have the following in place:

Configure the widget

You configure your velocity widget for a single team. If you want to view the velocity for several teams, then you must configure a portfolio management team which rolls up from several teams. To learn more about teams, see Add teams.

  1. If you haven't yet added the Analyics Marketplace extension, do that now.

  2. If you haven't yet added the Velocity widget to your dashboard, do that now.

  3. Click the Actions icon actions icon and choose the Configure option to open the configuration dialog.

    Modify the title, select the team, and then choose either the backlog level or work item type to track. Select whether you want to track a count of work items or a sum of a numeric field. The most common summed field is that of Effort, Story Points, or Size.

    Configure dialog, Velocity widget

  4. Specify the number of sprints you want to view. The default is 6 and the maximum is 15.

  5. (Optional) Select the check boxes to show additional information for work completed later than planned for each sprint.

    Displayed planned work for iterations: Check this box to display the amount of work planned for an iteration at the start of the iteration. This is useful for comparing your planned work to actual deliverables. By default, the count of planned work begins as of the start date of the iteration.
    Days past start date of iteration when planned work is final: Specify a number of days past the start date to count planned work. For example, if the first 2 days of an iteration are for planning, then you can enter "3", and planned work will be counted on the 3rd day.

    Highlight work completed late Work items marked complete after the iteration end date are considered to be completed late and will show as light green. This is useful for spotting a trend where work items are marked complete after the iteration is complete.


    A work item is considered late when the work item's Completed Date is later than End Date of the Iteration the work item is currently assigned to.

    It will take into account the value you enter for Days past end date of iteration after which work is late.

    Days past end date of iteration after which work is late: Specify a number of days past which a work item is considered late if it's status is still new or in progress. For example, entering 3 days will give the team 3 days after the end of an iteration to mark work items complete or done, before they are considered late.

  6. Click Save when done. The following image shows Velocity based on Story Points and 8 sprints of data.

    Example Velocity widget, 8 iterations

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