Sprint Planning Meeting Agenda Template (With Timeboxes)
Quick answer
A sprint planning meeting agenda should cover five blocks: sprint goal review (5 min), capacity check (10 min), story estimation and selection (30 min), team commitment (10 min), and a wrap-up (5 min). Total runtime is 60 minutes for a two-week sprint.
Sprint planning is the most consequential ceremony in your sprint. Get it right and the team leaves aligned, energized, and clear on what they are building. Get it wrong and you spend two weeks chasing a moving target. The difference almost always comes down to structure. This guide gives you a battle-tested sprint planning agenda with exact timeboxes you can copy into your calendar invite today.
The Full Sprint Planning Agenda at a Glance
Before diving into each block, here is the complete template: 0:00 - 0:05 | Sprint goal review (5 min) 0:05 - 0:15 | Capacity check (10 min) 0:15 - 0:45 | Backlog estimation and story selection (30 min) 0:45 - 0:55 | Team commitment (10 min) 0:55 - 1:00 | Wrap-up and parking lot (5 min) Total: 60 minutes for a two-week sprint. If your planning routinely runs past 90 minutes, the agenda is not the problem — the backlog is.
Block 1: Sprint Goal Review (5 Minutes)
The sprint goal is the single sentence that gives the sprint meaning beyond a list of tickets. Open every planning meeting by stating it out loud, not by projecting the backlog. A strong sprint goal sounds like: "Customers can complete checkout without leaving the app." A weak one sounds like: "Complete PROJ-112, PROJ-118, and PROJ-120." The former gives the team latitude to make good decisions mid-sprint.
Block 2: Capacity Check (10 Minutes)
Capacity is the number of story points the team can realistically deliver. Subtract planned time off, company holidays, recurring meetings, on-call rotations, and any carry-over work from the previous sprint. A simple formula: take each developer's available days, multiply by a focus factor (0.6 to 0.7 is typical), then convert to story points using the team's historical velocity. Do not skip this step. Teams that skip the capacity check consistently over-commit.
Block 3: Backlog Estimation and Story Selection (30 Minutes)
This is the core of sprint planning. Structure it in two passes. First pass (10 minutes): the Product Owner walks through the top candidates. No estimation yet — just a quick confirmation that everyone understands each story. Second pass (20 minutes): the team estimates stories using planning poker. Each story gets one round of simultaneous card reveal. If there is a spread, the highest and lowest estimators give a one-sentence rationale, then the team re-votes. Cap discussion at 90 seconds per story. Stop pulling stories into the sprint when the cumulative estimate reaches the team's agreed capacity.
Tips for Remote Sprint Planning
Remote sprint planning has one enemy: silence. When the team is distributed, silence looks identical whether someone is thinking hard or has tuned out entirely. Start with cameras on for the first 15 minutes. Use a shared digital board for the backlog so every participant sees the same thing. For estimation, a dedicated planning poker tool beats a spreadsheet or emoji request every time. End every remote planning meeting with a verbal round-robin: each person states the one story they feel least clear on.
What to Do When the Backlog Is Not Ready
The single most common reason sprint planning runs over is a backlog that was not refined before the meeting. When this happens, do a triage in the first five minutes. The Product Owner reads each story title. The team gives a thumbs-up (ready to estimate) or thumbs-down (needs more work). Any story that gets a thumbs-down goes to a refinement session. If fewer than half the stories pass triage, stop the meeting and reschedule for 48 hours later.
What to Do When Planning Runs Over Time
The timebox exists to protect the team. The facilitator's most important tool is the explicit call: "We have five minutes left in this block." For runaway estimation discussions, apply the two-minute rule: if a story has been discussed for more than two minutes without convergence, defer it. If the team routinely needs more than 60 minutes, examine whether you are trying to plan too many stories. A sprint with eight well-understood stories almost always delivers more value than one with fourteen half-understood ones.
Run the estimation portion in under 30 minutes
No account required. Share a link and your team can vote in seconds.
Start a free planning poker session