Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
Not seeing this insight? Add estimates to your issues in order to calculate your sprint burndown. If you’ve added estimates after your sprint has started, you’ll need to update the sprint’s start date. You should change the start and end date, so it’s set as a time before the estimations were added. Make these updates in your backlog so that you can view data for this insight. Learn more about adding estimates.
The Burndown insight helps you keep an eye on your sprint progress as it’s happening. By frequently tracking your output against your goal, you can shift focus, maintain momentum, or take a moment to revel at your pace.
The sprint burndown calculates how many points or issues have been completed, and how many points or issues remain.
This makes it easy for you and your team to see how you’re tracking and if necessary, make changes. Hover over the blue shaded area representing the remaining work.
The Y-axis represents the total amount of work committed to a sprint, measured in the estimation statistic you have configured for your board. As work’s completed, the percentage and corresponding blue line reduce, indicating how much work remains. Learn how to change how your board estimates work.
The grey horizontal line acts as a guide. It indicates roughly what percentage you’d expect to see at that point in time, in order to reach 0% by the end of your sprint.
Find your scope change information underneath the Burndown chart when you add, remove or modify issues after the sprint has started.
This expansion of the insight gives you more transparency over unplanned work. Scope change information will equip you with the right amount of detail to manage your team’s priorities effectively.
Hover over the sprint scope changes to reveal a tooltip with the most recent scope changes. You can also select these data points to see a list of affected work in a separate tab.
Overall, you’ll be able to track exactly how much work remains compared to how much work was planned. This helps you manage and pace effort, gives you adequate time to respond to trends and allows faster decision-making to help your team achieve their sprint goals.
The Burndown chart only applies to Scrum boards. Only Story Points on parent tasks are included, subtasks are not.
If you add a subtask to an issue in an active sprint, it’s treated as a scope change. However, this scope change will only be reflected in your burndown chart if you’re using either the Remaining estimate or Time spent fields on your board.
Was this helpful?