sprint-planning

Sprint planning requires scoping work, estimating team capacity against availability, and setting measurable sprint goals. You map your prioritized backlog, including carryover items and dependencies, against available effort to generate a structured plan.

Prioritizing P0 tasks versus stretch goals involves capacity-aware scoping that accounts for PTO and meetings. You clarify mandatory items first, then map stretch work to remaining capacity while calling out dependencies and blockers.

Sizing a sprint backlog with PTO and dependencies requires estimating available effort after calendar constraints. You incorporate carryover items and cross-team blockers into the scope to ensure the sprint plan reflects actual team availability.

Generating a sprint plan document with risks and a definition of done is the core output of capacity-aware planning. The structured plan includes capacity allocation, a prioritized backlog, identified risks, and a definition of done checklist.

Sprint planning works for two-week sprints by pasting your prioritized backlog, listing team availability, and adding carryover or dependency constraints. The output maps scope to capacity for the specified sprint length.

When setting sprint goals and success criteria, avoid overcommitting capacity by ignoring PTO, meetings, and interrupts. Failing to account for cross-team dependencies and carryover items leads to unrealistic backlog sizing and missed goals.