Story Points: Estimating Effort, Not Time

THE MENTAL MODEL: Story points are a unit of relative effort, not a measure of time. They encapsulate the total work required for a task, including its complexity, the risks or uncertainties involved, and the amount of repetition. Think of it as answering 'how hard is this?' rather than 'how many hours will this take?'. A 5-point story is roughly half the effort of a 10-point story.

HOW IT WORKS: Teams typically use a modified Fibonacci sequence (1, 2, 3, 5, 8, 13...) for estimation. This non-linear scale reflects the increasing uncertainty that comes with larger tasks. During a planning session, often called 'planning poker', team members privately choose a point value for a user story and then reveal their estimates simultaneously. Discrepancies lead to valuable discussions about hidden complexities or misunderstandings. The team then agrees on a final point value.

WHEN TO USE IT: Story points are central to Agile and Scrum frameworks. They are used during sprint planning to gauge team capacity. By tracking the total points completed in previous sprints, a team can calculate its 'velocity'—a historical average used to forecast how much work it can realistically take on in the next sprint. This fosters more predictable delivery and sustainable pace.

WHEN NOT TO USE IT: Avoid using story points to measure individual productivity or compare different teams. A point is a relative measure unique to the team that created it; Team A's 5-point story is not equivalent to Team B's. Also, avoid converting points directly to hours. This practice, a common footgun, negates the benefits of abstracting away from time and reintroduces the inaccuracies and pressures of time-based estimation.

ONE CANONICAL EXAMPLE: A team is estimating two tasks. Task A is 'Add a login button,' which is well-understood and low-risk. They estimate it as 2 points. Task B is 'Integrate a new third-party payment provider,' which involves unknown APIs and significant risk. Even if both might take a similar amount of time if everything goes perfectly, the team estimates Task B as 8 points to account for the high complexity and uncertainty. This relative sizing helps them plan more effectively.