A shared number is the point of the conversation, not a promise to the calendar.
Start here
Compare Fibonacci, T-shirt sizing, story points, and #NoEstimates. Learn which technique fits your team and why the conversation matters more than the number.
Use in a session
Tick through a session while you run it. Nothing here needs a sign-in.
Distributed teams lose the cues that make estimation work — and replace them with marathon video calls and anchoring bias. Three structural fixes: async voting, refinement before planning, and evidence-based sizing.
Teams answer 'when will this be delivered?' with a metric that was never designed for it. A practical guide to velocity, throughput, cycle time, Monte Carlo, and delivery-system metrics — and when to use each.
Teams don't struggle with technical debt because it's unquantifiable — they struggle because they estimate the wrong thing. A layered guide to choosing the right method for the decision you're actually trying to make.
Teams don't miss sprint goals because the work is unpredictable — they miss them because the planning session ignored who was actually available. A practical guide to velocity-based, available-hours, and hybrid capacity planning.
AI-first disrupters, developer-centric platforms, and enterprise tools are all fighting for the same space. A strategic breakdown of when to choose each — and why your tracker is only half the story.
The number at the end matters. The conversation that produces it matters more. A step-by-step guide to running an honest, structured, and genuinely useful first session.
Two decades of this argument, and teams are still asking the wrong question. A practical guide to when each method helps, when it hurts, and what actually makes estimation work.
AI hasn't broken agile planning overnight — but the pressure it introduces is making familiar practices feel brittle. A reflection on what's changing and where teams are adapting.
Hidden voting, a shared briefing, and the result written back to the tracker.