This article will familiarize you with the overview, interpretation, configuration, and best use of the Sprint Velocity Trend widget.
Skip Ahead to:
Sprint velocity trend helps you measure how much work your team has accomplished in the past sprints. Once your team has completed a few sprints, they can use the velocity to forecast how much of the backlog they can finish in the upcoming sprint.
To plot a Sprint Velocity Trend, perform the following steps:
1. Open Analytics Builder and go to Standard Widgets. Click the Sprint Velocity Trend from the Agile Analytics group of metrics.
2. The Setting page appears where you can specify the settings for the widget:
Widget name: Modify the name, if required.
1. Select team: Select a team to see the sprints associated with the selected team only.
2. Select filter: Open the Select filter drop-down and choose an existing item filter for your sprints from the drop-down. You can also create an item filter by clicking the Add icon. Moreover, you can also modify an existing filter by clicking the Edit icon. The specified number of sprints matching to the applied filter will be plotted in the widget.
3. Sprint Selection: There are two ways to select the sprints for plotting the chart.
a. Fixed list of Sprints: Select this option to choose specific sprints from the given date range. To select specific sprints, specify a date range in the From and To fields. All the sprints whose start date falls between the given date range will be displayed. Select the sprints that you want to plot in your widget.
Note: Only past sprints (sprints with an end date earlier than the current date) are available for selection.
b. Dynamic list of Sprints: Click this option to dynamically plot the chart based on the past sprints (sprints with an end date earlier than the current date).
To select the dynamic sprints, enter the number of the sprints in the Sprints field. Note: You can select a maximum up to 99 sprints. By default, the past 12 sprints are selected.
4. Show Data Labels: Select this check box to show the labels on the chart.
Dimension and settings
5. Show Trend Line: Select this option to show the trend based on the linear progression of the selected analytics.
6. Left Y-axis: Select the Unit of Measurement and the chart type in which you want to plot data on the left Y-axis of the widget.
7. Right Y-axis: By default, the Unit of Measurement is set as count and the chart type is set as Line chart for the right Y-axis of the widget. Turn the toggle on to enable the settings for the Right Y axis.
The sprints along with their release name are displayed on the X axis and the Estimates (Points)/ Workitem Count are shown on the Y axis. The trend line shows the increasing or decreasing pattern of the sprint velocity.
If the team size is selected, then it helps you correlate the impact of the varying team size on the delivered workitems for the sprints.
The Chart also shows us the following summary on top:
1. Average: Shows the average value of sum of estimated points or workitem count of all the selected sprints.
2. Last 3: Shows the average value of sum of estimated points or workitem count of the last three sprints.
3. Best 3: Shows the average value of sum of estimated points or workitem count of 3 sprints that have the highest sum of points or workitem count amongst the selected sprints
4. Worst3: Shows the average value of the sum of estimated points or workitem count of 3 sprints that have the lowest sum of estimated points or number of workitems amongst the selected sprints.
Note: For the Medium size widget, only Average and Last 3 values are shown on top.
Based on the average velocity you can plan your future Sprints accordingly.
1. If the complexity level is high for the workitems planned for the Sprint then the average of the worst 3 sprints can give you a perspective of how many story points you might end up delivering in the worst case scenario.
2. Similarly, if the workitems being planned for the upcoming sprint are relatively straightforward then the average of the best 3 sprints where the team delivered the most story points can act as a guidance
3. And in cases, where the kind of work being done is same as it has been for the recent 3 sprints then the average story points delivered in the past 3 sprints will help you plan for your future sprint.
Note: If your team size is dynamic in nature then it will help you to have the Team Size in perspective to the average story points delivered in the past sprints. That will help you plan workitems for future sprint depending on how the change of team size as affected their velocity.
Note: Sprint Velocity Trend is based on current data.