Track the progress of your sprints with a burndown chart. See how much is left and whether you're in time or behind. Click through to see individual tasks. Are you meeting your sprint goal?
HOW IS YOUR SPRINT BURNING?
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 time. When you complete tasks, the chart shows how much work is still remaining.
ARE YOU AHEAD OR BEHIND THE TARGET?
See how many tasks are done and how many are left in the current sprint, and whether you'll likely complete the sprint on time. The unit can be a set estimate or simply a task count.
TRACK VELOCITY ACROSS MULTIPLE SPRINTS
SEE THE STATUS PER INDIVIDUAL
See the number of tasks in different states per individual. Clicking labels shows the individual tasks. Great for stand-ups and sprint reviews!
SEE THE AMOUNT OF WORK PLANNED VS DONE
Selecting Planned vs done from the menu shows the scope of work in the beginning of each sprint versus the amount completed in the end of that sprint.
A record of historical velocity can help in estimating how much work a team is likely to accomplish in the next sprints.
Do you 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.
How does the chart handle work estimated vs work 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.