Process Library

Sprint Planning

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

Product & Engineering 6 steps
When to use

At the start of each sprint or iteration.

Trigger
Runs when: The start of a new sprint

The procedure

6 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 trackerBacklog board
Note: Commit to what the team believes, not what leadership hopes. An over-committed sprint teaches the team that the plan is fiction.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
sprint planning sop agile planning process scrum sprint checklist backlog refinement iteration planning

Related SOPs

Product & Engineering
Code Review
6 steps
Product & Engineering
Deploy
6 steps
Product & Engineering
Bug Triage
6 steps
Product & Engineering
Feature Spec
6 steps
← Back to the Process Library