Release reports help teams predict end dates more accurately based on which tasks have been completed and which are still open.
Release reports help teams understand progress across a sprint, allowing teams to answer product questions such as whether the project is delayed or on time, if the recently added bugs pushed the release date forward, or if the sprint scope should be revised to make it in time. It’s important to have everyone on the same page and stay ahead of what’s on track, what’s blocked, and how changes are impacting goals and deadlines.
Release reports are automatically created for each sprint, and they are live updated every time a task is updated with a change to the status or estimate value.
The release report is made up of two axes.
On the x-axis you will find the duration, which is taken from the sprint’s start and end dates. If the predicted end date is after the desired end date, the x-axis will update its length.
The y-axis shows the total number of points that make up all estimated and non-estimated tasks in the sprint.
Over time, the graphic will show multiple layers and lines that show the relevant information about how you are burning up towards the goal:
The Desired Velocity shows the velocity that is required to hit your desired end date.
The Actual Velocity is calculated by using the closing date of completed tasks in the sprint, both estimated and unestimated. On the graph, it is shown by a solid dark-blue line.
The Predicted Velocity uses the total scope of the sprint and your Actual Velocity to predict an end date if you continue at the same pace. Note that in order for the system to provide a predicted end date, at least 30% of the tasks in the sprint must have their status set to “Completed.”