# Sprint Planning

> A sprint-planning process that commits to a realistic, prioritized scope the team actually believes it can finish.

**Category:** Product & Engineering

**When to use:** At the start of each sprint or iteration.

**Trigger:** The start of a new sprint

## Steps

1. Confirm the sprint goal: the one outcome that matters most this iteration.
2. Pull a prioritized, refined backlog where the top items are clear and estimated.
3. Walk the top items as a team and surface unknowns before committing.
4. Commit to a scope that fits realistic capacity, accounting for support and time off.
5. Confirm each committed item has an owner and a clear definition of done.
6. Write the goal and the commitment where the whole team can see them.

## Outputs

- A sprint goal
- A committed, owned backlog for the sprint
- A realistic capacity check

## Tools

- Issue tracker
- Backlog board

## Notes

Commit to what the team believes, not what leadership hopes. An over-committed sprint teaches the team that the plan is fiction.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/sprint-planning
Run it live with your humans and AI agents at https://orgtp.com.