Projected Velocity & Sprint Planning Template : Q2 2016
ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
IMPORTANT: MAKE A COPY OF THIS SPREADSHEET TO BEGIN USING :)
2
INSTRUCTIONSFull capacitySprint 1Sprint 2Sprint 3Sprint 4Sprint 5
3
Put the developer's full capacity for story points for a sprint in column B.Developer 140.50.50.750.751
4
Put multipliers for a given developer for a given sprint in columns C-G. For example, if you know that someone is going to be out for half of the sprint, put 0.5.Developer 240.50.50.50.750.75
5
Add as many columns as you need for the time period you're planning.Developer 3510.75111
6
Developer 450000.51
7
Developer 530.250.250.7511
8
Numbers above this line are for calculations; focus below this line for actual plans.
9
Full capacitySprint 1Sprint 2Sprint 3Sprint 4Sprint 5
10
If you do the above steps correctly, this section will now show you the total number of points a given developer will have in a sprint, adjusted for any hits to their velocity you inputted above (like vacation, help with recruiting, company retreat, etc.)Developer 1422334
11
Developer 2422233
12
Developer 3553.75555
13
Developer 450002.55
14
Developer 530.750.752.2533
15
Total219.758.512.2516.520
16
17
Now that you know your team's velocity, this section is all about dividing your major projects up over your sprints.ProjectPlanning Period TotalsSprint 1Sprint 2Sprint 3Sprint 4Sprint 5Totals
Difference from plans
18
Use this row to make note of anything you have to do *every* sprint. For us, these are thigns like 1 pt of a production issue, 1 pt for selenium testing, etc. Add up the total number of points you'll spend on these things each sprint, and put each sprint's total in D17-H17.Spoken for
1 pt PROD
1 pt Selenium/Regression Testing
Urgent support issues
1944344190
19
This row now shoes you the points you have each sprint to work on other things. Hooray!Available pts485.754.59.2512.516n/an/a
20
Use these rows to plan out how many points you'll spend on each project each sprint. First, put the total point estimate for a project in column C to help you remember the total. Then, spread that number of points out in columns D-H in a way that makes sense for your team (for example, if you've broken down the project into stories, you might put the point values for various stories that you want to accomplish each sprint in columns D-H).Project 17.50304.507.50
21
Project 221.584.505421.50
22
Project 338.50022610-28.5
23
Project 435013.1252713.125-21.875
24
Column I now shows you the total # of points you'll be spending for a given project over the whole planned period. If that total differs from the original estimate, you'll see that difference in column J. If column J is negative, you're in trouble - you're not going to complete the project in the alotted time.Bugs7.50002.557.50
25
This row shows you the total points you'll spend during each sprint.Total1291212.58.125202678.625-50.375
26
This row shows you if you'll be spending more or less points in a given sprint than your team's capacity. If this row is negative, you're overcommitted.Difference from available points-41-2.25-44.125-3.5-6
27
28
This section shows you how much of your actual effort over the course of the planned period goes to various projects (assuming you stick to the points allocated to a given project for a given sprint in C17:H23.Project
% of Cumulative
Velocity
29
Spoken for24.17%
30
Project 19.54%
31
Project 227.34%
32
Project 312.72%
33
Project 416.69%
34
Bugs9.54%
35
Total100.00%