emerald-hill.co.

uk

You can use this template for creating Sprint Burndown charts. The example is for a typical 2-week Sprint in which story po
Sprints can be a maximum of 4 weeks. Simply adjust the number of rows in the data table to reflect your Sprint length. The
dividing the total estimated capacity of the team in the Sprint (in this case, 120 story points) by the number of working day
row of the first 'Planned' column (under 'Burned Down'). The actual burndown is created by entering the estimated size of
'Actual' column under 'Burned down' . Remember Burndown reports the estimated effort remaining over time. This will be
estimates are not used

Burned Down Balance Daily 140

Date Planned Actual Planned Actual Completed
5/12/2014 12 9 120 120 9 120
5/13/2014 12 10 108 111 10 100
5/14/2014 12 12 96 101 12
5/15/2014 12 13 84 89 13 80
5/16/2014 12 13 72 76 13 60
5/19/2014 12 11 60 63 11
5/20/2014 12 11 48 52 11 40
5/21/2014 12 10 36 41 10 20
5/22/2014 12 24 31 #N/A
5/23/2014 12 12 #N/A #N/A 0
5/12/2014 5/19/2014
5/24/2014 0 0 #N/A #N/A
 2-week Sprint in which story points are being used. In Scrum
to reflect your Sprint length. The average trend line is created by
s) by the number of working days and entering the result in every
by entering the estimated size of any completed feature in the
remaining over time. This will be distorted if the original

Trend Line
Actual Burndown

5/19/2014
 Sprints Burned down Balance Completed Added to
Remaining Planned Actual Planned Actual in Sprint Sprint
5 60 53 300 300 53 0
4 60 64 240 247 64 70
3 60 65 180 253 65
2 60 66 120 188 66
1 60 #N/A 60 122 #N/A 350
0 60 #N/A 0 #N/A #N/A
300

250

200

150

100

50

0
5 4 3 2
 Trendline
Actual Burndown

4 3 2 1 0