Track a projected release with the Release Burndown
10 min
Intermediate
By the end of this lesson, you'll be able to:
- Read and understand the Release Burndown
- Track the projected release date for a version
- Describe how the Release Burndown can benefit your team
What is the Release Burndown report?
The Release Burndown report tracks the projected release date for a version. This helps you monitor whether the version will release on time so you can take action if work is falling behind.
👇 Here’s an example of a Release Burndown report.
Use the Release Burndown when:
- You want to see how quickly your team is working through the backlog.
- You want to see how work added and removed during the sprint has affected your team's overall progress.
- You want to predict how many sprints it will take to complete the work for a version.
The Release Burndown report can help you and your team:
âś” Monitor whether a version will release on time. If work is falling behind, you can quickly take action.
âś” Stay informed with version progress and scope change insights.
âś” Give accurate predictions to stakeholders.
Explore the Release Burndown report
👇 Click the icons below to explore this report.
Predicted sprints are calculated based on your team's velocity and the total work remaining for the epic. Velocity, in this case, is the amount of work completed in the last three sprints. Scope change is not considered when calculating the velocity, but is included in the total work remaining.
👇 Click the boxes below to see what you can learn from the Release Burndown.
How was this lesson?
next lesson
Track cycle time with the Control Chart
- What is the Control Chart?
- Explore the Control Chart