Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Throughout your sprint, you can monitor the sprint burndown report to determine if your team is on track to complete its sprint plan. There are two accessible burndown charts: the in-context Burndown Trend report viewable from a team sprint backlog and the Sprint Burndown widget that you can add to a dashboard.
Both the report and the widget derive data from Analytics. They support monitoring burndown based on a count of work items or a sum of Story Points, Size, Effort, Remaining Work, or other numeric fields.
You can add either the report or widget to a dashboard. Additionally, you can monitor progress using the Analytics-based burndown or burnup widgets, which provide more configuration options.
Important
- Deleting Area Paths or reconfiguring Iteration Paths causes irreversible data loss. For example:
- Burndown and burnup widget charts
- Sprint burndown charts
- Velocity charts for teams with changed Area Paths
- Historical trend charts that reference the Area Path and Iteration Path as they were defined at the time for each work item.
- Once deleted, you can't retrieve historical data for these paths.
- You can only delete area and iteration paths that are no longer used by any work items.
For an overview of all burndown and burnup charts available to you, see Burndown and burnup guidance.
Note
Sprint burndown reports are derived from data tracked by a team during a sprint or iteration. For more information, see About teams and Agile tools.
The in-context Burndown Trend report
The Burndown Trend report is based on either a count of tasks or remaining work estimates, or other numeric fields that you define and update throughout the sprint cycle. For details, see Sprint planning. To open this report, see Open a Sprint backlog.
A healthy sprint burndown report appears similar to the following example. The blue area indicates the number of work items active or in progress each day of the sprint. As shown in this example, one work item is still active at the end of the sprint.
| Element | Description |
|---|---|
| Date range | The start and end date of the sprint. |
| Stories Remaining | The number of stories remaining in the sprint. If you choose a different work item type, the remaining number of those work items is shown. |
| Completed | The percentage of work completed based on original scope. Select Completed to see the full list of completed work items. |
| Average burndown | Average work completed. |
| Total Scope Increase | Shows the change in how much work from the original scope since the burndown started. The example shows that six work items were removed. |
| Remaining | The number of work items active or in progress. The example shows one active item is remaining in the sprint. |
| Total Scope | The total number of work items in the sprint including closed work items. If the team's default iteration is the @CurrentIteration, then new work items are added to the current iteration. The scope decreases as the Iteration Path is modified to another sprint, or work items are completed. |
| Ideal Trend | The ideal burndown rate for the sprint calculated from the number of work items, days in the sprint, and number of working days. |
Because individual team members might only update their work items once a week or every few days, there's usually a stair-case burndown pattern.
The Sprint Burndown widget
In the widget catalog, you find two versions of the Sprint Burndown widget: the Analytics-based Sprint Burndown and Sprint Burndown (Legacy), which is built from the work tracking data store.
Sprint Burndown widget
The Analytics-based Sprint Burndown widget provides an easy way to monitor progress for a team by showing work remaining for a given sprint. Work remaining is the vertical axis and time is the horizontal axis. You can define remaining work based on Stories or Tasks, and by counting the work items or summing a field.
| Element | Description |
|---|---|
| Date range | The start and end date of the sprint. |
| Tasks Remaining | The number of tasks remaining in the sprint. If you choose a different work item type, the remaining number of those work items is shown. |
| Completed | The percentage of work completed based on original scope. Select Completed to see the full list of completed work items. |
| Average burndown | Average work completed. |
| Total Scope Increase | Shows the change in how much work from the original scope since the burndown started. The example shows that four work items were added to the sprint. |
| Remaining | The number of work items active or in progress. The example shows 15 active items are remaining in the sprint. |
| Total Scope | The total number of work items in the sprint including closed work items. If the team's default iteration is the @CurrentIteration, then new work items are added to the current iteration. The scope decreases as the Iteration Path is modified to another sprint, or work items are completed. |
| Ideal Trend | The ideal burndown rate for the sprint calculated from the number of work items, days in the sprint, and number of working days. |
The charts provide useful metrics to help you answer the question: Are we on track to complete this set of work by the end a sprint?
- Percentage work complete
- Number of work items not estimated, if using a field other than Remaining Work
- Average burndown
- Total scope increase
Sprint Burndown (Legacy) widget
The Sprint Burndown (Legacy) widget adds a chart based on Remaining Work defined for tasks in a team's current sprint. Select this version when you don't have access to Analytics. Configuration options include team selection, and widget size.
If your dashboard already has a legacy version available, you can easily upgrade the widget by editing the widget's configuration, and checking Try the new version now. You can always go back to the legacy version by unchecking the box.
Prerequisites
| Category | Requirements |
|---|---|
| Access levels | - Project member. - At least Basic access. |
| Permissions | - Team administrator or project administrator or specific dashboard permissions granted to you. - To add a widget to a team dashboard: Member of the team. |
| Feature enablement | Azure Boards enabled. If disabled, none of the work tracking Analytics widgets display. To re-enable it, see Turn a service on or off. |
| Task awareness | Be aware of the required and recommended tasks, listed later in this article. |
| Category | Requirements |
|---|---|
| Access levels | - Project member. - At least Basic access. |
| Permissions | - Team administrator or project administrator or specific dashboard permissions granted to you. - To add a widget to a team dashboard: Member of the team. |
| Feature enablement | - Azure Boards enabled. If disabled, none of the work tracking Analytics widgets display. To re-enable it, see Turn a service on or off. - Analytics installed and enabled. Project Collection Administrators group members can add extensions or enable the service. Organization owners are automatically members of this group. |
Team activities to track tasks and Remaining Work
To monitor sprint burndown, your team must schedule sprints and assign work to those sprints.
If you want to monitor sprint burndown based on tasks and Remaining Work, your team must carry out these extra actions.
Required activities
- Define and estimate tasks for each product backlog item that you're working on in the sprint. If you work from your team's backlog and taskboard, the items you create are automatically assigned to the current sprint (Iteration) and to your team's default Area Path. For more information, see Add tasks to backlog items to support sprint planning.
- Update Remaining Work for each sprint task as work progresses. For more information, see Update tasks during the sprint cycle.
Recommended activities
- To decrease the effect of poor estimates, define tasks that take a day or less to complete.
- Don't divide tasks into subtasks. If you divide a task into subtasks, specify hours only for the subtasks. These hours are rolled up as summary values for the parent task.
- To support monitoring and achieve a smoother burndown chart, update Remaining Work daily or several times within a week.
- At the end of the sprint, update the task status of completed tasks and determine how to handle incomplete tasks.
Empty sprint burndown chart
If your sprint burndown chart appears empty, check these points:
- Did you assign tasks to the sprint associated with the chart?
- Did you assign Remaining Work to the tasks assigned to the sprint?
- Are the parent work items of the tasks assigned to the same sprint? If not, the tasks might appear in another sprint associated with the parent item.
Open a Sprint backlog
You view the in-context sprint burndown report from a team's Sprint backlog.
From your web portal, open your team's sprint backlog.
- Check that you selected the right project.
- Select Boards>Sprints and select the correct team from the team selector menu.
- Select Backlog.
To select another team, open the selector and select a different team or select the View Sprint directory option. Or, you can enter a keyword in the search box to filter the list of team backlogs for the project.
To select a different sprint than the one shown, open the sprint selector and select the sprint you want.
The system lists only those sprints that are selected for the current team focus. If you don't see the sprints you want listed, select New Sprint from the menu, and then select Select existing iteration. For details, see Define iteration paths.
View the in-context Burndown Trend report
To open the Sprint burndown report, select Analytics.
Use the interactive controls to select from the following options:
- The Start Date and End Date of the sprint. These dates default to the team's current iteration sprint dates.
- The Backlogs/Work Items to burn down on, either the product backlog (Stories, Issues, Product Backlog Items, or Requirements) or Tasks backlog to use. Your selection impacts the options available for the Burndown on menu.
- The Burndown on field to use to calculate burndown, either a Count of Work Items or a sum of a field, such as Story Points, Effort, or Size.
- Check or uncheck Show non-working days. Nonworking days appear as gray bars in the background when enabled. Default nonworking days are set for a team and for a team's sprint through the capacity page. For more information, see Set sprint capacity.
Select Reset to reset the controls to the default options. By default, the dates are set to the selected sprint. Changes to the start and end dates don't change any sprint date definitions.
If you don't track Remaining Work in tasks, you can view burndown based on a count of work items or tasks. To show a summary of the data for a specific day, hover over any point on the chart.
When you choose to view the Tasks backlog and Sum of Remaining Work, the blue area shows the sum of Remaining Work per day for those tasks that are still active or in progress. As the Remaining Work is updated, the chart indicates the rate of burndown. The Scope trend line indicates the addition of Remaining Work after the start of the sprint. The Ideal trend line indicates the ideal burndown rate for the sprint. Capacity lines are only shown when the team configured capacity.
Note
The options for the sum fields depend on the numeric fields defined for task and requirement category work item types. The most common fields used to show the burndown trend are:
- Count of work items
- Sum of Story Points, Effort, or Size
- Sum of Remaining Work
The selections you make are only set for you, and persist across sessions until you change them.
Add the report to a dashboard
To add the report to a dashboard, select the
actions icon and select Copy to Dashboard.
Select the dashboard and select OK.
Add the Sprint Burndown widget to a dashboard
You can add the Sprint Burndown widget to a dashboard and select the team whose progress you want to monitor. You configure these widgets for one or more teams.
If you need to add the Sprint Burndown widget to your dashboard, do that now.
You can filter the Add Widget dialog with sprint burndown to quickly locate the two widgets available to you.
To configure the widget, select the
actions icon and then select Configure.
Configure the Analytics-based Sprint Burndown widget
To configure the widget, select the
actions icon and select the Configure option.
Modify the Title of the widget and select your preferred Size. The Sprint Burndown widget can scale up to 10x10.
Make the following selections:
- Team: Select the Team you want to track.
- Backlogs and work items: Select the work items to include in your burndown. You can select to any backlog or a specific work item type.
- Burndown on: Choose how you want to burndown. You might burndown by count of work items or a sum based on a selected field.
- Select iteration: You can select @CurrentIteration, or a specific iteration.
- Time period: If you selected @CurrentIteration, these dates aren't editable. They're automatically the start and end date of the current iteration. If you selected a specific iteration, you can customize the start/end date for the burndown chart.
Advanced features: Select the following options that you want to add to your chart.
- Show total scope: Displays both the historical and projected scope increase.
- Show non working days: Displays nonworking days on the burndown. When displayed, nonworking days are shaded.
- Plot remaining using work item type color: Displays remaining work based on the work item type color, rather than the default blue color. If multiple work items are included, then it stacks colors by work item type.
Configure the Sprint Burndown (Legacy) widget
To configure the widget, select the
actions icon and select the Configure option.
If your dashboard already has a legacy version available, you can easily upgrade the widget by editing the widget's configuration. Select Try the new version now. You can always go back to the legacy version by unselecting the option.
Current and past sprint burndown charts
As you complete each sprint, the system maintains a history of your activity.
To view a past sprint and its burndown chart, select the sprint from the Sprint selector.
You can review sprint burndown in-context reports to show the team patterns in execution. The burndown charts maintain a record of the team's ability to plan and estimate.
Teams can find it useful to review these reports periodically during their sprint retrospectives. It can spark useful discussions and lead to setting one or more sprint goals, such as:
- How does your projected velocity match up to your actual velocity?
- How can you more accurately determine how much your team can accomplish in a sprint?
- How can you complete work at a more regular pace throughout the sprint?