Agile

Sprint Planning Template

A high-precision framework for engineering teams to calculate capacity, align on goals, and commit to a 2-week sprint backlog without over-committing.

When to use this template

•When transitioning from ad-hoc task management to structured 2-week Agile sprints.
•Before starting a new development cycle to ensure the team has enough bandwidth for high-priority stories.
•When the team consistently over-promises or under-delivers and needs a data-driven capacity calculation.

How to fill it in

1.Define the Sprint Goal by identifying the single most important outcome for this cycle.
2.Calculate team capacity using the [team_days x focus_factor] formula to set a realistic velocity.
3.Review the refined backlog and move top-priority items into the sprint container based on estimated effort.
4.Confirm the Sprint Backlog matches the capacity and verify that all stories meet the Definition of Ready.

Template preview

Prep Checklist

·Product Backlog Refined
·Stakeholder Feedback Reviewed
·Bugs Triaged and Prioritized
·Team Availability Updated
·Definition of Ready (DoR) Verified

Capacity Calculation

·Engineer Days: 10
·Focus Factor: 0.7
·Target Velocity: 70 Hours
·Buffer for Bugs: 10%
·Net Project Capacity: 63 Hours

90-Minute Agenda

·0-10: Context & Sprint Goal
·10-40: Backlog Deep-Dive
·40-70: Task Breakdown
·70-85: Confidence Vote
·85-90: Final Commitment

Exit Criteria

·Sprint Goal Documented
·Tasks Assigned to Owners
·Dependencies Flagged
·Team Consensus Reached

Copy as Markdown

## Sprint Planning: [Sprint Name/Number]

**Sprint Goal:** [State the primary outcome, e.g., 'Launch V1 of User Billing']
**Duration:** [Start Date] to [End Date] (2 Weeks)

### 1. Capacity Calculation
Use this formula to prevent over-allocation:
- **Total Engineer Days:** [Number of Engineers] x [Working Days in Sprint]
- **Adjusted Days (PTO/Holidays):** [Total Days] - [Days Off]
- **Focus Factor:** [Default 0.7 to account for meetings/admin]
- **Net Team Capacity:** [Adjusted Days] x [Focus Factor]

> **Note:** For a 2-week sprint with 5 engineers and 0 PTO, capacity is typically 70 engineer-days (at 1.0) or ~49 effective days (at 0.7).

### 2. Pre-Planning Checklist
- [ ] Backlog is refined and items at the top have clear requirements.
- [ ] Bug backlog has been reviewed for critical 'must-fix' items.
- [ ] Team availability/vacation calendar is updated.
- [ ] High-level estimates (Story Points or Hours) are applied to the top 15 items.

### 3. Agenda (90 Minutes)
- **00:00 - 00:10:** Review Sprint Goal & Business Context (PO led).
- **00:10 - 00:40:** Select items from the backlog until Net Team Capacity is reached.
- **00:40 - 01:10:** Task breakdown: Engineers split stories into sub-tasks (< 1 day each).
- **01:10 - 01:25:** Dependency Check & Confidence Vote (Fist-to-Five).
- **01:25 - 01:30:** Finalize the Sprint Backlog and move to 'In Progress'.

### 4. Sprint Backlog Artifact
| ID | Task Description | Estimate | Owner |
| :--- | :--- | :--- | :--- |
| [ID] | [Example: API Auth Middleware] | [Size] | [Name] |
| [ID] | [Example: Unit tests for Stripe] | [Size] | [Name] |
| [ID] | [Example: Update documentation] | [Size] | [Name] |

### 5. Ceremony Exit Criteria
- [ ] The Sprint Goal is clearly visible on the dashboard.
- [ ] Every backlog item has an owner and a primary estimate.
- [ ] No single team member is allocated beyond their individual capacity.
- [ ] External dependencies (e.g., Design, DevOps) are confirmed.

---
*Template provided by Planet Roadmap. Scale your engineering team with unlimited projects and no per-seat pricing.*

Use this template inside Planet Roadmap to visualize your sprint on a Kanban board and link every task to your Pro-tier OKRs for full executive visibility.

Skip copy-paste. Set up this template inside a Planet Roadmap project in one click.

Try Planet Roadmap Free

FAQ

What focus factor should a new team use?

If you don't have historical velocity, start with 0.6 or 0.7. This accounts for the 'hidden' time spent on code reviews, meetings, and minor production interruptions.

How long should planning take for a 2-week sprint?

A standard rule of thumb is 1-2 hours of planning per week of sprint. For a 2-week cycle, 2 to 4 hours is typical, though highly refined teams can often finish in 90 minutes.

What happens if the team finishes early?

If the Sprint Backlog is cleared before the end of the 2-week cycle, the team should pull the next highest priority item from the 'Refined' backlog after consulting the Product Owner.

Should bugs be included in the sprint capacity?

Yes. You should either allocate a percentage of capacity (e.g., 10-20%) specifically for bugs or pull specific high-priority bugs into the sprint backlog as individual items.

Related templates