Estimation techniques, backlog refinement, and planning strategies.
I know this has been discussed a million times, but I'm seeing a new trend at my org. Leadership is pushing us back to hourly estimates because "story points aren't predictable enough." Here's my argument for keeping story points: 1. They measure complexity, not time — which is what actually matters for capacity planning 2. They reduce sandbagging (people pad hourly estimates) 3. Velocity stabilizes over time and becomes MORE predictable than hours 4. They force conversations about scope and complexity What's your go-to response when leadership pushes back on story points?
Our sprint planning used to be a marathon. Here's what changed: **Before:** PO presents every story cold, team asks questions for the first time, estimates take forever. **After:** 1. **Continuous refinement** — 2x 30-min sessions per week 2. **Pre-read** — PO shares stories 48 hours before planning 3. **Definition of Ready** — stories must meet DoR or they don't enter planning 4. **Confidence voting** — instead of debating each story, we do a quick confidence vote. Only discuss if there's disagreement. 5. **Sprint goal first** — we align on the goal before picking stories Result: 90-minute planning sessions, higher team satisfaction, better sprint goals.