How to Estimate Stories the Right Way

Story points, Fibonacci, t-shirts, hours — everyone has an opinion on how to estimate. But most teams are either doing it wrong, skipping it entirely, or worse — using it as a weapon against their developers. In this episode, Alex sits down with 20-year product veteran Marc Brickley to break down the real purpose of estimation, when each method actually works, and the secret fuzzy math that senior product managers use to scope massive initiatives without losing their minds. If you've ever sat in a planning session wondering what the point of all this estimating is — this one's for you. 👉 What we cover: 👕 T-shirt sizing vs. story points vs. hours — when to use each and why 🗺️ Why roadmap-level estimates should always stay high level 🍚 RICE scoring — how to prioritize using reach, impact, confidence & effort 🗣️ Why the real value of story pointing is the CONVERSATION not the number ⚠️ What "weaponizing story points" means and why management does it wrong 🧠 The psychology of developers and why they hate asking for help 📈 Velocity — the metric managers should almost never be looking at ⏰ Parkinson's Law — why your task takes exactly as long as you give it 🔮 The fuzzy math method for estimating massive multi-sprint initiatives 🎯 Projections vs. plans — the crucial difference between agile and waterfall thinking 🤝 Why trust is the foundation of every good estimation process 🤖 How AI is already starting to change the timeline of sprints 🔗 Check out Marc Brickley's blog The Product Ref — link below! 💬 Do you use story points on your team? Love them or hate them? Tell us in the comments! 👍 Like, Subscribe, and share with your scrum masters and product owners! Follow Marc on Medium:   / marcbrickley   Connect with Marc on LinkedIn:   / marc-brickley   Check Out Clear Path: https://www.moserlabs.work/clear-path