If your team has completed multiple sprints, you can forecast release and product completion dates and plan future projects more accurately by reviewing the velocity report. Based on the velocity of previous sprints that the report illustrates, you can accomplish the following goals:
Track how much effort your team has reported as complete for each sprint.
Estimate how much backlog effort your team can handle in future sprints if your team composition and sprint duration stay constant.
This report requires that the team project collection that contains your team project was provisioned with SQL Server Reporting Services. This report is not available if Reports does not appear when you open Team Explorer and expand your team project node.
In this topic
As the following illustration shows, a velocity graph shows the amount of effort that your team has reported as complete for each sprint. The source of the raw data is your product backlog. The horizontal axis represents sprints, and the vertical axis measures the backlog effort that your team has reported as complete. The vertical axis shows effort in whatever unit your team uses (for example, story points or hours).
The graph also displays a horizontal line that represents the average velocity across all the sprints.
You can filter the report by specifying the fields above the graph:
Specify sprints from the Sprint list.
Specify area paths from the Area list.
Required Activities for Tracking Work Items
For the velocity graph to be useful and accurate, your team must perform the following activities for tracking work items:
Define product backlog items and bugs, and specify the Iteration and Area paths for each.
For more information, see Create and Modify Areas and Iterations.
Specify and update the Effort for each product backlog item and each bug that is active.
Update the State of each product backlog item and each bug as it progresses from New to Done.