Plantilla Con Sprint BackLog
19
Product Backlog Story ID Story name Status Size Sprint Priority Comments 1 This is a sample story Done 3 1 2 This is another sample story Ongoing 8 1 3 This is a third sample story Planned 6 2 4 This is a fourth sample story Planned 7 3 5 This is an unallocated sample story Planned 13 6 This is a removed story Removed 5 You can add comments here to add key detail or explanation to the story. For larger definitions, use external
-
Upload
castillo-castill -
Category
Documents
-
view
134 -
download
2
Transcript of Plantilla Con Sprint BackLog
Product Backlog
Story ID Story name Status Size Sprint Priority Comments1 This is a sample story Done 3 12 This is another sample story Ongoing 8 1
3 This is a third sample story Planned 6 24 This is a fourth sample story Planned 7 35 This is an unallocated sample story Planned 136 This is a removed story Removed 5
You can add comments here to add key detail or explanation to the story. For larger definitions, use external tools and materials.
A4
Once a Story ID is given to a story, do not change that number or reuse it even if you delete the story.
C4
Use the following statuses: Planned (or empty) Ongoing Done Removed The sheet uses the above statuses in the formatting and calculation formulas.
D4
Story Points or Ideal Days
E4
Create a release plan by assigning stories to planned sprints. If there are more stories in the backlog than in the plan, leave the remaining stories unassigned to sprints.
F4
You may assign priorities to the stories, but keep in mind that priority does not always equal implementation order.
Sprint 1 Backlog
Sprint implementation days 7 Effort Remaining on implementation day…Trend calculated based on last 7 Days Totals 25 25Task name Story ID Responsible Status Est. 1Example task 1 Danny Dev Done 4 4Example task 2 1 Tina Tester Ongoing 7 7Example task 3 2 Danny Dev Ongoing 7 7<Delete these example lines> 2 Planned 7 7
0
5
10
15
20
25
30
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
A9
Count only active working and implementation days. Do not include Planning Day or Sprint Review. E.g. a 4-week Sprint would most likely have 18 implementation days.
Remaining on implementation day…24 17 212 3 4 5 6 72 07 2 26 6 109 9 9
0
5
10
15
20
25
30
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
0
5
10
15
20
25
30
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
Increment Plan
Incr. Start Days End Size Status Release Date1 13.6.2006 42 24.7.2006 242 25.7.2006 42 4.9.2006 0
Template note: Increment plan is intended to collect individual sprints into larger releases. In smaller projects, this is not needed.
Sprint Plan
Sprint Start Days End Size Status Release Date1 6/13/2006 14 6/26/2006 11 Planned2 6/27/2006 14 7/10/2006 6 Planned3 7/11/2006 14 7/24/2006 7 Planned4 7/25/2006 14 8/7/2006 0 Planned5 8/8/2006 14 8/21/2006 0 Planned6 8/22/2006 14 9/4/2006 0 Planned
UnplannedUnplannedUnplannedUnplannedUnplannedUnplannedUnplannedUnplannedUnplanned
Unallocated stories 13
Goal
Template note: Increment plan is intended to collect individual sprints into larger releases. In smaller projects, this is not needed.
Goal IncrementPlanning 1Specification and prototype development 1Specification and prototype development 1Specification and prototype development 2Specification and prototype development, documentation 2Usability test, documentation, prototype corrections 2
Product Backlog Burndown Chart
Original planned size 137Count trend from last 3 sprints
Velocity (points per sprint)Original estimate 30Last 3 sprints 25.0Realized total average 25.0Average last 8 25.0Avg. worst 3 in last 8 25.0Trend 25.0
Predictions - Completion at the end of sprint…Original estimate - Min 3Original estimate - Avg 5Original estimate - Max 8Last 3 sprints 6Realized average 6Average last 8 6Avg. worst 3 in last 8 6Trend 6Realized + St. Dev 6Realized - St. Dev 6
Sprint1 137 23 23 1372 114 29 27 1373 87 31 1374 56 28 1375 28 28 1376789
101112131415161718192021222324
Remain.Work
Planned Work
Realized Work
Current Total Size
0
2
4
6
8
10
12Velocity and Remaining Work
0
2
4
6
8
10
12Development Velocity
Planned Speed Realized SpeedAverage Realized Avg. Last 8Avg. Worst 3 in Last 8
B15
Average estimate * 0,6
B17
Average estimate * 1,6
B19
As of latest Product Backlog estimate
Note:In this chart, the tops of the bars show the amount of actual (or planned) implemented functionality at the beginning of each sprint. The bottoms of the bars show the changes in project scope(i.e. if the amount of story pointsin the project increases, the bottoms move lower). The lengthof the bars indicate the estimated size of the project at thebeginning of each sprint. The red line indicates the current planned scope.
0
2
4
6
8
10
12Velocity and Remaining Work
0
2
4
6
8
10
12Development Velocity
Planned Speed Realized SpeedAverage Realized Avg. Last 8Avg. Worst 3 in Last 8
In this chart, the tops of the bars show the amount of actual (or planned) implemented functionality at the beginning of each sprint. The bottoms of the bars show the changes in project scope
in the project increases, the bottoms move lower). The lengthof the bars indicate the estimated size of the project at the
The red line indicates the current planned scope.
Sprint 1 Backlog
Sprint implementation days 5 Effort Remaining on implementation day…Trend calculated based on last 5 Days Totals 0 0Task name Story ID Responsible Status Est. 1 2
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
A9
Count only active working and implementation days. Do not include Planning Day or Sprint Review. E.g. a 4-week Sprint would most likely have 18 implementation days.
Remaining on implementation day…
3 4 5
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
Daily Progress
Ideal Progress
Current Trend
Wo
rk
Re
ma
inin
g (
h)
Story ID: 1 Story: This is a sample storyTask: Example task
Responsible Person: Danny Dev
4
Story ID: 1 Story: This is a sample storyTask: Example task 2
Responsible Person: Tina Tester
7
Story ID: 2 Story: This is another sample storyTask: Example task 3
Responsible Person: Danny Dev
7
Story ID: 2 Story: This is another sample storyTask: <Delete these example lines>
Responsible Person:
7
Initial Estimate
Work Done
Work Left
Initial Estimate
Work Done
Work Left
Initial Estimate
Work Done
Work Left
Initial Estimate
Work Done
Work Left
![[PPT]Slide 1 - Deniss Kumlander · Web viewSprint retrospective 1-3 hours Release Sprint backlog Product backlog Updated product backlog The process, called Scrum, is widely used](https://static.fdocuments.in/doc/165x107/5afc53c97f8b9a944d8bfb15/pptslide-1-deniss-viewsprint-retrospective-1-3-hours-release-sprint-backlog.jpg)
