Overview

This workbook provides multiple template options for managing both product backlogs and sprint backlogs. Select the templa
product backlog template (option 1, 2 or 3) and one sprint backlog template (1 week or 2 week) -- and then delete the others

Below are instructions on how to use each template, including which fields are editable, which are not, and issues to be awar
modifications.

Product Backlog Instructions

Note: Each of the three product backlog templates use conditional formatting rather than visual basic (VBA) programming to
Macros can be problematic for some users in certain security environments.

The product backlog template options provide the data and calculations to not only generate a project/release burndown cha
empirical "PERT" extrapolations for release delivery dates based on a scrum team's velocity.

The three template options are identical, with the following differences (provided for individual preferences):

Product Backlog - option 1: This option highlights all rows within the ranges calculated in columns K, L and M.

Product Backlog - option 2: This option highlights only the last row of the ranges calculated in columns K, L and M.

Product Backlog - option 3: This option underlines only the last row of the ranges calculated in columns K, L and M.

Extrapolation data is calculated in the range F2:M15, and assumes a project with 10 sprints. This can be modified, but remem
chart's data range must be manually updated to match any changes. "P" stands for "pessimistic" (i.e. lowest velocity), "ML" st
average velocity"), and "O" stands for "optimistic" (i.e. highest velocity).

Be aware that many cells contain values and/or formulas required to calculate other cells and/or the burndown chart. Comm
cell (or the first cell in a range) that requires manual updating by the user. Avoid changing values in any cells that do not have
right corner, indicating there is a comment.

Sprint Backlog Instructions

The sprint backlog template 1- and 2-week options provide the data and calculations to generate a sprint burndown chart for
hours. For instructions, see https://platinumedge.com/blog/anatomy-sprint-backlog.

The two template options are identical, except for sprint length. Burndown chart data is generated based on data in rows 81-
added to accommodate more or fewer user stories and/or tasks in each user story, however be aware that formulas may hav
rows, as well as in each individual user story row.

Be aware that many cells contain values and/or formulas required to calculate other cells and/or the burndown chart. Avoid c
that contain formulas.

You may also notice the shape of the story point line is a little different between sprint length versions. The 1-week version is
you would expect. The 2-week version has a slight-but-noticeable slant instead of a straight vertical drop. This is due to Excel
weekend days where no development work would be done. It's a minor visual difference that should not negatively impact th
progress visibility of your sprint.
<Product Name> Release Projections
Project Burndown
160
### Project start
7 Sprint length (days) 140
3 Release 1 sprints (#) 120
7 Release 1 release sprint length (days)

Remaining Points
100
### Release 1 date
2 Release 2 sprints (#) 80
0 Release 2 release sprint length (days) 60
12/8/2016 Release 2 date
40
3 Release 3 sprints (#)
0 Release 3 release sprint length (days) 20
### Release 3 date 0
Plan Start 1 2 3 4 5 6 7
Actual

<Product Name> Product Backlog

ID Title Description
0002 <PBI title> As a ____, I want ____, so that ____.
0003 <PBI title>
0004 <PBI title>
0005 <PBI title>
0001 <PBI title>
0006 <PBI title>
0007 <PBI title>
0008 <PBI title>
0009 <PBI title>
0010 <PBI title>
0011 <PBI title>
0013 <PBI title>
0015 <PBI title>
0014 <PBI title>
0016 <PBI title>
0020 <PBI title>
0019 <PBI title>
0017 <PBI title>
0018 <PBI title>
0022 <PBI title>
0024 <PBI title>
0025 <PBI title>
0026 <PBI title>
0027 <PBI title>
0028 <PBI title>
0029 <PBI title>
0030 <PBI title>
0031 <PBI title>
0032 <PBI title>
0034 <PBI title>
0035 <PBI title>
0036 <PBI title>
 Requirement Empirical PERT Calculations
Project Burndown
Improvement Actual Sprints Actual
Maintenance Sprint Velocity Remain Burn
Overhead Start 10 10 142
1 9 142
2 8 142
3 7 142
4 6 142
5 5 142
6 4 142
7 3 142
8 2 142
9 1 142
2 3 4 5 6 7 8 9 10 10 0 142

Running Sprint Release

Acceptance Criteria Type Size Total CompletedDates
When I do this: ____, this happens:____. Requirement 2 2
1 3
3 6
3 9
5 14
3 17
2 19
8 27
5 32
3 35
3 38 ###
5 43
5 48
8 56
5 61
13 74 ###
13 87
21 108
34 142 ###
 34 176
21 197
34 231
13 244
55 299
89 388
55 443
34 477
55 532
21 553
13 566
55 621
144 765
 P Scope ML Scope O Scope
Plan Remain Remain Remain
Burn 10 10 10
142 100 100 100
128 90 90 90
114 80 80 80
99 70 70 70
85 60 60 60
71 50 50 50
57 40 40 40
43 30 30 30
28 20 20 20
14 10 10 10
0 0 0 0

Release
Goals

Release 1: <goal>

Release 2 <goal>

Release 3 <goal>
<Product Name> Release Projections
Project Burndown
160
### Project start
7 Sprint length (days) 140
3 Release 1 sprints (#) 120
7 Release 1 release sprint length (days)

Remaining Points
100
### Release 1 date
2 Release 2 sprints (#) 80
0 Release 2 release sprint length (days) 60
12/8/2016 Release 2 date
40
3 Release 3 sprints (#)
0 Release 3 release sprint length (days) 20
### Release 3 date 0
Plan Start 1 2 3 4 5 6 7
Actual

<Product Name> Product Backlog

ID Title Description
0002 <PBI title> As a ____, I want ____, so that ____.
0003 <PBI title>
0004 <PBI title>
0005 <PBI title>
0001 <PBI title>
0006 <PBI title>
0007 <PBI title>
0008 <PBI title>
0009 <PBI title>
0010 <PBI title>
0011 <PBI title>
0013 <PBI title>
0015 <PBI title>
0014 <PBI title>
0016 <PBI title>
0020 <PBI title>
0019 <PBI title>
0017 <PBI title>
0018 <PBI title>
0022 <PBI title>
0024 <PBI title>
0025 <PBI title>
0026 <PBI title>
0027 <PBI title>
0028 <PBI title>
0029 <PBI title>
0030 <PBI title>
0031 <PBI title>
0032 <PBI title>
0034 <PBI title>
0035 <PBI title>
0036 <PBI title>
 Requirement Empirical PERT Calculations
Project Burndown
Improvement Actual Sprints Target
Maintenance Sprint Velocity Remain Burn
Overhead Start 10 10 142
1 9 142
2 8 142
3 7 142
4 6 142
5 5 142
6 4 142
7 3 142
8 2 142
9 1 142
2 3 4 5 6 7 8 9 10 10 0 142

Running Sprint Release

Acceptance Criteria Type Size Total CompletedDates
When I do this: ____, this happens:____. Requirement 2 2
1 3
3 6
3 9
5 14
3 17
2 19
8 27
5 32
3 35
3 38 ###
5 43
5 48
8 56
5 61
13 74 ###
13 87
21 108
34 142 ###
 34 176
21 197
34 231
13 244
55 299
89 388
55 443
34 477
55 532
21 553
13 566
55 621
144 765
765
 P Scope ML Scope O Scope
Plan Remain Remain Remain
Burn 10 10 10
142 100 100 100
128 90 90 90
114 80 80 80
99 70 70 70
85 60 60 60
71 50 50 50
57 40 40 40
43 30 30 30
28 20 20 20
14 10 10 10
0 0 0 0

Release
Goals

Release 1: <goal>

Release 2: <goal>

Release 3: <goal>
<Product Name> Release Projections
Project Burndown
160
### Project start
7 Sprint length (days) 140
3 Release 1 sprints (#) 120
7 Release 1 release sprint length (days)

Remaining Points
100
### Release 1 date
2 Release 2 sprints (#) 80
0 Release 2 release sprint length (days) 60
### Release 2 date
40
3 Release 3 sprints (#)
0 Release 3 release sprint length (days) 20
### Release 3 date 0
Plan Start 1 2 3 4 5 6 7
Actual

<Product Name> Product Backlog

ID Title Description
0002 <PBI title> As a ____, I want ____, so that ____.
0003 <PBI title>
0004 <PBI title>
0005 <PBI title>
0001 <PBI title>
0006 <PBI title>
0007 <PBI title>
0008 <PBI title>
0009 <PBI title>
0010 <PBI title>
0011 <PBI title>
0013 <PBI title>
0015 <PBI title>
0014 <PBI title>
0016 <PBI title>
0020 <PBI title>
0019 <PBI title>
0017 <PBI title>
0018 <PBI title>
0022 <PBI title>
0024 <PBI title>
0025 <PBI title>
0026 <PBI title>
0027 <PBI title>
0028 <PBI title>
0029 <PBI title>
0030 <PBI title>
0031 <PBI title>
0032 <PBI title>
0034 <PBI title>
0035 <PB title>
0036 <PB title>
 Requirement Empirical PERT Calculations
Project Burndown
Improvement Actual Sprints Target
Maintenance Sprint Velocity Remain Burn
Overhead Start 10 10 142
1 9 142
2 8 142
3 7 142
4 6 142
5 5 142
6 4 142
7 3 142
8 2 142
9 1 142
2 3 4 5 6 7 8 9 10 10 0 142

Running Sprint Release

Acceptance Criteria Type Size Total CompletedDates
When I do this: ____, this happens:____. Requirement 2 2
1 3
3 6
3 9
5 14
3 17
2 19
8 27
5 32
3 35
3 38 ###
5 43
5 48
8 56
5 61
13 74 ###
13 87
21 108
34 142 ###
 34 176
21 197
34 231
13 244
55 299
89 388
55 443
34 477
55 532
21 553
13 566
55 621
144 765
 P Scope ML Scope O Scope
Plan Remain Remain Remain
Burn 10 10 10
142 100 100 100
128 90 90 90
114 80 80 80
99 70 70 70
85 60 60 60
71 50 50 50
57 40 40 40
43 30 30 30
28 20 20 20
14 10 10 10
0 0 0 0

Release
Goals

Release 1: <goal>

Release 2: <goal>

Release 3: <goal>
 577235413.xlsx

<Product name> - Sprint <#>

Sprint Dates: <Month> <DD> - <Month> <DD>, <YYYY>
Available working hours in the sprint Days in sprint: 4.5
Sprint Goal M Tu W Th F
24-Dec 25-Dec 26-Dec 27-Dec 28-Dec
Demonstrate the ability to <sprint goal>. (NOTE: Define a sprint goal in terms of working customer functionality
you will be able to demonstrate to internal stakeholders and possibly release to the marketplace.) Developers
<Developer name> 4 6 6 6 4
<Developer name> 4 6 6 6 4
Burndown: Hours & Points Remaining <Developer name> 4 6 6 6 4
<Developer name> 4 6 6 6 4
140 20
<Developer name> 4 6 6 6 4
18 Total sprint hours:
120
Estimated Hrs Remaining

Story Points Remaining

16 Total per day:
100 14

80 12
10
60 8
40 6
4
20
2
0 0
24-Dec 25-Dec 26-Dec 27-Dec 28-Dec Actual
Plan
Day of Sprint
Story Points

Feature Burndown - Based on estimated hours remaining

M Tu W Th F
Task Description Acceptance Criteria Type Story Responsible 24-Dec 25-Dec 26-Dec 27-Dec 28-Dec
Points

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 8 Developer name 8 8 8 8 8
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 5 Developer name 5 5 5 5 5
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

Page 18 of 23
 577235413.xlsx
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 3 Developer name 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 2 Developer name 2 2 2 2 2
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

<User story title> As a ____, I want to ____, so thatWhen I do this: ____, this happenRequirement 1 Developer name 1 1 1 1 1
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3
<task> 3 3 3 3 3

Actual Hrs Remaining 120 120 120 120 120

Schedule Hrs Remaining 130 98 65 33 0
Story Points Remaining 19 19 19 19 19
Day: 1 2 3 4 5
Issues
Team Member
<issue>

Team Member
<issue>
<issue>

Page 19 of 23
 577235413.xlsx

<Product name> - Sprint <#>

Sprint Dates: <Month> <DD> - <Month> <DD>, <YYYY>
Available working hours in the sprint Days in sprint: 10
Sprint Goal M Tu W Th F M Tu W Th F Total
25-Nov 26-Nov 27-Nov 28-Nov 29-Nov 2-Dec 3-Dec 4-Dec 5-Dec 6-Dec
Demonstrate the ability to <sprint goal>. (NOTE: Define a sprint goal in terms of working customer functionality
you will be able to demonstrate to internal stakeholders and possibly release to the marketplace.) Developers
<Developer name> 2 6 6 6 6 6 6 6 6 2 102
<Developer name> 2 6 6 6 6 6 6 6 6 2 102
Burndown: Hours & Points Remaining <Developer name> 2 6 6 6 6 6 6 6 6 2 102
<Developer name> 2 6 6 6 6 6 6 6 6 2 102
600 20
<Developer name> 2 6 6 6 6 6 6 6 6 2 102
18 Total sprint hours: Total sprint hours: 510
500 Total per day: Total per day: 51
16
Estimated Hrs Remaining

Story Points Remaining

14
400
12
300 10
8
200
6
4
100
2
0 0
25- 26- 26- 27- 27- 28- 28- 29- 29- 2- 2- 3- 3- 4- 4- 5- 5- 6- 6-
Nov Nov Nov Nov Nov Nov Nov Nov Nov Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Actual
Day of Sprint Plan
Story Points
Feature Burndown - Based on estimated hours remaining
M Tu W Th F M Tu W Th F
Task Type Story Responsible 25-Nov 26-Nov 27-Nov 28-Nov 29-Nov 2-Dec 3-Dec 4-Dec 5-Dec 6-Dec Done Accepted
Points (Y) (Y/N)
<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 8 Developer name 8 8 8 8 8 8 8 8 8 8
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 5 Developer name 5 5 5 5 5 5 5 5 5 5
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 3 Developer name 3 3 3 3 3 3 3 3 3 3
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 2 Developer name 2 2 2 2 2 2 2 2 2 2
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

<User story title> As a ____, I want to ____, so that When I do this: ____, this happenRequirement 1 Developer name 1 1 1 1 1 1 1 1 1 1
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

Page 20 of 23
 577235413.xlsx
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6
<task> 6 6 6 6 6 6 6 6 6 6

Actual Hrs Remaining 240 240 240 240 240 240 240 240 240 240
Schedule Hrs Remaining 510 453 397 340 283 227 170 113 57 0
Story Points Remaining 19 19 19 19 19 19 19 19 19 19
Day: 1 2 3 4 5 6 7 8 9 10
Issues
Team Member
<issue>

Team Member
<issue>
<issue>

Page 21 of 23