Blog
Practical guides on agile estimation, Planning Poker and Scrum — from real sessions, not the textbook.
Story Points vs. Hours: Why Teams Estimate Relative Size
Why not just estimate in hours? Because the moment you put a clock on unfamiliar work, you're guessing with false precision. Here's what relative sizing fixes.
Read moreThe Fibonacci Sequence in Planning Poker: Why the Gaps Matter
Why does the deck skip 4, 6 and 7? Because the widening gaps force honesty: the bigger a task, the less precisely anyone can size it. Here's the logic.
Read moreHow to Run a Remote Planning Poker Session That Doesn't Suck
Remote estimation fails in predictable ways — dead air, silent multitasking, one loud voice. Here's how to facilitate a session that stays sharp and quick.
Read moreCommon Estimation Anti-Patterns (and How to Counter Them)
Four ways estimation quietly goes wrong: anchoring, the HiPPO effect, 'just average it', and estimates hardening into deadlines. Here's how to counter each.
Read morePlanning Poker vs. T-Shirt Sizing vs. the Bucket System
Planning Poker, T-shirt sizing, and the Bucket System solve different problems. Here's when each one shines — and how to pick without overthinking it.
Read moreThe Lego City Exercise: Teaching Estimation Hands-On
Reading about story points convinces no one. Building a Lego city on a timer does. Here's the hands-on workshop I use to make relative estimation click.
Read more