Burndown chart for Trello

Track the progress of your sprints with a burndown chart. See how much is left and whether you're in time or behind. Retain the history of your past sprints. See the stats, trends and outliers. Use in your daily standups. If you're a team doing Scrum with Trello, this is the chart for you. 


Burndown chart for Trello is part of Screenful dashboard for Trello. To get the chart above inside your Trello UI, activate the Screenful Agile from the Power-ups menu. Alternatively, you can just sign up for our 21 day free trial and use Screenful as a standalone web app. 



  • Select Trello lists, set sprint start and end date
  • Specify burn unit: story point or a task count
  • Set timezone and select working days
  • Split backlog on multiple Trello boards
  • See your velocity history and the amount of work planned vs done over time
  • See the tasks added or removed from sprint (coming soon)
  • Use custom fields for estimation (coming soon)

Don't just take our word for it

Screen Shot 2018-01-27 at 23.52.57.png

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. Learn more about assigning estimates to Trello cards

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 the card is 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.

Can I specify my timezone and/or working hours?

If you don't work on weekends, you may want to omit those days from the burdown. You can set your timezone and the exact working hours at the account settings.