Free Sprint Planning Template
One sprint, from the preparation the planning meeting needs to the review and retrospective that close it. Refine the backlog and work out the team's real capacity first, agree the goal and choose the work that fits, then run the sprint and close it with the numbers the next planning meeting will use.
No credit card. Opens as a real project on the Free plan.
The spreadsheet is a 11-task plan with phases, durations and milestones, ready for Excel or Google Sheets. It carries no dates, so set your own start, or paste it into the Gantt chart generator to have the schedule built for you. Want to compare the plans side by side first? Every one of them is on the project plan template page, with the rows shown before you download.
The Microsoft Project file (.xml) is the same plan with its dates worked out: every task is scheduled from Monday 4 January 2027. Open it in Microsoft Project, or open it free in Onplana Schedule, the desktop app that edits Project files without Microsoft Project.
What’s inside
All 11 tasks are below, in four phases, each with its description, duration and priority. The preparation phase happens in the last days of the previous sprint, so the planning meeting starts the new one on its first morning.
11
Scheduled tasks
4
Phases
4
Milestones
~2
Weeks end to end
Most sprint planning problems are solved before the meeting
A sprint planning meeting goes badly for two reasons: the items at the top of the backlog are not ready, or nobody knows how much the team can take on. This template puts both before the meeting. Refining the backlog means the top items have acceptance criteria and an estimate. Working out capacity means counting the days each person is actually available in the sprint, taking off leave and the meetings that do not move, and comparing that with what the team finished in recent sprints.
The meeting itself then has a short job. The product owner proposes a sprint goal, the team pulls items from the top of the backlog until the capacity is used, and each item is broken into tasks small enough to finish in a day or two. For a two-week sprint that takes about two hours. The goal matters more than the list: when something unexpected arrives mid-sprint, the goal is what the team uses to decide what gives.
The sprint closes with a review of what was built, a retrospective that agrees one change for the next sprint, and a record of the velocity and the unfinished items. Those last numbers are the input to the next planning meeting, which is how the plan gets more accurate sprint by sprint. For a whole project of several sprints, the agile project template lays them out end to end; this one is the single sprint in detail.
The plan, phase by phase
Before Planning3 tasks
Refine the top of the backlog
The items likely to be chosen each get acceptance criteria and an estimate, with questions answered before the meeting.
Work out the team's capacity
Days available per person in the sprint, minus leave and fixed meetings, checked against the velocity of recent sprints.
Draft a sprint goal
The product owner writes one sentence on what this sprint should achieve, to propose at the meeting.
Sprint Planning Meeting2 tasks
Agree the goal and choose the work that fits
About two hours for a two-week sprint. Confirm the goal, then pull items from the top of the backlog until the capacity is used.
Break the chosen items into tasks
Tasks of a day or two each, with an owner, put on the board so progress is visible from the first day.
The Sprint3 tasks
Build the sprint backlog items
Rename or split this into the items chosen at planning. Each one meets the definition of done before it counts.
Hold the daily stand-up
Fifteen minutes each day on progress toward the goal and anything blocking it, not a status report to a manager.
Refine the next sprint's backlog
An hour mid-sprint with the product owner, so the next planning meeting starts with ready items.
Close the Sprint3 tasks
Hold the sprint review
Show the working result to the people who asked for it, and put their feedback into the backlog.
Hold the retrospective
What helped, what got in the way, and one change the team will make in the next sprint.
Record velocity and carry over what is left
What was finished, what goes back to the backlog, and the velocity the next planning meeting will use.
Milestones
Four milestones: the backlog ready for planning, the sprint planned, the sprint review held and the sprint closed. Copy the file once per sprint and the milestones line up on a two-week rhythm.
Backlog ready for planning
Day 4 of the plan
Sprint planned
Day 6 of the plan
Sprint review held
Day 15 of the plan
Sprint closed
Day 17 of the plan
Frequently asked
What is in the download?
A CSV file with the 11 tasks of one sprint, each with its phase, duration in days, priority and notes, and the four milestones as zero-day rows. Excel opens it directly and Google Sheets imports it. Copy it once per sprint.
How do I work out the team's capacity?
Count the days each person is available in the sprint, take off leave, holidays and fixed meetings, and add them up. Then compare the total with what the team finished in its last three sprints, and plan to the lower of the two. New teams with no history should plan light and adjust after the first sprint.
How long should sprint planning take?
About an hour per week of sprint, so two hours for a two-week sprint. If it takes longer, the backlog was not ready: the preparation tasks in this template are there to keep the meeting short.
How is this different from the agile project template?
The agile project template lays out a whole nine-week project: a setup sprint, three delivery sprints and a release sprint. This template is one sprint in detail, from the preparation before planning to the retrospective. Use the agile project template to plan the project and this one to run each sprint inside it.
Start with the plan already built
Open the Sprint Planning template free and your phases, tasks, and milestones are scheduled before the kickoff meeting. No credit card, no time limit.