Plan velocity-calibrated sprints

Transform raw backlog into velocity-calibrated sprint plan with goals

PMs and team leads planning sprints that don't overcommit and have clear, measurable success criteria.

• · Sprint duration (1 or 2 weeks)
• · Team size and velocity (story points per sprint)
• · Top 3-5 backlog items or epics
• · Team absences, holidays, events
• · Previous sprint's incomplete items (carry-overs)

• · Sprint goal (outcome-focused)
• · Sprint backlog with prioritized user stories, point estimates, acceptance criteria
• · Capacity plan (team availability breakdown)
• · Sprint planning agenda (2-hour structured meeting)
• · Risk flags and dependencies

• · Historical velocity data or reasonable baseline (20-30 pts for 5-person team)
• · Backlog items have acceptance criteria or are flagged
• · Team availability known (holidays, events)

• · Sprint goal is task-list, not outcome-focused
• · Capacity calculation ignores meetings and focus time
• · Stories estimated 8+ points not flagged for splitting
• · Carry-overs not accounted for in available capacity
• · Acceptance criteria missing or unclear

• · Capacity formula with explicit adjustments (focus hours/day, availability factor)
• · Story point table with clear complexity ranges
• · Recommendation to commit to 80% capacity, not 100%
• · Acceptance criteria required on every story or flagged
• · Velocity trend mentioned in context (one-off vs. pattern)