Sprint Planning Template for Two-Week Sprints
Two-week sprints are the most common cadence for product teams. They are long enough to deliver meaningful work but short enough to maintain feedback loops.
Use this template at the start of every sprint to ensure the team commits to the right amount of work with clear priorities.
Template sections
5 sections covering the complete sprint planning workflow.
Capacity Calculation
Calculate available capacity: take each team member available days (10 working days minus PTO, holidays, on-call duties), multiply by their daily capacity in story points, and sum the team total. Plan to 70-80% of this number.
Sprint Goal
Define one clear sprint goal: By the end of this sprint, users can [outcome]. The goal is not a list of tickets; it is the user or business outcome that the sprint delivers.
Story Selection and Ordering
Pull stories from the top of the prioritized backlog until you reach 70-80% of capacity. Order by dependency and then by priority.
Mid-Sprint Checkpoint
Schedule a 15-minute mid-sprint checkpoint on day 5. Review the burndown: is the team on pace? This prevents surprises at the sprint review.
Carry-Over Protocol
Stories not completed by sprint end move to the next sprint backlog. Track carry-over rate as a planning health metric: above 20% indicates chronic over-commitment.
Copy-paste template
# Sprint [Number] Planning — [Date Range] ## Sprint Goal [One sentence outcome] ## Capacity | Team Member | Available Days | Points/Day | Capacity | |---|---|---|---| | [Name] | [X]/10 | [1.5] | [X] | ## Selected Stories | ID | Story | Points | Owner | Dependencies | |---|---|---|---|---| | [T-1] | [Story] | [3] | [Name] | [None] |
Frequently asked questions
Generate instead of filling in templates
Connect your tools, and Vantage generates the content using real product data. Free to start.
Free to start. No credit card required.