Of all the Scrum challenges teams raise, estimation is the one that quietly poisons everything else. Get it wrong and the sprint is overcommitted, the burndown lies, and trust with stakeholders erodes. The hard truth behind most Scrum estimation challenges is that story points are a relative measure of complexity — but teams keep trying to use them as a measure of how much will fit, which is really a question of capacity.

Why estimates drift

Three forces pull estimates off course, and they’re well documented in agile circles:

• Cognitive bias. Anchoring to the first number spoken, the halo effect around a senior voice, optimism bias, and groupthink all skew planning poker.
• External pressure. Deadlines, budgets, and stakeholder expectations push teams to estimate the answer they think is wanted rather than the one the work justifies.
• Capacity blindness. A team’s velocity assumes a full sprint. Holidays, PTO, support rotations, and meetings routinely remove 20–40% of that, and a points target alone never sees it.

Separate complexity from capacity

Story points are fine for sizing relative complexity. The mistake is stopping there. The teams that estimate well do two things separately: they size the work, and they calculate what the team can actually absorb this sprint based on real availability. When those two numbers meet, the commitment is defensible — you can show a stakeholder exactly why the sprint holds eight stories and not twelve. We walk through the mechanics in aligning sprint planning with capacity planning and the difference that trips teams up in velocity vs. capacity.

Make it repeatable in Jira

This is exactly what Sprint Planning, Capacity & Resource Planning for Jira was built for: it converts each person’s real availability — part-time splits, leave, and detail assignments included — into a capacity number, then plans scope against it so the team commits to what it can finish, not what it hopes to. Pair it with Backlog Refinement, Sprint & Capacity Planning so the next sprint’s stories arrive already sized and ready, and planning poker stops being a guessing contest.

Estimation will never be perfect — it’s a forecast, not a fact. But once you stop conflating complexity with capacity and let real availability drive the commitment, the gap between what you plan and what you deliver narrows fast. For the bigger picture, see the full rundown of Scrum challenges and how to solve them.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio