Story point estimation¶

Mike Cohn, Agile Estimating and Planning¶

The classic, still considered current two decades later. It's widely regarded as the definitive guide to planning in an unpredictable world, covering story points, velocity, release planning, and backlog refinement with a good balance of theory and practical application. DEV Community

Atlassian's guide to story points¶

free, fast primer. It frames story points as a relative estimation method for assessing effort, complexity, and risk, and notes that using points instead of hours reduces emotional bias and improves forecasting. Atlassian

The Art of Story Point Estimation¶

a shorter, more modern take. Its core reframe is useful: estimation is a tool for alignment and calibration, not prediction — a common language for discussing uncertainty rather than a commitment. Medium

Notes¶

For an infra person specifically: the trap is usually treating a story point like "how many hours will this take," when the team actually wants "how complex/risky/unfamiliar is this relative to a story we already agreed was a 3." Reframing it as relative sizing rather than a time estimate tends to fix most estimation friction fast and it's a good thing to say explicitly in retro if that's not how the team is calibrating.