Agile

Sprint Planning: A Step-by-Step Guide With a Free Template

By the Fairlx team · Updated · 8 min read

Short answer

Sprint planning sets a Sprint Goal, picks the backlog items that fit the team's real capacity, and makes a plan to deliver them. Prepare a ready backlog, work out capacity from availability and past velocity, agree the goal first, then pull items until capacity is used. Copy the free template below. In Fairlx you can also hand well-scoped items to an AI agent.

What is sprint planning?

Sprint planning is the event that starts every Scrum sprint. The whole Scrum team — Product Owner, Scrum Master and Developers — answers three questions from the Scrum Guide: why is this sprint valuable, what can be done this sprint, and how will the chosen work get done. The output is the Sprint Backlog: a Sprint Goal, the selected backlog items, and a plan for delivering them.

The Scrum Guide timeboxes sprint planning to a maximum of eight hours for a one-month sprint, and usually shorter for shorter sprints. In practice, a well-prepared team planning a two-week sprint rarely needs anything close to that. Long planning meetings are almost always a sign the backlog was not ready beforehand.

How do you prepare for a sprint planning meeting?

Good planning is mostly done before the meeting. In the days leading up to it:

  • Refine the top of the backlog. The Product Owner and Developers should have discussed, split and estimated enough items to fill roughly one to two sprints.
  • Check items against the Definition of Ready (below). Anything that fails goes back to refinement, not into the sprint.
  • Collect availability. Holidays, time off, on-call rotations, interviews and company events all reduce capacity.
  • Review the last sprint. What carried over, what was unplanned, and what did the retrospective decide to change?
  • Draft a candidate Sprint Goal. The Product Owner brings a proposal; the team shapes it in the meeting.

What is the sprint planning meeting agenda?

This agenda fits a two-week sprint in about two hours. Scale the times to your sprint length and team.

StepTime (2-week sprint)Who leadsOutput
1. Context: product goal, last sprint, carry-over10 minProduct OwnerShared starting point
2. Capacity check10 minScrum MasterAvailable person-days and a points forecast
3. Agree the Sprint Goal15 minProduct Owner with the teamOne-sentence Sprint Goal
4. Select backlog items40 minDevelopersItems that serve the goal and fit capacity
5. Plan the how: break items into tasks30 minDevelopersTasks, owners for the first days, risks
6. Confirm and commit10 minWhole teamSprint Backlog everyone agrees to
7. Start the sprint5 minScrum MasterSprint started in your tool

How do you plan a sprint, step by step?

Step 1: Set the context

Start with where the product is going. The Product Owner restates the Product Goal, reminds the team of anything stakeholders said in the last Sprint Review, and lists items carried over from the previous sprint. Carry-over is not automatically top priority; it competes with everything else.

Step 2: Work out capacity

Capacity is how much work the team can realistically take on, given who is around. Most teams combine two inputs: availability (person-days this sprint) and historical velocity (story points actually finished in recent sprints). See the worked example below.

Step 3: Agree the Sprint Goal

The Sprint Goal is a single objective that gives the sprint a purpose, such as 'Customers can reset their password without contacting support.' Agree it before selecting items, so the goal drives the selection instead of the goal being written to describe a random pile of tickets. A good goal leaves room to negotiate scope if the team learns something mid-sprint.

Step 4: Select backlog items

The Developers pull items from the top of the ordered backlog — the ones that serve the goal first — until the forecast capacity is used. The Product Owner clarifies; the Developers decide how much fits. Leave some slack for bugs and unplanned work rather than filling to 100%.

Step 5: Plan the how

For each selected item, the Developers sketch how they will build it: split stories into tasks or subtasks, spot dependencies and risks, and agree who starts on what for the first couple of days. The plan does not have to be complete — the Daily Scrum adjusts it — but the first few days should be clear.

Step 6: Confirm and start

Read the Sprint Goal and the selected items aloud. Ask each person whether they believe the plan is achievable. If someone does not, adjust now rather than discovering it on day eight. Then start the sprint in your tool so the board, burndown and notifications reflect it.

How do you calculate sprint capacity? A worked example

Imagine a team of five Developers running two-week sprints of ten working days. At full availability that is 5 × 10 = 50 person-days. Over the last three sprints, with everyone mostly present, they finished 30, 34 and 26 story points — an average velocity of 30 points.

This sprint, one person is on holiday for three days and there is a public holiday that affects one person who works in another country. That removes 4 person-days, leaving 46.

  1. Availability ratio: 46 ÷ 50 = 0.92.
  2. Adjusted forecast: 30 points × 0.92 = 27.6 points.
  3. Round down and plan around 27 points of committed work.
  4. Pick one extra small item as a stretch, clearly marked, in case the sprint goes smoothly.

Two notes. First, velocity already includes the team's normal meetings and support load, so do not subtract those again unless something unusual is happening — such as a heavy on-call week. Second, if the last few sprints vary a lot, use a range (for example 24 to 32 points) and plan to the lower end.

How do story points work in sprint planning?

Story points are a relative measure of the effort, complexity and uncertainty in a backlog item. They are not hours. A five-point item should feel roughly as big as five one-point items, and teams often use a Fibonacci-like scale (1, 2, 3, 5, 8, 13) so bigger items get coarser estimates, which reflects real uncertainty.

  • Pick reference stories. Agree on a small, well-understood item as a '2' and compare everything else to it.
  • Estimate together. Planning poker — everyone reveals an estimate at once — prevents anchoring on the loudest voice. The discussion when estimates differ is the valuable part.
  • Split big items. If something estimates above your largest comfortable size (often 8), split it before it enters a sprint.
  • Never compare teams. Each team's points are its own scale; velocity is a forecasting tool, not a performance score.
  • Points are optional. Some teams count items instead and forecast with throughput. It works well when items are similarly sized.

What are the Definition of Ready and the Definition of Done?

The Definition of Done is part of the Scrum Guide: a formal description of the quality an increment must meet. The Definition of Ready is not in the Scrum Guide, but many teams use one as a checklist for whether a backlog item can enter a sprint. Keep both short and visible.

Definition of Ready (example)Definition of Done (example)
Clear title and a description of the user or business needCode reviewed and merged to the main branch
Acceptance criteria written and agreedAutomated tests written and passing
Estimated by the teamAcceptance criteria verified
Small enough to finish within the sprintDeployed to staging (or production, if that is your bar)
Dependencies known, and none blockingDocumentation and changelog updated where needed
Designs or technical notes attached if neededProduct Owner has seen it working

Free sprint planning template

Copy this into a doc, a wiki page or your project tool before each planning meeting. Fill in the bracketed parts.

Sprint planning template
SectionFill in
Sprint[Sprint name or number], [start date] to [end date]
Product Goal[The longer-term objective this sprint moves toward]
Sprint Goal[One sentence: what value will exist at the end of the sprint?]
Team availability[Person-days available] of [person-days at full availability]; absences: [names and dates]
Recent velocity[Points finished in the last 3 sprints] → average [X]
Capacity forecast[Average velocity] × [availability ratio] = [points to plan]
Carry-over[Unfinished items from last sprint, and whether they are still the top priority]
Selected items[Item, points, owner for day one] — one row per item
Stretch item[Optional item if the sprint goes well]
Unplanned buffer[Capacity reserved for bugs and support]
Risks and dependencies[External teams, reviews, releases, unknowns]
Retro actions[Improvements from the last retrospective to apply this sprint]
Agreed by[Team members] on [date]

The same template as a checklist:

  • Sprint name and dates: ____
  • Product Goal: ____
  • Sprint Goal (one sentence): ____
  • Available person-days: ____ of ____ (absences: ____)
  • Velocity, last three sprints: ____, ____, ____ → average ____
  • Capacity forecast in points: ____
  • Carry-over items and decision: ____
  • Selected items with points and day-one owner: ____
  • Stretch item: ____
  • Buffer for unplanned work: ____
  • Risks and dependencies: ____
  • Retrospective actions applied: ____
  • Everyone agrees the plan is achievable: yes / no

What are the most common sprint planning mistakes?

  1. Planning with an unrefined backlog. The meeting turns into refinement and runs for hours. Refine before, plan during.
  2. Selecting items first and writing the goal last. The goal becomes a list in disguise and gives no guidance when trade-offs come up.
  3. Filling to 100% of capacity. Every sprint has surprises. Leave a buffer for bugs, support and learning.
  4. Ignoring availability. Using last sprint's velocity during a holiday-heavy sprint guarantees carry-over.
  5. Letting one person estimate. Estimates from the person who will not do the work, or the most senior voice alone, are less reliable than a team estimate.
  6. Treating the plan as a contract. The Sprint Goal is the commitment; scope can be renegotiated with the Product Owner when the team learns something.
  7. Carrying over by default. Unfinished work should be re-prioritized like any other item.
  8. Forgetting review capacity. Code review and QA are part of the work. If they are always the bottleneck, plan for them explicitly.

How do AI coding agents change sprint planning?

AI coding agents can now take a work item, write code in a sandbox and open a pull request. That does not remove planning; it changes what you plan. A few practical rules:

  • Give agents well-scoped items. Small bugs, contained features and refactors with clear acceptance criteria are good candidates. Vague or cross-cutting work still belongs with people.
  • Your Definition of Ready matters more. An agent cannot ask a hallway question. Clear acceptance criteria, linked context and a known repository make the difference.
  • Plan review capacity. Every agent pull request needs a human reviewer. If the agent produces more PRs, someone has to read them; count that time in your capacity.
  • Track agent items separately at first. Mark which items went to an agent so the team can see what worked before changing velocity forecasts.
  • Keep the Definition of Done the same. Agent-written code meets the same bar: tests pass, review approved, acceptance criteria verified.

For a deeper look at how agents fit into issue trackers and review workflows, read AI coding agents in project management.

How do you run sprint planning in Fairlx?

This section is about our product. In Fairlx, a project holds a backlog of epics, stories, tasks, bugs and issues with story points, and sprints sit inside the project:

  1. Refine the backlog: write acceptance criteria in the work item, add subtasks under stories, tasks, bugs or issues, and estimate with story points.
  2. Check sprint points and velocity in reporting, and the workload report to see how work is spread across people.
  3. Create the sprint, move the selected items in from the backlog, and record the Sprint Goal where the team will see it, such as a project doc.
  4. Track the sprint on the sprint board with statuses from your custom workflow.
  5. On Fairlx Plus, assign a well-scoped item to the agent. It proposes a plan, waits for your approval, codes in an isolated cloud VM, boots a live preview, runs checks and opens a pull request for a person to review.

Honest trade-offs: Fairlx is in beta, there is no one-click importer from Jira or other tools, and the free plan is for personal accounts only — organizations start on Plus at $8 per license a month. Agent work spends the license's included credits; when they run out the agent pauses, while boards and sprints keep working. More in agile methodology in Fairlx.

Frequently asked questions

How long should sprint planning take?

The Scrum Guide sets a maximum of eight hours for a one-month sprint, and usually less for shorter sprints. A prepared team planning a two-week sprint often finishes in about two hours; much longer usually means the backlog was not refined beforehand.

Who attends the sprint planning meeting?

The whole Scrum team: the Product Owner, the Scrum Master and the Developers. The team may invite other people, such as a designer or a specialist, to give advice on specific items.

How many story points should a sprint have?

There is no universal number, because story points are relative to each team. Use your own recent velocity, adjust it for this sprint's availability, and leave a buffer for unplanned work.

What is the output of sprint planning?

The Sprint Backlog: a Sprint Goal, the backlog items selected for the sprint, and a plan for delivering them. The plan is detailed for the first few days and refined during the sprint.

Can an AI agent take items from the sprint?

Yes, in tools that support coding agents, such as Fairlx Plus. Give the agent small, well-defined items with clear acceptance criteria, and plan time for a person to review every pull request it opens.