sprint-planninglisted

# Sprint Planning ## Overview Sprint planning decides which stories enter a milestone and in what order. Input: a list of DoR-approved stories from DISCUSS. Output: a prioritised, capacity-bounded, dependency-resolved sprint plan. A sprint plan answers three questions: 1. **What** enters this milestone? (MoSCoW prioritization) 2. **How much** fits? (capacity check) 3. **In what order?** (dependency sequencing) --- ## MoSCoW Prioritization Assign one MoSCoW label to every story before placing it in a milestone. ### Priority Levels | Level | Label | Definition | Capacity rule | |---|---|---|---| | **Must Have** | `priority/must` | No sprint value delivered without it. Legal compliance, core user journey, removes a blocker. | Must-Haves fill ≤ 60% of sprint capacity. | | **Should Have** | `priority/should` | High value but a workaround exists. Would significantly improve user experience. | Should-Haves fill ≤ 30% of sprint capacity. | | **Could Have** | `priority/could` | Nice-to-have. Easy to cut without impacting the core sprint goal. | Could-Haves fill the remaining capacity. First items cut if overloaded. | | **Won't Have** | `priority/wont` | Explicitly out of scope for this sprint. Documented to avoid re-discussion. | Not scheduled. | ### Application Steps 1. For each story, ask: "Can the sprint goal be achieved without this story?" - No → Must Have - Yes, but degraded → Should Have - Yes, no degradation → Could Have 2. Fill capacity: Must-Haves first,