# Sprint Planning: [Team name], Sprint [NN]

> Sprint Planning starts the Sprint. Following the Scrum Guide 2020 (Schwaber and Sutherland, the current revision as
> of October 2026), the Scrum Team answers three questions: why this Sprint is valuable (the Sprint Goal), what can
> be done (the Product Backlog items selected) and how the work will get done (the plan). Together these form the
> Sprint Backlog. The event is timeboxed to a maximum of eight hours for a one-month Sprint, and is usually shorter
> for shorter Sprints. Capacity and points are common practice, not part of Scrum. Replace every `[bracketed]` value
> and every row marked *Example*.

<!-- Guidance: How to use this template
- Agree the Sprint Goal before selecting the last items; the goal gives the team flexibility in the exact work.
- Only the Developers decide how much they can take on. Use capacity and recent velocity as inputs, not targets.
- The worked example is the fictional Tallow Notes team; item IDs match product/product-backlog.
-->

## Sprint details

| Field | Value |
|---|---|
| Sprint | [NN] (YYYY-MM-DD to YYYY-MM-DD) *Example:* Sprint 34, 2026-11-23 to 2026-12-04 (two weeks, 10 working days) |
| Product Goal | [Link] *Example:* A new team succeeds together in its first week |
| Definition of Done | [Link to product/definition-of-done] |
| Attendees | [Product Owner, Scrum Master, Developers, invited experts] |

## 1. Why: Sprint Goal

<!-- Guidance: One objective, in outcome terms, that a stakeholder would understand. -->

**Sprint Goal:** [One sentence]

*Example:* A team lead can create a workspace from a starter space, edit its pinned notes and invite colleagues from
any note.

## 2. Capacity

<!-- Guidance: Count available days after leave, holidays and other duties. Use it with recent velocity to sanity-check the selection. -->

| Developer | Available days | Notes |
|---|---|---|
| [Name] | [N] | [Leave, support rota] |
| *Example:* Asha | 10 | |
| *Example:* Bram | 10 | |
| *Example:* Chen | 8 | 2 days leave |
| *Example:* Dara | 10 | |
| *Example:* Eli | 9 | 1 day support rota |
| **Total** | [N] | *Example:* 47 of 50 days (94%) |

Recent velocity: [N, N, N] *Example:* 21, 24, 23 (average 22.7). At 94% availability the team plans about 21 points.

## 3. What: selected items

| Order | ID | Item | Estimate | Contributes to Sprint Goal |
|---|---|---|---|---|
| 1 *(Example)* | PBI-101 | Choose a starter space by team type | 5 | Yes |
| 2 *(Example)* | PBI-102 | Edit pinned starter notes in place | 3 | Yes |
| 3 *(Example)* | PBI-103 | Invite colleagues from inside any note | 5 | Yes |
| 4 *(Example)* | PBI-107 | Fix duplicate note after offline edit | 2 | No (guardrail) |
| 5 *(Example)* | PBI-108 | Keyboard focus order on invite dialog | 3 | Yes |
| **Total** | | | *Example:* 18 points | |

PBI-106 (5 points) was left out: taking it would bring the total to 23, above the 21 planned.

## 4. How: plan

<!-- Guidance: Break the first days of work into tasks of one day or less; the rest can be planned as the Sprint goes. -->

| Item | First tasks | Owner(s) |
|---|---|---|
| [ID] | [Tasks] | [@names] |
| *Example:* PBI-101 | Starter content for three team types, selection screen, creation API | Asha, Dara |
| *Example:* PBI-103 | Invite entry point in note menu, reuse invite dialog | Bram |

Risks and dependencies: [*Example:* starter content wording needs review by support by day 3]

## Related templates and references

- product/product-backlog, product/definition-of-done, product/sprint-retro, meetings/standup
- Scrum Guide 2020, section "Sprint Planning": https://scrumguides.org/scrum-guide.html

## Standard and licence note

Structure aligned with the Sprint Planning event of the Scrum Guide 2020 (CC BY-SA 4.0), cited by name only; all
wording is original. Check the current Guide at scrumguides.org. Template licence: MIT.