Sprint Planning
Sprint #: [Sprint 25]Sprint Dates: [June 17, 2025 – June 30, 2025]Facilitator: [Scrum Master / PM]Attendees: [List team members]
🎯 Sprint Goal
State the single most important outcome for this sprint.Ex: Deliver MVP for new onboarding flow with full tracking implemented.
📊 Capacity Planning
Team Member
Days Available
Planned PTO
Notes
[Name]
[#]
[#]
[Notes]
Use this section to calculate total team capacity for the sprint.
🔎 Review Backlog Candidates
Add only groomed, well-defined stories that meet the Definition of Ready.
🚩 Dependencies / Risks
Awaiting API update from external team.
Design review scheduled for June 19.
🔧 Stretch Goals (If Capacity Allows)
Polish account settings UI
Start investigation on search speed optimization
📝 Open Questions
Final decision on tracking implementation method.
Confirm QA resource availability.
✅ Sprint Commitments
Finalize the list of tickets committed for this sprint based on capacity and team discussion.
📎 Linked Docs
[Backlog Board Link]
[Design Files]
[Product Requirements Doc]
How to use:
PM / Scrum Master fills out pre-planning
Team reviews and adjusts during planning meeting
Finalize Sprint Commitments before closing
Table
Backlog Item
Description
Priority
Estimation (Story Points)
Owner
Notes
US-1234 New onboarding flow High 8 Ethan Roberts Dependent on design
BUG-456 Fix payment page error Medium 3 Ava Miller Quick fix
