/

Templates / Projects and agile

Scrum meeting (sprint planning)

Scrum meeting template for sprint planning

Scrum has five events: the sprint itself, which contains sprint planning, the daily scrum, the sprint review and the sprint retrospective. Sprint planning needs the most structure on paper, because it should end with a sprint goal, the backlog items the developers select for the sprint, and their plan for delivering them. This template records capacity, the goal, the selected items, risks and what was left out.

Looking for the 15-minute daily scrum? Use the daily standup template. This page is for sprint planning.

Best forScrum teams, typically 10 or fewer people including the product owner and scrum master

Meeting lengthAt most 8 hours for a one-month sprint; for shorter sprints the Scrum Guide says it's usually shorter

SectionsLast sprint result, capacity, sprint goal, selected backlog items, plan for delivering the items, risks, not taken in

FormatsGoogle Docs, Word, Notion, Markdown

Word Markdown

Sprint planning notes: Sprint [number].docx

Sprint planning notes: Sprint [number]

SprintNumber and datesDate Attendees Notes by

Last sprint result

Goal met or not. Completed points or items. What carried over and where the product owner ranked it.

Capacity

Person	Days available	Note
		Leave, on-call, holidays

Total person-days, and what the team completed last sprint

Sprint goal

One or two sentences: why this sprint is worth doing

Selected backlog items

ID	Item	Estimate	Starts with	Still unclear
				Question, and who answers it

Plan for delivering the items

Who does what, which day

Risks and dependencies

Risk or dependency	Owner	Next step

Discussed but not taken in

Item, and why it was left out

Action items

Item	Owner	Due

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Word Markdown

Scrum meeting agenda: sprint planning.docx

Scrum meeting agenda: sprint planning

Sprint Date TimeAt most 8 hours for a one-month sprint, usually shorterFacilitatorScrum masterAttendeesProduct owner, developers, scrum master

Item	Owner	Time	What we need to leave with
Last sprint result and carry-over	Scrum master	10 min	Carry-over items back in the product backlog, re-ranked
Capacity for this sprint	Developers	10 min	Agreed person-days available
Why: proposed sprint goal	Product owner, then the whole scrum team	15 min	A sprint goal the whole team agrees on
What: select backlog items	Developers with the product owner	40 min	Items pulled in, each estimated and clear enough to start
How: plan the delivery, first items in detail	Developers	30 min	A plan the developers own, with work for the first days broken down
Confirm goal, risks and read-back	Scrum master	10 min	Final sprint goal, each risk with an owner

The other scrum events

Event	When	Timebox (Scrum Guide, for a one-month sprint)	What it produces
Daily scrum	Every working day, same time and place	15 minutes, whatever the sprint length	A plan for the next day, blockers raised
Sprint review	End of the sprint	At most 4 hours, usually shorter for shorter sprints	Feedback from stakeholders, an updated product backlog
Sprint retrospective	After the review, before the next planning	At most 3 hours, usually shorter for shorter sprints	One or two improvements for the next sprint
Backlog refinement	Ongoing, often one session mid-sprint	No set length (an activity, not a scrum event)	Items ready for the next sprint planning

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Quillfield invoicing team, Sprint 14 planning

Filled-in example

Quillfield invoicing team, Sprint 14 planning

SprintSprint 14, Monday Nov 16 to Friday Nov 27, 2026 (office closed Nov 26 and 27)DateMonday, November 16, 2026, 10:00 to 11:50 amAttendeesAna Ferreira (product owner), Jonah Pike (scrum master), Ines Coleman, Ray Okoye, Mei Lindqvist, Tobi Adeyemi, Carla BostNotes byTobi Adeyemi

Last sprint result

Sprint 13 goal (freelancers can send invoice reminders automatically) was met. 21 of 23 points done. QF-212, the Spanish reminder email copy, carried over. Ana ranked it third in the product backlog.

Capacity

Person	Days available	Note
Ines	8	Office closed Nov 26 and 27
Ray	6	Also off Nov 19 and 20
Mei	8
Tobi	7	On call Nov 16 to 20, counting one day lost
Carla	8

Total 37 person-days. Sprint 13 had 46 person-days and finished 21 points, so roughly 17 points is realistic this time.

Sprint goal

Freelancers can take a card payment on an invoice and see it marked paid without refreshing the page.

Selected backlog items

ID	Item	Estimate	Starts with	Still unclear
QF-230	Pay by card button on the invoice page	5	Mei	Which card brands at launch? Ana to confirm.
QF-231	Payment webhook marks the invoice paid	5	Ray
QF-235	Payment receipt email	3	Ines
QF-238	Paid status updates live on the invoice list	3	Tobi	Polling or push? Spike Tuesday morning.
QF-212	Spanish reminder email copy (carried over)	2	Carla	Translation due from the agency Nov 18

Plan for delivering the items

Ray: payment provider test account and webhook endpoint, Monday and Tuesday
Mei: card form layout, pairs with Ray Wednesday on the handoff to the webhook
Tobi and Ines: 30-minute spike on polling vs push, Tuesday 9:30 am
Carla: chase the translation agency Monday, then help Ines with receipt email templates

Risks and dependencies

Risk or dependency	Owner	Next step
Payment provider hasn't approved the live account yet	Ana	Contact provider support Monday afternoon. If not approved by Nov 18, the goal changes to test mode only.
18 points selected against a realistic 17 in a short sprint	Jonah	QF-212 is the first item to drop if needed
Translation arrives late	Carla	Ask the agency for a firm delivery date

Discussed but not taken in

QF-240 Partial payments: too big, needs splitting at refinement on Nov 19
QF-226 Dark mode for invoices: Ana moved it down after this month's customer calls

Action items

Item	Owner	Due
Confirm card brands for launch	Ana	Nov 17
Get a delivery date from the translation agency	Carla	Nov 17
Add QF-240 to the Nov 19 refinement session	Jonah	Nov 18

Quillfield and everyone on its invoicing team are a fictional sample.

Best forScrum teams, typically 10 or fewer people including the product owner and scrum master

Meeting lengthAt most 8 hours for a one-month sprint; for shorter sprints the Scrum Guide says it's usually shorter

SectionsLast sprint result, capacity, sprint goal, selected backlog items, plan for delivering the items, risks, not taken in

FormatsGoogle Docs, Word, Notion, Markdown

What to write in each section

Last sprint result

Was the last sprint goal met, and what carried over. Unfinished items go back to the product backlog for the product owner to re-rank. They don't roll into the new sprint automatically.

Capacity

Working days per person after holidays, leave and on-call duty. Use last sprint's completed points or item count as a sanity check, not as a target.

"37 person-days, two fewer days for Thanksgiving" beats "about the same as usual".

Sprint goal

One or two sentences on why this sprint is worth doing. The product owner proposes how the product could increase its value, and the whole scrum team then works out the sprint goal together. If the items selected don't serve the goal, change one or the other.

Selected backlog items

Items pulled from the top of the product backlog, each with an estimate and a note on anything still unclear. The developers decide how much fits, not the product owner.

Plan for delivering the items

How the developers will turn the selected items into a done increment. The Scrum Guide says this is often done by breaking items into pieces of work of one day or less, and how is up to the developers. Plan the first items in detail so people can start the next morning; the rest of the plan gets worked out during the sprint.

Risks, and items not taken in

Dependencies on other teams, people who are out, and the items discussed but left out. Stakeholders should hear what's not coming now, not at the sprint review.

When to use this template

Sprint planning turns into a long estimating session and still ends without a sprint goal.
The team takes on more than it finishes, sprint after sprint.
You're new to scrum and want a written agenda for each event, starting with planning.

Questions people ask

Is a scrum meeting the same as a daily standup?: People often say "scrum meeting" when they mean the daily scrum, the 15-minute event for the developers. Scrum has five events: the sprint itself and the four inside it (planning, daily scrum, review and retrospective), and sprint planning is where most decisions get made. For the daily one, use the standup template linked at the top of this page.
Who runs sprint planning?: The Scrum Guide makes the scrum master responsible for making sure the event takes place and stays within its timebox; many teams also have the scrum master facilitate. The product owner brings the ordered backlog and proposes how the product could increase its value. The developers select the items, with the product owner, and decide how they'll do the work.
Is backlog refinement a scrum event?: Not officially. The Scrum Guide treats refinement as an ongoing activity, but most teams hold one refinement session per sprint so items arrive at planning already understood and estimated.

Sources

The Scrum Guide (November 2020)Defines the Scrum events and their maximum timeboxes, and the Daily Scrum as a 15-minute event for the Developers, who choose its structure.

Related templates

Daily standup meeting templateSoftware, operations and project teams of 3 to 10 working toward a shared goalAgenda · Template · Example

Backlog refinement meeting agendaScrum and agile teams, once or twice per sprint, product owner plus developersAgenda · Template · Example

Retrospective meeting templateAgile teams after each sprint, and any team after a project, launch or incidentAgenda · Template · Example