SPRINT BURNDOWN

Track the progress of your sprints with a burndown chart. Are you meeting your sprint goal? See the progress of each team member and click through to see individual tasks. track velocity over multiple sprints.

Screen Shot 2017-10-30 at 14.08.10.png

HOW IS YOUR SPRINT BURNING?

Screen Shot 2017-10-30 at 14.05.36.png

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. As the team completes 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. Can you maintain that smiley face throughout the sprint?

 

Screen Shot 2017-10-13 at 14.01.52.png
 

TRACK VELOCITY ACROSS MULTIPLE SPRINTS

Screen Shot 2017-10-13 at 14.20.49.png

See your team's velocity during the previous four sprints. If your velocity is stable so that your team can keep the same pace of work from one sprint to another, it can be used for planning longer term goals.

 

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!

Screen Shot 2017-10-27 at 15.05.19.png
 

SEE THE AMOUNT OF WORK PLANNED VS DONE

Screen Shot 2017-10-27 at 15.10.16.png

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 can accomplish per sprint. 

 
 

Related in the product tour



Common questions

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.