Track your sprint progress with a sprint burndown chart. Are you meeting your sprint goals or are you behind? Understand your team's velocity and see how the time is spent. Communicate your sprint status with a burndown chart that is constantly visible. 



A sprint burndown chart shows you how much work there's left in the sprint vs time. It is used for predicting when all the work in the sprint will be completed. The vertical axis represents work items and the horizontal axis represents the time. As the team completes tasks, the chart shows the work done vs the remaining work for during the sprint.



Immediately see how many tasks are done and how many there are still to do in your current sprint. Are you behind the target? How many days do you have to catch up? Or still on target? Congratulations - but can you maintain that smiley face throughout the sprint :)

Screen Shot 2014-12-01 at 12.40.48.png


Screen Shot 2014-12-01 at 17.50.12.png

See your team's velocity during the last four sprints. If your velocity is stable so that your team can keep the same pace of work from one sprint to another, you can use that as a tool for planning longer term goals.


Common questions

How does the chart handle work estimated vs word done?

The burndown line always shows the amount of work left. If no actual work done value is given for a task, the whole estimated value remains until the task is completed. If the work done is specified then it's subtracted from the estimate to get the work left for that task.

When the sprint is over,  the total amount of work done is calculated for that sprint. Actual work done values are used for the tasks that have them, otherwise the estimate values are used.




How do you decide when a task is completed?

A task is considered completed once it's moved to a state that is mapped to "Done" in the workflow mapping.

How is ahead / behind target calculated?

The current sprint view only looks at the tasks in the current iteration. It calculates a velocity for the iteration (number of points completed divided by the number of days passed in the iteration) and then extrapolates how many days it would take to complete the remaining points with that velocity. The behind target / ahead target value shown is the difference between that extrapolation and the actual number of days left in the sprint.

Does this chart support time estimates like story points?

Yes. You can use either estimates or task counts as the unit. You can select the unit in the chart settings when starting a new sprint.