oxbshw Sprint Planner
When to use
- Start of a sprint cycle
- After a re-prioritization mid-cycle
- When intake outpaces capacity and you need a defendable plan
When NOT to use
- Daily standup (different cadence)
- Annual planning (different scope; use
roadmap-synthesizer)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
tickets |
list / path | yes | candidate work items with priority + estimates |
capacity |
object | yes | per-engineer days available |
previous_carry |
list | no | items rolling over from last sprint |
commitments |
list | no | OKR / stakeholder commitments that must land |
Outputs
sprint-plan.md with: Sprint goal, Committed, Stretch, Non-goals, Risks.
Workflow
- Compute total capacity (days × team)
- Sort candidates: committed → carry → stretch
- Pack to ~85% of capacity (leave room for support / interrupts)
- Identify dependencies between items; surface blockers
- Surface explicit non-goals — what we are not doing this sprint and why
- Risks: anything that would cause spillover
References
references/sprint-plan-template.md
Success criteria
- Committed work ≤ 85% of capacity
- Every committed item has an owner and an estimate
- Non-goals section is non-empty
- Risks include at least one "what could derail us"
Failure modes
- Capacity unknown → ask, don't guess
- Tickets without estimates → flag and exclude from "committed"