Sprint Planning Meeting Agenda
Sprint planning is the meeting that starts each sprint, where the whole Scrum team agrees why the sprint is valuable, what it can deliver and how the work will get done. This sprint planning meeting agenda fits a two-week sprint into 60 minutes and produces a sprint goal and a sprint backlog the developers believe in.
Agenda
60 min · 5 parts
- 0:00Last sprint10 minWhat got done, what carried over and what the review and retro changed
- 10:00Sprint goal10 minOne sentence on why this sprint is valuable
- 20:00Backlog25 minPick the items that serve the goal, size them and plan the first tasks
- 45:00Capacity10 minTime off, focus time and dependencies
- 55:00Commit5 minConfirm the goal and the plan, and who starts on what
Free to start. Guests join from a link, no account needed.
- Length
- 60 min
- How often
- On the first day of every sprint, after the previous sprint's review and retrospective.
- Who attends
- The whole Scrum team: the product owner, the developers and the Scrum Master, plus anyone invited to give advice.
- You leave with
- A sprint goal everyone can explain, the backlog items selected to reach it and a plan for the first days of work.
The agenda, part by part
How to run a sprint planning meeting
1. Last sprint
10 minStart where the last sprint ended: what met the definition of done, what didn't, and why. Bring in feedback from the sprint review and the action from the retrospective, because both should shape this sprint. Decide what happens to unfinished work instead of rolling it over by default.
Ask: What did we learn last sprint that should change this one?
2. Sprint goal
10 minThe product owner proposes how the product could become more valuable this sprint, and the team shapes it into one sentence. A good sprint goal describes an outcome, not a list of tickets, so the team can adapt the work and still meet it. Write it where everyone will see it all sprint.
Ask: If we deliver only one thing this sprint, what should it be?
3. Backlog
25 minWalk the top of the product backlog in order and select the items that serve the goal. The developers decide how much they can take on and break each item into tasks of a day or less. If an item isn't clear enough to start, leave it out rather than guess; refining before the meeting keeps this part short.
Ask: Do we understand this item well enough to start it tomorrow?
4. Capacity
10 minCheck the selection against real availability: holidays, support duty, recurring meetings and work that depends on other teams. Use recent sprints as a guide, not a target. If the plan doesn't fit, cut items, not quality or the goal.
Ask: Who is out, on call or shared with another team this sprint?
5. Commit
5 minRead the sprint goal and the selected items aloud and ask whether the developers believe in the plan. In the 2020 Scrum Guide, the commitment is the sprint goal; the selected items are a forecast that can change as the team learns. Close by naming who starts on what tomorrow.
Ask: From one to five, how confident are we in this plan?
Sprint planning questions to ask
- What is the most valuable thing we could deliver this sprint?
- Which items are ready to start, and which need more refinement?
- What does done look like for each item?
- Which dependencies or other teams could slow us down?
- What did we leave unfinished last sprint, and does it still matter?
- How much of our time is already taken by support or meetings?
- What would we drop first if something unexpected comes up?
Example: planning a two-week sprint with a holiday
A team of six plans a sprint with a public holiday and one developer on leave for a week.
Notes
- Last sprint: 7 of 9 items done; search filters carried over.
- Sprint goal: new customers can import their contacts without help.
- Selected: file import, field mapping, error report. Search filters go back to the product backlog.
- Capacity: 9 working days; Kofi out the second week; Sara on support Monday and Tuesday.
- Confidence vote: 4 out of 5. Risk: no test files large enough yet.
Action items
- Ingrid (product owner): confirm import size limits with sales, by Wednesday.
- Mateo: break field mapping into tasks, by the end of tomorrow.
Ways to adapt it
One-week sprints
Use the same sprint planning template in 30 to 45 minutes. Keep the look back to a few minutes and spend most of the time on the backlog.
Refine before you plan
Hold a backlog refinement session a few days before planning so items arrive clear and sized. The backlog part then becomes selection, not discovery.
Three- or four-week sprints
Split the meeting in two: the goal and the selection with the product owner first, then a separate session where the developers plan how they will build it.
Common mistakes
Choosing the backlog first and writing the goal last.
Instead: Agree on why the sprint matters first. A goal written to describe whatever was picked won't guide any decision during the sprint.
Filling the sprint to 100% of capacity.
Instead: Leave room for bugs, support and questions. A plan with some slack is one the team can actually finish.
Refining stories in the meeting.
Instead: Refine the top of the backlog before planning. If an item still isn't clear, move it to a later sprint instead of guessing.
The product owner decides how much fits.
Instead: The product owner brings the priorities. The developers decide how much they can take on and how they will build it.
Run it in Edworking
Your agenda keeps the meeting on time
Start a video meeting from any template. Edworking turns the agenda into the structure of the call, so nobody has to watch the clock.
Live agenda
A timer for every part
Everyone sees the agenda and how long is left in each part, with a clear moment when the meeting moves on.
AI notes
Notes that follow the agenda
AI takes the notes part by part and writes the summary and action items when the call ends.
Tabs in the call
Your work on screen, no sharing
Open docs, tasks and files as tabs in the call. Everyone sees the same thing without anyone sharing a screen.
Guests
Anyone can join from a link
Free to start. Clients, candidates and guests join from a link, with no account needed.
Frequently asked questions
The Scrum Guide sets a maximum of eight hours for a one-month sprint, and shorter sprints usually need less. With a refined backlog, a two-week sprint can often be planned in one to two hours; this agenda fits 60 minutes.
Why the sprint is valuable, captured in the sprint goal. What can be done, meaning the product backlog items the developers select. How the chosen work will get done. Together, the goal, the items and the plan form the sprint backlog.
The whole Scrum team. The product owner brings priorities and proposes the goal, the developers decide what they can deliver and how, and the Scrum Master usually facilitates. The team can invite others to give advice.
A look back at the last sprint, the sprint goal, selecting and breaking down backlog items, a capacity check and a final commitment. Put the goal before the backlog in your sprint planning agenda, so the goal guides what gets picked.
Refinement is ongoing work to clarify, split and size items before they are needed. Sprint planning picks from those ready items and builds the plan for one sprint. Good refinement is what keeps planning short.
More meeting agenda templates
Daily Standup Meeting Agenda
A 15-minute daily check-in on what moved, what's next and what's in the way.
3 parts
Sprint Review Meeting Agenda
Show what the sprint delivered, hear from stakeholders and decide together what comes next.
5 parts
Sprint Retrospective Template
Look back on the sprint together and agree on the one or two things to change.
5 parts