Free template

Free sprint planning template with the meeting agenda

A sprint planning meeting sets one goal, checks who is actually available, and commits to the work that fits. This template gives you a timeboxed agenda, a capacity table, the sprint goal, the committed items with owners, and the risks to watch. Copy it or download it as Markdown.

Get the templateDo this with Atrix AI

Free · Markdown · no sign-up

When to use it

Fill it in during the planning meeting, not before it. The capacity table and the goal come first, and the list of work follows from them.

  • Running your first sprint and wanting a meeting that ends on time

  • Planning sessions that run long and end without a clear goal

  • Teams that keep committing to more than they finish

  • Planning around holidays, leave or a teammate shared with another project

The template

The complete template

Everything below is included when you copy or download it. Replace the [bracketed] blanks and delete the guidance lines as you go.

Sprint [number]: [sprint goal in a few words]

Replace everything in [brackets]. Fill the sections in order: capacity before the goal, and the goal before the list of work. If an item does not serve the goal, it waits for the next sprint.

01Sprint at a glance

The facts everyone needs before the meeting starts.

  • Sprint: [Name or number]
  • Dates: [Start date] to [end date]
  • Length: [One week / two weeks]
  • Team: [Names]
  • Facilitator: [Who runs the meeting and keeps time]
  • Review and retrospective: [Date and time]

02Meeting agenda

A timeboxed agenda for a two-week sprint. Shorten each step for a one-week sprint. The facilitator calls time; anything unresolved goes on the risks list.

  • Total time: [About 90 minutes for two weeks, 45 for one]
StepTimeWhoOutput
1. Review the last sprint10 min[Facilitator]What shipped, what carried over, and why
2. Confirm capacity10 minEveryoneThe capacity table below, filled in
3. Set the sprint goal15 min[Product owner or founder]One sentence everyone agrees with
4. Pick the items25 minEveryoneCommitted items that serve the goal and fit capacity
5. Break down the first items15 minOwnersEach first item split into pieces of a day or less
6. Name the risks10 minEveryoneRisks and dependencies, each with an owner
7. Confirm the commitment5 minEveryoneA yes from each person, or a change to the plan

03Capacity

Count days, not hopes. Take out leave, holidays and other commitments, then apply a focus factor for meetings, support and interruptions. A focus factor of 0.6 to 0.8 is common; use what your last sprints show.

  • Team capacity: [Sum of the last column] days
PersonDays availableLeave or holidaysOther commitmentsFocus factorCapacity (days)
[Name][10][1][Support rota, 1 day][0.7][5.6]
[Name][10][0][None][0.7][7]
[Name][10][3][Shared with another project, 2 days][0.7][3.5]

04Sprint goal

One outcome, in one sentence, that a customer or teammate would notice. Not a list of tickets. If the sprint goes badly, the goal is what you protect.

  • Goal: [By the end of this sprint, (who) can (do what)]
  • How we will know: [The check, demo or number that shows it is done]
  • Out of scope: [What we are deliberately not doing this sprint]

05Committed items

Only what serves the goal and fits within capacity. Every item has one owner. Estimate in whatever unit your team uses, and stop adding when the total reaches capacity.

  • Committed total: [Sum of estimates] against capacity of [team capacity]
KeyItemTypeOwnerEstimateServes the goal
[ABC-101][What will be done][Story / Task / Bug][Name][2 days][Yes: how]
[ABC-102][What will be done][Story / Task / Bug][Name][1 day][Yes: how]
[ABC-103][What will be done][Story / Task / Bug][Name][3 days][Yes: how]

06Stretch items

Work you will pick up only if the committed items finish early. Not part of the commitment, and not reported as missed if untouched.

  • [Stretch item, owner]
  • [Second stretch item, owner]

07Risks and dependencies

Anything that could stop the goal: work from another team, a decision nobody has made, a teammate on leave, an unfamiliar system. Each one gets an owner and a next step.

Risk or dependencyLikelihoodImpactOwnerMitigation
[Waiting on design for the settings page][Medium][High][Name][Agree the layout by day 2, or ship the simple version]
[Risk][Low / Medium / High][Low / Medium / High][Name][What you will do, and by when]

08Definition of done

What every committed item must meet before it counts as done. Agree it once and reuse it each sprint.

  • The change is reviewed and merged
  • It works in [staging / production], not only on a laptop
  • Tests cover the new behaviour
  • Anything users see is documented or announced
  • The owner has moved the item to Done

09Before you close the meeting

Check each line out loud. A plan nobody agreed to is a wish list.

  • The sprint goal is one sentence and everyone can repeat it
  • Committed work fits within capacity, with leave taken out
  • Every committed item has exactly one owner
  • Every risk has an owner and a next step
  • The review and retrospective are on the calendar

Atrix AI

Do this with Atrix AI

Atrix AI does not have sprints or cycles. You plan the sprint as a board view: the backlog holds what is not planned, and the board shows what you committed to.

  • Plan the sprint as a board view

    Unplanned work sits in the Backlog status. Move each committed item to To do, give it an owner and the sprint's end date as its due date, then run the sprint across In progress, In review and Done. A milestone can mark the end date, and the Sprint plan project template starts you with two weeks of Sprint goal, Build and Close out groups.

  • Keep the goal and the work together

    Group stories, tasks and bugs under an epic for the sprint goal, set one of four priorities from low to urgent, and switch between the board, timeline, backlog and by-date views of the same work.

  • Let the agent fill the backlog

    The AI agent proposes stories, tasks and bugs from your requirements. They land in the backlog marked as coming from the agent and never go straight into the sprint. People decide what is committed.

FAQ

Questions, answered

What should a sprint planning meeting cover?

A short review of the last sprint, the team's capacity, one sprint goal, the items that serve it and fit within capacity, a breakdown of the first items, the risks, and a final yes from each person. This template has a section for each.

How long should sprint planning take?

A common guide is up to two hours per week of sprint, so up to four hours for two weeks. Most small teams need far less: the agenda here is about 90 minutes for a two-week sprint.

How do I work out sprint capacity?

For each person, take the working days in the sprint, subtract leave, holidays and other commitments, then multiply by a focus factor for meetings and interruptions. Add the results. Use your last few sprints to set the focus factor honestly.

Does Atrix AI have sprints?

No. Atrix AI has no sprint or cycle object and no story points field. You plan the sprint as a board view: committed items move out of the backlog to To do with the sprint's end date as their due date, and a milestone can mark the end of the sprint.

Is the template free?

Yes. Copy it or download it as Markdown without signing up.

Keep exploring

Run the whole company from one place.

Start a 7-day trial of Builder. Bring your team, your calendar and your code when you are ready.

Start 7-day trialSee pricing

7-day trial · card required · cancel anytime