How to Run a Perfect Sprint Planning Meeting (Step-by-Step)

The 90-Minute Sprint Planning Framework

If your sprint planning takes more than 2 hours for a 2-week sprint, something's broken. Here's the framework we use with our teams.

Before the Meeting (Async Prep)

1. Product owner: Refine and prioritize the backlog. Every story in the top 15 should have clear acceptance criteria.
2. Team: Review the top stories. Come with questions, not just blank stares.
3. Scrum Master: Share a ClockHive comparison link with the meeting time in everyone's local zone. No "wait, what time is that for me?" confusion.

During the Meeting

Minutes 0-15: Set the sprint goal. One sentence that defines success. "Users can reset their password without emailing support."

Minutes 15-60: Walk through stories one by one. Quick clarification questions only. Use Scrum Poker to estimate — everyone votes, discuss outliers, move on.

Minutes 60-80: Capacity check. "We have 45 story points of capacity. We've estimated 52. What do we cut?"

Minutes 80-90: Confirm the sprint backlog and close. Everyone should leave knowing exactly what they're working on Monday morning.

Sprint Planning Checklist ✅

• Backlog refined and prioritized before the meeting
• Clear sprint goal defined
• Every story estimated (use Scrum Poker!)
• Team capacity calculated realistically
• Meeting recorded for anyone who couldn't attend live
• Timezone-friendly time chosen (use ClockHive Meeting Planner)