Sprint Planning

Choose the next iteration on purpose. A sprint plan is a capacity-constrained bet, not a wish list.

Context

Sprint planning turns a backlog of valid work into a realistic short-horizon commitment. It is where business priority, engineering capacity, and delivery risk are forced into one explicit decision.

In Prodcraft, sprint planning should consume actual task, estimate, and risk artifacts. If it runs on optimism or memory, the system has already lost planning discipline.

Inputs

• task-list -- Candidate work for the iteration.
• estimate-set -- Size and confidence data for each task.
• risk-register -- The risks that should constrain commitment or sequencing.

Process

Step 1: Start From Capacity, Not Desire