Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
Review your sprint burndown chart throughout your sprint cycle to check for these indicators:
- Is remaining work getting updated regularly? Flat spaces within the blue area indicate a lack of updates.
- Is remaining work increasing instead of decreasing? Increases can indicate work that wasn't estimated or planned. Both signal a need for the team to discuss how they'll complete the sprint tasks on time.
- Based on the actual burn rate, does the team feel confident that they'll complete the work by the end of the sprint?
To configure or view sprint burndown charts, see Sprint burndown.
By estimating remaining work of tasks for each product backlog item, teams have a good understanding of what they can accomplish within a sprint. Because the sprint tasks represent the overall sprint scope, the sprint scope is well defined. Anything that is not represented by a task in the sprint should be considered out of scope for the sprint.
As the team makes progress, divergences from the ideal trend line help the team monitor divergences from scope.
Increases instead of decreases within the blue graph may indicate:
Whatever the cause, teams should come together quickly to determine how to remedy the increased workload.
Solutions may include reassigning tasks or recruiting additional resources. The team should move all non-essential sprint work to the backlog and consider it during the next sprint planning meeting.
Mitigate risk through daily inspection
Your burn-down chart shows you if your project is on schedule. A daily check can mitigate risks and provide early warning of potential schedule or cost overruns, two metrics associated with traditional project management.
For example, when the actual remaining work (blue area) goes flat for a period of time, or remains high above the ideal trend line, the team is at risk of not meeting their sprint commitments.
Teams should meet immediately to course correct and either reassign work, recruit more resources, or reset expectations.
Try this next
In addition to the sprint burndown chart, teams can review the velocity at which they work sprint over sprint. The velocity chart tracks how many backlog items your team works on in a sprint.