Free template
Sprint planning template
A one-page sprint plan: the goal, who’s available, what’s in, how big each item is, and what could go wrong. Free as a CSV that opens in Google Sheets, Excel and Notion, no sign-up.
Works in Google Sheets, Excel and Notion. Formulas included.
1 · Capacity
| Person | Days available | Notes |
|---|---|---|
| Jonas | 10 | |
| Lena | 10 | |
| Sam | 8 | On call Tue–Wed |
| Ken | 9 | Conference Fri |
| Total | 37 | At 70% focus: 26 dev-days |
3 · Risks and open questions
- Seat limit policy isn’t decided: block, warn or charge?Billing · Wed
- Accepting an invite touches sign-in. Spike it first.Ken · Mon
4 · Definition of done
- Tests pass in CI
- Behind a feature flag
- Support and docs notified
- Demoed to product
2 · Backlog, in dev-days
| Item | Owner | Best | Likely | Worst |
|---|---|---|---|---|
| INV-1Invite modal with role picker | Sam | 1 | 2 | 3 |
| INV-2Invitations API: create, revoke, accept | Ken | 2 | 3 | 5 |
| INV-3Signed invite tokens with expiry | Jonas | 0.5 | 1 | 2 |
| INV-4Accept-invite page, four states | Lena | 1.5 | 2.5 | 4 |
| INV-5Seat limit check | Unassigned | 1 | 2 | 3 |
| Total | 6 | 10.5 | 17 |
Fits: even the worst case, 17 dev-days, is inside the 26 the team has at 70% focus.
What’s in it
What a sprint plan needs, and nothing else.
Sprint goal
One sentence the team can check every decision against.
Capacity
Who’s around and for how long, with time off and on-call taken out first.
Backlog with ranges
Best, likely and worst case per item, so you can see whether the bad case still fits.
Risks and open questions
Each with an owner and a date. An open question without an owner becomes scope creep.
Definition of done
What “finished” means for every item, agreed before anyone starts.
How to use it
How to run sprint planning with it.
The Scrum Guide timeboxes sprint planning to at most eight hours for a one-month sprint, and less for shorter sprints. Filling in capacity beforehand saves most of that time.
- 01Before the meeting: fill in capacity, and have the product owner put the backlog in priority order.
- 02Agree the sprint goal in one sentence.
- 03Pull items in order and estimate each as a range. Stop when the worst case reaches capacity. Use planning poker if the team disagrees.
- 04Write down the risks that came up, each with an owner and a date.
- Sizing the backlog with a remote team? Run planning poker online, no sign-up. Using points for velocity? See how to calculate story points.
- New work arrives after planning? Handle it as a sprint scope change: check it against the goal, size it, and swap something out.
- Shipping at the end of the sprint? The release management template sets the process every release follows.
Skip the blank sheet
Let SprintProof fill it in.
Describe the feature and the AI planner drafts the backlog with ranges. The check library fills in the risks you’d otherwise find mid-sprint, and tasks go straight to Jira or Linear.
FAQ
Sprint planning questions
What should a sprint plan include?
How long should sprint planning take?
Why ranges instead of story points?
How do I open the template in Google Sheets, Excel or Notion?
Related templates
Templates that go with it.
- Markdown, CSV
Software estimate template
Best, likely and worst case per part, rolled up into a range you can defend.
- Markdown
User story template
Who, what and why, with the acceptance criteria and the questions to settle first.
- Markdown
Acceptance criteria template
Given, when, then for the happy path, the edge cases and the states nobody designs.
- Markdown, CSV
Release plan and release management template
Milestones with ranges, dates at 50, 80 and 90% confidence, the rollout steps and a release readiness checklist.
- Markdown
PRD template
The problem, who it is for, what done means, what is out, and the open questions, on one page.
- Markdown
Feature spec and feature description template
A feature broken into parts by layer, each with behaviour, states and a range, and a one-page feature description.
Team
Plan the next sprint with ranges.
Create your account and name your workspace. Your first feature plan is free. To keep planning, subscribe to Team: the 14-day money-back guarantee applies.
Want to hear when the ChatGPT and Codex plugin ships? Leave your email.