PM Sprint Planning Guide
(2026 Edition)
6-step sprint planning agenda, 6 story writing rules, and the 6 anti-patterns that turn good teams into scattered ones.
Practice Execution Skills Daily — Free →6-Step Sprint Planning Agenda
1. Review last sprint (10 min)
What shipped, what slipped, why. One-line retro.
2. Align on sprint goal (10 min)
ONE primary outcome for this sprint. Not 5 goals.
3. Walk through ranked backlog (20 min)
Top items explained in enough detail to estimate.
4. Capacity estimation (15 min)
Engineering + design estimate each item. PM holds scope, not pressure.
5. Commit (10 min)
Decide what goes in. Leave 15–20% buffer for surprises.
6. Dependency + risk scan (5 min)
What could block this sprint? What's waiting on another team?
6-Part Story Writing Template
Title: verb + noun ('Add dark mode toggle')
User story: As a [persona], I want [action], so I can [outcome]
Acceptance criteria: 3–5 testable conditions — QA should be able to write tests from these
Out of scope: what this ticket does NOT include
Design link: Figma or mockup if relevant
Dependencies: what's needed from other teams or systems
6 Sprint Planning Anti-Patterns
Planning for 100% capacity — every sprint has surprises; plan for them
Multi-goal sprints — 1 sprint goal = focus; 5 goals = chaos
Skipping story writing — vague tickets become mid-sprint arguments
PM over-specifying HOW — tell engineering WHAT, let them own HOW
Committing to features without clear acceptance criteria — quality suffers
Running sprint planning longer than 90 minutes — you're doing it wrong
FAQ
How long should sprint planning take?
60–90 minutes for a 2-week sprint. Less and you haven't actually planned; more and you've wasted the team's time on discussion that should have happened async. The quality of sprint planning depends on pre-read preparation: a well-written backlog, clear next-up items, and engineering-ready stories.
What's the PM's role in sprint planning?
Facilitate, don't estimate. PMs own the backlog, the goal, and the WHAT. Engineering owns the estimates and the HOW. PMs who push back on estimates ('can't you do it faster?') erode trust; PMs who facilitate explicit trade-offs ('if we include X, we'd defer Y — is that the right call?') build trust.
Should PMs attend daily standups?
Yes — but briefly and non-interrupting. Standups help PMs stay aligned on progress and unblock fast. PMs who skip standups lose connection with reality; PMs who dominate standups make them boring for everyone. The balance: attend, listen, speak only if asked or if you have a quick decision to unblock someone.
Build PM Execution Skills Daily
Daily scenarios on sprint trade-offs, scope, and stakeholder alignment.
Start Free Trial →