The Agile Estimation Mistake 90% of Teams Are Making

Story points or hours? Planning poker or just picking a number and hoping for the best? In this episode, Alex and Atlassian expert Jimi Wikman go head-to-head on one of the most debated topics in agile estimation. Jimi is coming in HOT with the opinion that story points are pointless, and the real conversation around why most teams fail at estimation isn't about the method it's about the requirements. Whether you love story points or hate them, this conversation will make you rethink everything. 👉 What we cover: 🔥 Why Jimi thinks story points are completely pointless (and why Alex disagrees) ⏱️ Hours vs. story points — which one actually helps your team deliver? 📋 The 3 things every requirement MUST answer before estimation even starts 👕 When t-shirt sizing is the right tool and when it isn't 🃏 Planning poker — great conversation starter or complete waste of time? 🧠 How experienced developers read between the lines of a requirement 🤖 How AI is completely changing the estimation equation 🐛 Should bugs have story points? What about incidents? 📌 Spikes — should you estimate them and how do they fit in a sprint? 🎯 Why acceptance criteria upfront = better estimates every time ⚠️ The hidden reason teams give astronomical story point estimates 💸 Why poor estimation isn't just a team problem — it's a management problem 🔄 When does a requirement end and a user story begin? 💬 Are you team story points or team hours? Drop your hot take in the comments! 👍 Like, Subscribe, and stay tuned — spikes vs. subtasks vs. workflow statuses is coming next!