emerald-hill.co.

uk

You can use this template for creating Sprint Burndown charts. The example is for a typical 2-week
Sprints can be a maximum of 4 weeks. Simply adjust the number of rows in the data table to reflec
dividing the total estimated capacity of the team in the Sprint (in this case, 120 story points) by th
row of the first 'Planned' column (under 'Burned Down'). The actual burndown is created by enterin
'Actual' column under 'Burned down' . Remember Burndown reports the estimated effort remaining
are not used

Burned Down
Date
Planned Actual
5/12/2014
12
5/13/2014
12
5/14/2014
12
5/15/2014
12
5/16/2014
12
5/19/2014
12
5/20/2014
12
5/21/2014
12
5/22/2014
12
5/23/2014
12
5/24/2014
0

Balance
Daily
Planned Actual
Completed
9
120
120
9
10
108
111
10
12
96
101
12
13
84
89
13
13
72
76
13
11
60
63
11
11
48
52
11
10
36
41
10
24
31 Err:512
12 Err:512
Err:512
0 Err:512
Err:512

140
120
100
80
60
40
20
0
5/12/2014

mple is for a typical 2-week Sprint in which story points are being used. In Scrum
s in the data table to reflect your Sprint length. The average trend line is created by
ase, 120 story points) by the number of working days and entering the result in every
ndown is created by entering the estimated size of any completed feature in the
estimated effort remaining over time. This will be distorted if the original estimates

140
120
100
80

Trend Line

60

Actual Burndown

40
20
0
5/12/2014

5/19/2014

Burned down
Balance
Sprints
Remaining Planned Actual
Planned Actual
5
60
53
300
300
4
60
64
240
247
3
60
65
180
253
2
60
66
120
188
1
60
Err:512
60
122
0
60
Err:512
0
Err:512

Completed in Added to
Sprint
Sprint
53
0
64
70
65
66
Err:512
Err:512

350
300
250
200
Trendline
150

Actual Burndown

100
50
0
5