Product Sprint Backlog

Increment Plan
Incr.
1
2
Start
13.6.2006
25.7.2006
Days
42
42
End
24.7.2006
4.9.2006
Size
19
0
Status
Release Date
Template note: Increment plan is intended to collect individual sprints into larger releases. In smaller projects, this is not ne
Sprint Plan
Sprint
1
2
3
4
5
6
Start
6/13/2006
6/27/2006
7/11/2006
7/25/2006
8/8/2006
8/22/2006
Days
14
14
14
14
14
14
End
6/26/2006
7/10/2006
7/24/2006
8/7/2006
8/21/2006
9/4/2006
Unallocated stories
Size
8
3
8
0
0
0
-5
Status
Release Date
Planned
Planned
Planned
Planned
Planned
Planned
Unplanned
Unplanned
Unplanned
Unplanned
Unplanned
Unplanned
Unplanned
Unplanned
Unplanned
Goal
er releases. In smaller projects, this is not needed.
Goal
Planning
Specification and prototype development
Specification and prototype development, documentation
Usability test, documentation, prototype corrections
Increment
1
1
1
2
2
2
Product Backlog
Story ID Story name
1
This is a sample story
2
This is another sample story
3
4
5
6
This is a third sample story

This is a fourth sample story
This is an unallocated sample story
This is a removed story
Status
Done
Ongoing
Size
3
5
Sprint
1
1
Planned
Planned
Planned
Removed
3
8
13
5
2
3
Priority Comments
You can add comments here to add key detail or
explanation to the story. For larger definitions,
use external tools and materials.
Product Backlog Burndown Chart

Original planned size
Count trend from last
137
3 sprints
Velocity (points per sprint)

Original estimate
Last 3 sprints
Realized total average
Average last 8
Avg. worst 3 in last 8
Trend
30
25.0
25.0
25.0
25.0
25.0
12
Velocity and Remaini
10
Predictions - Completion at the end of sprint

Original estimate - Min
3
Original estimate - Avg
5
Original estimate - Max
8
Last 3 sprints
6
Realized average
6
Average last 8
6
Avg. worst 3 in last 8
6
Trend
6
Realized + St. Dev
6
Realized - St. Dev
6
Development Ve
12
10
Sprint
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Remain.
Work
137
114
87
56
28
Planned
Work
23
29
31
28
28
Realized
Work
23
27
Current Total
Size
137
137
137
137
137
Planned Speed
Average Realized
Velocity and Remaining Work
Note:
In this chart, the tops of the bars show the amount of actual
(or planned) implemented functionality at the beginning of each sp
The bottoms of the bars show the changes in project scope
(i.e. if the amount of story points
in the project increases, the bottoms move lower). The length
of the bars indicate the estimated size of the project at the
beginning of each sprint.
The red line indicates the current planned scope.
Development Velocity
Planned Speed
Realized Speed
Average Realized
Avg. Last 8
show the amount of actual

onality at the beginning of each sprint.
e changes in project scope
oms move lower). The length

d size of the project at the
t planned scope.
Daily Progress
Ideal Progress
Current Trend
35
Work Remaining (h)
Sprint 1 Backlog
30
25
20
15
10
5
0
Sprint implementation days

Trend calculated based on last
Task name
Example task
Example task 2
Example task 3
<Delete these example lines>
5
5
Story ID
1
1
2
2
Days
Responsible
Danny Dev
Tina Tester
Danny Dev
Totals
Status
Done
Ongoing
Ongoing
Planned
Effort Remaining on im
33
33
Est.
1
5
5
7
7
12
12
9
9
Work Remaining (h)
35
30
25
20
15
10
5
0
Remaining on implementation day

30 23 21
2
3
4
5
2
0
7
2
2
12 12 10
9
9
9
Sprint 1 Backlog
Ideal Progress
Current Trend
Work Remaining (h)
Daily Progress
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
0
Sprint implementation days

Trend calculated based on last
Task name
5
5
Days
Story ID Responsible
Totals
Status
Effort Remaining on impleme

0
0
Est.
1
2
.9
.8
.7
.6
.5
.4
.3
.2
.1
0
Remaining on implementation day

3
Story ID:
Task:
1
Story:
Example task
Responsible Person: Danny Dev

Initial
Work
5
Estimate
Done
Story ID:
Task:
1
Story:
Example task 2
Work
Left
Responsible Person: Tina Tester

Initial
Work
7
Estimate
Done
Story ID:
Task:
2
Story:
Example task 3
Work
Left
Responsible Person: Danny Dev

Initial
12 Work
Estimate
Done
Story ID:
Task:
Work
Left
2
Story:
<Delete these example lines>
Responsible Person:
Initial
Work
9
Estimate
Done
Work
Left

Product Sprint Backlog

Uploaded by

Copyright:

Available Formats

Product Sprint Backlog

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Product Sprint Backlog

Uploaded by

Copyright:

Available Formats

Increment Plan

er releases. In smaller projects, this is not needed.

This is a third sample story

Product Backlog Burndown Chart

Velocity (points per sprint)

Velocity and Remaini

Predictions - Completion at the end of sprint

Velocity and Remaining Work

show the amount of actual

oms move lower). The length

Work Remaining (h)

Sprint implementation days

Work Remaining (h)

Remaining on implementation day

Work Remaining (h)

Sprint implementation days

Effort Remaining on impleme

Remaining on implementation day

This is a sample story

Responsible Person: Danny Dev

This is a sample story

Responsible Person: Tina Tester

This is another sample story

Responsible Person: Danny Dev

You might also like