reph

Templates · Product

Sprint planning template

Sprint goal, team capacity, committed and stretch items, carry-over, risks and a definition of done

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

A team is about to start a sprint and needs one agreed page for the goal, what fits in capacity and what does not

Who it's for

Product managerEngineering managerTech leadEngineer

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Sprint 42 planning: Payments team

Author: Marta Lindqvist · Date: 2026-10-05
Team Cascade Payments
Sprint 42
Dates 2026-10-06 to 2026-10-17
Planning facilitator Marta Lindqvist

Sprint goal

Customers on annual plans can switch to monthly billing themselves, without a support ticket.

Velocity & capacity

Capacity is down about 15% because Tomas is on call in week two and Aisha is out for two days.

Avg velocity (last 3)
34 pts
Capacity this sprint
38 days
▼ -15%
Committed
29 pts
Person Available days Time off / other duties Focus
Aisha Bello 8 2 days leave Plan switch API
Tomas Keller 6 On call week 2 Proration logic
Lin Zhou 10 Billing settings UI
Ravi Menon 9 1 day hiring panel QA and migration
Marta Lindqvist 5 Half time on planning Copy, support briefing
Total 38

Committed

Item Owner Estimate Goal link
PAY-311 Plan switch endpoint (annual to monthly) Aisha 8 Core path
PAY-312 Prorated credit for unused annual term Tomas 8 Core path
PAY-315 Billing settings: "Switch to monthly" flow Lin 5 Core path
PAY-316 Confirmation email with new invoice preview Lin 3 Core path
PAY-318 Audit log entry for plan changes Ravi 2 Required for finance
PAY-319 Help center article and support macro Marta 3 Removes ticket need

Stretch

Item Owner Estimate
PAY-320 Monthly to annual switch (reverse direction) Aisha 5
PAY-302 Retry failed card updates in background Ravi 3

Carry-over

Item Estimate left Why it slipped Plan
PAY-298 Tax ID validation for EU invoices 3 Waiting on the tax provider's sandbox keys Keep out of commitment until keys arrive; Ravi chases Monday

Risks & dependencies

Definition of done

The template

Show the blank template

Sprint planning

Author: [your name] · Date: [date]
Team
Sprint Number or name
Dates Start to end
Planning facilitator [your name]

Sprint goal

One sentence describing the outcome this sprint delivers, so the team can make trade-offs mid-sprint without asking. Not a list of tickets.

Velocity & capacity

Last three sprints' completed points next to this sprint's available capacity. Commit to what capacity supports, not to what you hope.

Avg velocity (last 3)
0 pts
Capacity this sprint
0 days
▲ 0%
Committed
0 pts
Person Available days Time off / other duties Focus
Total

Committed

Items the team agrees to finish. Each one should trace back to the sprint goal.

Item Owner Estimate Goal link

Stretch

Pulled only if committed work finishes early. Not part of the goal and not counted as a miss if untouched.

Item Owner Estimate

Carry-over

Unfinished work from the last sprint, with why it slipped. Repeated carry-over is a signal to split the item or cut scope.

Item Estimate left Why it slipped Plan

Risks & dependencies

What could stop the goal: another team's API, a pending decision, an on-call week, a release freeze. Name who is chasing each.

Definition of done

What every committed item must clear before it counts as finished.

Questions

How many points should we commit?
Your average velocity over the last three sprints, scaled by this sprint's capacity
What is a stretch item?
Work the team will pull only if committed items finish early, never counted against the goal
What happens to carry-over?
It is re-planned like any other item, with a note on why it slipped

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Sprint planning" with search_docs, then read it with read_doc. Draft the goal from the roadmap's Now items, capacity from the team calendar and time-off list, and committed and stretch items from the refined backlog within capacity; put last sprint's unfinished work in Carry-over with a reason. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (unestimated items, blocking dependencies) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Analytics request

Brief for a data or analytics request: the decision it informs, the exact question, metric definitions, segments, timeframe, sources, due date and output format

Product managerResearcherMarketerExecutiveOperationsAnyone

Experiment (A/B) plan

Hypothesis, variants, metrics, sample size and decision rule

Product managerResearcherEngineer

Feature brief

Short brief aligning team on a feature before design

Product managerDesignerEngineer

Launch checklist

Everything to ship a feature: eng, docs, support, marketing

Product managerManager

One-pager

A single-page pitch for an idea: problem, solution, why now

Product managerFounderExecutive

PRD / requirements doc

Problem, users, requirements, success metrics and scope for a feature

Product managerEngineerDesigner

Start with this template →Sign in