You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Velocity metrics provide valuable insights that help teams plan and [forecast](../../boards/sprints/forecast.md) sprints, and evaluate how accurately they estimate and meet planned commitments. These metrics indicate how much work a team can complete during a sprint, based on either **the count of work items completed** or **the sum of estimates** for effort (product backlog items), story points (user stories), or size (requirements). Use velocity to aid in determining team capacity, but don't confuse it with key performance indicators.
20
20
@@ -23,11 +23,18 @@ Velocity metrics provide valuable insights that help teams plan and [forecast](.
> The images in this article might differ from what you see in your web portal. These differences can be due to updates to your web app, options enabled by you or your admin, and the process chosen when creating your project (Agile, Basic, Scrum, or CMMI). The Basic process is available starting from Azure DevOps Server 2019 Update 1.
26
+
> The images in this article might differ from what you see in your web portal. These differences can be due to updates to your web app, options enabled by you or your admin, and the process chosen when creating your project (Agile, Basic, Scrum, or CMMI).
27
27
28
-
## Velocity chart types
28
+
## Understand velocity numbers
29
+
30
+
**Velocity** represents the amount of work your team completed in past sprints, which helps predict future capacity:
31
+
32
+
-**When tracking by count**: Velocity shows the number of work items (user stories, bugs, tasks) completed per sprint
33
+
-**When tracking by sum**: Velocity shows the total story points, effort hours, or size estimates completed per sprint
34
+
35
+
For example, if your team completed user stories worth 25 story points in Sprint 1, 30 story points in Sprint 2, and 28 story points in Sprint 3, your average velocity is approximately 28 story points per sprint. This average helps you plan how much work to commit to in future sprints.
29
36
30
-
::: moniker range=">= azure-devops-2020"
37
+
## Velocity chart types
31
38
32
39
You can choose between two Velocity charts: the in-context Velocity chart from the Backlogs page and the Velocity widget for dashboards. Both charts help you quickly understand the workflow state categories described in the following table.
33
40
@@ -61,15 +68,11 @@ You can configure each chart in the following ways:
61
68
- Number of iterations.
62
69
63
70
The widget offers more configuration options. For more information, see [Configure and view Velocity charts](team-velocity.md).
64
-
65
-
::: moniker-end
66
71
67
72
<aid="velocity-chart"></a>
68
73
69
74
## View the Velocity in-context report
70
75
71
-
::: moniker range=">= azure-devops-2020"
72
-
73
76
Velocity reports are available for both product and portfolio backlogs. Each report includes interactive controls, allowing users to customize the view to their specific interests.
74
77
75
78
1. Sign in to your project (```https://dev.azure.com/{Your_Organization/Your_Project}```).
@@ -97,8 +100,6 @@ Velocity reports are available for both product and portfolio backlogs. Each rep
97
100
98
101
7. To return to the Analytics summary, select the :::image type="icon" source="../../media/icons/back-arrow.png" border="false"::: back arrow.
99
102
100
-
::: moniker-end
101
-
102
103
## Configure the Velocity widget
103
104
104
105
You can only 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 that rolls up from several teams. For more information, see [Add teams](../../organizations/settings/add-teams.md).
0 commit comments