Sprint Planning Checklist

1 Review the Product Backlog with Product Owner and Architecture prior to Sprint Planning
(Make sure there is stakeholder alignment, right-size and estimate backlog items)
2 Stories ready for the sprint are “right-sized” and well understood
(Stories taken into a sprint should be small and acceptance criteria known)
3 Team is invited to the meeting – stakeholders are notified of the sprint planning cycle
(Entered into the teams’ sprint calendar)
4 Entire team participates in the meeting including development, test, product owner, etc.
(Stakeholders can be present, but the product owner is a single voice for product decisions)
5 Meeting is facilitated (not directed) by the Scrum Master
(Stories presented by Product Owner and discussed by team)
6 Expect the Sprint Planning Meeting to be 2-4 hours in length for a two week sprint
(This meeting may take longer for teams not familiar with the code or business domain)
7 Determine number of team hours available for the sprint
(Identify any team member absences, % allocation, and other items that reduce from optimal)
8 Team identifies tasks and estimates hours collaboratively
(Each team member can create tasks on post-it notes, they can be entered in a tool later)
9 Tasks are right-sized from 1 to 18 hours to assure tracking in the sprint
(Keep task sizes small to where tracking of progress is obvious)
10 Tasks are not assigned during the meeting
(Allow tasks to be pulled by anyone from the task board during the sprint)
11 Team determines commitment to the sprint after each story is estimated
(Use hours estimated and available, as well as their confidence in the task estimates, and allow the team to determine
sprint commitment)
12 Create the task board with each story and all of its tasks grouped on each row
(A task board provides visibility, ownership and tracking of progress during the sprint)
 Planned Actual
Sprint duration (days) 10 9
Hours per day 8 6

Skill Name Full Time Time Off Committed Time Available Time
1 DV Bob 54 6 5% 45.6
2 DV Mary 54 0 30% 37.8
3 DV Jessica 54 0 10% 48.6
4 DV Peter 54 12 10% 37.8
5 DV 54 0 100% 0
6 DV 54 0 100% 0
7 BA Steve 54 0 100% 0
8 QA Vanessa 54 0 60% 21.6
9 QA Felix 54 6 60% 19.2
Average 54 3 53% 23
Sprint Output 210.6
Daily Output 21
 35 points in this sprint

ep

ep

ep

ep

ep
-Se
210.6 available hours for this sprint

-S

-S

-S

-S

-S
18

19

22

24

25
23
Th F M Tu W
Pts ID Total Hours Remaining: 294 262 245 206 198
2 417 green 8 8 8 8 8
Create list with new field names 4 4 4 4 4
Data migration 4 4 4 4 4

5 379 blue 64 47 47 47 54
Functional design 8 0 0 0 0
Tech design 8 0 0 0 0
Create test matrix 3 3 3 3 2
Create Roll Up list web part 6 6 6 6 6
Create list 2 1 1 1 2
Calendar web part 10 10 10 10 9
Build Workflow 4 4 4 4 4
Style event list 3 3 3 3 3
Style web calendar 6 6 6 6 6
Style calendar 4 4 4 4 4
 QA - test scripts 4 4 4 4 4
QA - testing 6 6 6 6 6
Build Event display web part and page 8

5 415 purple 58 58 46 46 44
Tech design 8 8 0 0 0
Update stored proc/view 4 4 2 2 0
Update list to use datasource 18 18 18 18 18
Update data with new short names 4 4 2 2 2
Refactor views using column 18 18 18 18 18
QA - test scripts 2 2 2 2 2
QA - testing 4 4 4 4 4

5 358 red 24 12 10 10 9
Research converting to a graphical button 18 0 0 0 0
Style it 3 3 3 3 3
QA - test scripts 1 1 1 1 1
QA - testing 2 2 2 2 2
export event code refactor 6 4 4 3

5 405 orange 50 47 47 35 38
Functional design 8 8 8 0 0
 Tech design 8 8 8 4 0
Create test matrix 3 3 3 3 3
Create workflow 4 4 4 4 4
Create list page web part 12 12 12 12 12
Data interface/stored proc 4 4 4 4 4
Style list page 5 2 2 2 1
QA - test scripts 2 2 2 2 2
QA - testing 4 4 4 4 4
data interface - develop trigger to push data 4
add extended properties 4

13 387 pink 90 90 87 60 45
Functional design 8 8 8 0 0
Tech design 16 16 16 8 0
Create test matrix 3 3 3 3 3
Modify data access layer and business object 5 5 5 2 0
Update screen 12 12 12 4 1
Implement web service 8 8 8 8 8
Update data model 8 8 8 8 8
Create detail page web part 12 12 12 12 12
Data interface/stored proc 4 4 4 4 4
Style screen additions 2 2 2 2 2
Style detail page 6 6 3 3 1
QA - test scripts 2 2 2 2 2
QA - testing 4 4 4 4 4

maroon 0 0 0 0 0
yellow 0 0 0 0 0

light green 0 0 0 0 0

cyan 0 0 0 0 0
294 261 229 196 163
 ep

ep

ep

ep

t
-Se

-Se

c
3-S

-S

-S

-S

1-O
24

25

26

30
29

Th F M T W
150 124 108 94 0
8 0 0 0 0 Sprint #1 Burndown
4 0 0 0 0 320
4 0 0 0 0
300

Hours Remaining
280

260

240

220

200
45 40 33 27 0
0 0 0 0 0 180
0 0 0 0 0
2 2 1 1 0 160
6 2 2 2 0 140
2 2 2 2 0
2 1 1 1 0 120
4 4 4 4 0
100
1 1 1 1 0
6 6 2 2 0 80
4 4 2 2 0
60

40

20

0
 120

100

80

4 4 4 4 0 60
6 6 6 6 0 40
8 8 8 2 0
20
42 42 42 42 0
0
0 0 0 0 0 9/18 9/19 9/22 9/23 9/24 9/25 9/26 9/29 9/30 10/1
0 0 0 0 0
18 18 18 18 18
0 0 0 0 0
18 18 18 18 18
2 2 2 2 2
4 4 4 4 4

9 9 9 9 0
0 0 0 0 0
3 3 3 3 3
1 1 1 1 1
2 2 2 2 2
3 3 3 3 3

20 17 12 9 0
0 0 0 0 0
0 0 0 0 0
3 2 1 1 0
2 6 2 2 0
6 0 0 0 0
0 0 0 0 0
1 1 1 0 0
2 2 2 2 0
4 4 4 4 0
2 2 2 0 0
0 0 0 0 0

26 16 12 7 0
0 0 0 0 0
0 0 0 0 0
2 2 1 0 0
0 0 0 0 0
1 1 0 0 0
8 0 0 0 0
0 0 0 0 0
6 4 2 0 0
0 0 0 0 0
2 2 2 0 0
1 1 1 1 0
2 2 2 2 0
4 4 4 4 0

0 0 0 0 0
0 0 0 0 0

0 0 0 0 0

0 0 0 0 0
131 98 65.3 32.7 0
Total Hours Remaining

Baseline (White)

green

blue

purple

red

orange

pink

maroon

yellow

light green

cyan
 maroon

yellow

light green

cyan

9/29 9/30 10/1

START

respecting the QA estimates

STOP
developing until the last
minute
CONTINUE

doing team design session