Sprint planning agenda

A sprint planning agenda is the timeboxed run of show for the meeting that opens your sprint: confirm capacity, agree the goal, select the work, and plan enough of it to start. A good agenda does one thing above all — it stops a single item from eating the whole meeting.

Here is an agenda you can run this afternoon, sized for a two-week sprint with a four-hour ceiling. Scale each block up or down with your sprint length.

The agenda

Set the scene — 10 minutes. The product owner recaps the last sprint’s outcome, any change in priorities, and the candidate direction for this one. Short. This is context, not the goal yet.
Confirm capacity — 10 minutes. Establish the team’s real availability: who is on leave, what support or on-call rotation is running, standing meetings, and a realistic buffer for the unplanned. You want the honest number before anyone gets attached to scope. See velocity and capacity planning.
Agree the sprint goal — 20 minutes. Draft one sentence the team can commit to. Do this before selecting items, so scope serves the goal rather than the goal being reverse-engineered from a pile of tickets. See setting a sprint goal.
Select the work — 60 minutes. Walk the backlog from the top. For each item: does it serve the goal, is it ready, is it sized? Pull items until you reach capacity, then stop. Resist “one more small one”.
Plan the work — 90 minutes. Break the selected items into tasks and an approach. Surface dependencies and risks. This is where an item that “looked like a 3” reveals itself — send it back or split it now, not on day nine.
Confirm and commit — 10 minutes. Read the goal and the selected items back. Ask the team, plainly, whether they believe they can finish it. Adjust scope if the answer is soft.

That is roughly three and a half hours with slack. If you are routinely blowing past it, the problem is upstream — the backlog arrived unrefined, and you are doing refinement inside planning.

The two-part shape underneath

The six items above collapse into the two passes every good planning meeting runs: decide the scope, then plan the scope. Items 1–4 are scope — what are we taking on, and why. Items 5–6 are the plan — how, and do we believe it. Keeping the two apart is the difference between a meeting that decides and one that thrashes. The meeting walkthrough chapter goes deeper on why the order matters.

Where the 3-5-3 rule fits

Search for sprint planning structure and you will hit the 3-5-3 rule — a mnemonic for the shape of Scrum itself:

3 roles: product owner, Scrum Master, developers.
5 events: the sprint, sprint planning, the daily scrum, the sprint review, and the sprint retrospective.
3 artifacts: the product backlog, the sprint backlog, and the increment.

Sprint planning is one of the five events, and it is where two of the three artifacts meet — the team pulls from the product backlog to build the sprint backlog. It is a useful map of how the pieces relate. It is not an agenda. Do not confuse knowing the framework with knowing how to run the meeting.

The five stages of a sprint

The other framing people search for is the five stages of a sprint, which map directly onto the five events. The sprint is the container; the other four punctuate it:

Sprint planning opens the sprint and sets the goal.
The daily scrum keeps the team coordinated day to day.
The work happens — building toward the goal.
The sprint review inspects the outcome with stakeholders.
The sprint retrospective improves how the team works, then feeds the next planning.

Planning is stage one, but it does not stand alone — a goal set well on Monday only pays off if the daily scrum defends it and the retrospective sharpens how you plan next time. For the full tour of how the events connect, see the agile ceremonies guide.

Adapt the agenda to your team

The blocks above are a starting point, not scripture. A seasoned team on a one-week sprint might run the whole thing in forty-five minutes because the backlog is always ready and capacity barely moves. A team new to Scrum, or one whose backlog is perpetually raw, will need the full timebox and should invest in refinement between sprints to earn it back.

The invariant is the sequence: capacity, then goal, then scope, then plan, then a genuine check that the team believes it. Change the timings freely. Change the order at your peril.

Ready to run it? The sprint planning template turns this agenda into something you can copy into your tool and fill in as you go.

Frequently asked questions

What is the 3-5-3 rule in Scrum?

The 3-5-3 rule is shorthand for Scrum’s structure: 3 roles (product owner, Scrum Master, developers), 5 events (the sprint, sprint planning, the daily scrum, the sprint review, and the sprint retrospective), and 3 artifacts (the product backlog, the sprint backlog, and the increment). Sprint planning is one of the five events.

What are the five stages of a sprint?

The five stages map to Scrum’s five events: the sprint itself is the container, and inside it sit sprint planning, the daily scrum, the sprint review, and the sprint retrospective. Planning opens the sprint, the daily scrum keeps it on track, and the review and retrospective close it.

How long should the sprint planning meeting be?

About two hours per week of sprint length — four hours for a two-week sprint, up to eight for a month. Treat it as a ceiling. Timebox each agenda item so one debate cannot eat the whole meeting; park anything that turns into problem-solving.

Who attends sprint planning?

The whole Scrum team: the developers who make the forecast, the product owner who brings the goal and ordered backlog, and the Scrum Master who facilitates. Invite a subject-matter expert for one item only if a decision genuinely depends on them, then let them go.