Story Points: Estimating Effort, Not Time
Story points measure effort, not hours. They combine a task's complexity, uncertainty, and volume into a single relative number. Agile teams use them to forecast work capacity.
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.
Interview question
When a team assigns 8 story points to a task, what does this primarily signify?
- a.The task is expected to be finished by the 8th day of the sprint.
- b.The task is roughly twice the effort and complexity of a 4-point task.Correct
- c.The task will take approximately 8 hours to complete.
- d.The task requires 8 individual team members to complete it.
Why? this is the answer
Story points measure relative effort, complexity, and uncertainty, not time. Therefore, an 8-point task indicates it is roughly twice as hard as a 4-point task for that specific team. Option C represents a common misconception, as story points are explicitly not a measure of hours.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles