sprint-planning

To plan a sprint accurately, you estimate team capacity by adjusting for PTO and meetings, then scope backlog items against that availability to set clear goals. This generates a structured plan with a capacity table and definition of done.

Scoping a backlog against team availability involves prioritizing items, sizing them relative to capacity, and identifying dependencies. This ensures the sprint plan aligns with realistic team throughput and produces clear success criteria.

Handling carryover work when kicking off a new sprint involves assessing unfinished items, re-evaluating their priority against current capacity, and integrating them into the new sprint plan. This ensures dependencies are managed and the definition of done is maintained.

Yes, you can generate a structured sprint plan document that explicitly includes sprint goals, a capacity table, backlog items, identified dependencies, and a definition of done for execution. This document consolidates all core planning outputs.

Yes, sprint planning explicitly works for managing dependencies and risks alongside capacity estimation. It scopes work by identifying dependencies and risks while simultaneously sizing the backlog against team availability.

Defining success criteria when sizing a backlog ensures the sprint plan has clear goals guiding prioritization. This prevents overcommitting team capacity and aligns the definition of done with the expected execution outcome.