nw-leanux-methodologylisted

# LeanUX Backlog Management Methodology "A backlog is not a todo list. It's a collection of validated hypotheses waiting to become working software." ## Story States | State | Meaning | Entry Criteria | |-------|---------|----------------| | Draft | Idea captured, not validated | Has problem statement | | Ready | Validated, has UAT, ready to build | All DoR items complete | | In Progress | Actively being built | UAT test written (RED) | | In Review | Code complete, awaiting review | All tests green | | Done | Merged, deployed, validated | UAT passes in production | | Blocked | Cannot proceed | Blocker documented | ## Story Sizing Criteria ### Right-Sized Completable in 1-3 days | 3-7 UAT scenarios | Delivers demonstrable value | Explainable in 2 minutes ### Oversized Indicators >7 UAT scenarios | >3 days effort | Multiple distinct user outcomes | Cannot demonstrate in single session ### Splitting Strategy Split by user outcome, not technical layer. Each resulting story delivers independently demonstrable value. Example: "User Management" (20 scenarios) splits into: - "Quick Login" (5 scenarios) -- returning customer on trusted device - "New Registration" (4 scenarios) -- first-time customer sign-up - "Password Recovery" (3 scenarios) -- customer who forgot credentials - "Profile Settings" (4 scenarios) -- customer updating preferences ## Definition of Ready (DoR) - Hard Gate Stories pass ALL 8 items before proceeding to DESIGN wave. ### Checklist with Pass/Fail Exa