Story Point
An abstract numerical unit used in agile development to measure the relative complexity and effort associated with a user story. Story points are typically assigned using the Fibonacci sequence and are intended to avoid direct time estimation, focusing instead on comparative sizing of work items.
Timeline (last 90 days)
A story point is a unit used in agile development to estimate the relative complexity of a task rather than absolute work hours, usually referencing the Fibonacci sequence, and is jointly determined by the team through methods such as planning poker.
Under AI-assisted programming, the limitations of story points are amplified: code quality, maintainability, and subsequent rework costs are not included in the estimate, and the number of story points completed cannot be equated with real engineering value.
Story points are based on the cognitive characteristic that the human brain is more accurate at relative comparison than at absolute estimation.
The Fibonacci sequence was introduced into estimation because the increasing gaps between numbers reflect the growing uncertainty of higher-complexity tasks.
Story points were originally intended to measure complexity and effort using relative numerical values as a replacement for poor time estimates.
When a subjective relative measure (story points) is treated as an absolute measure for cross-team comparison and performance management, all inferences drawn from it become systematically distorted.
The author does not entirely reject story points, but advocates treating them as a shared language for discussing uncertainty rather than as commitments or predictions.
The author believes that story points ultimately failed to solve the problem and instead created a new kind of religious-like belief.
The concept of story points originated in Extreme Programming (XP) and early Scrum practices, and was popularized by Ron Jeffries and others in the late 1990s.
All Facts (9)
A story point is a unit used in agile development to estimate the relative complexity of a task rather than absolute work hours, usually referencing the Fibonacci sequence, and is jointly determined by the team through methods such as planning poker.
50%UnverifiedUnder AI-assisted programming, the limitations of story points are amplified: code quality, maintainability, and subsequent rework costs are not included in the estimate, and the number of story points completed cannot be equated with real engineering value.
50%UnverifiedStory points are based on the cognitive characteristic that the human brain is more accurate at relative comparison than at absolute estimation.
50%UnverifiedThe Fibonacci sequence was introduced into estimation because the increasing gaps between numbers reflect the growing uncertainty of higher-complexity tasks.
50%UnverifiedStory points were originally intended to measure complexity and effort using relative numerical values as a replacement for poor time estimates.
50%UnverifiedWhen a subjective relative measure (story points) is treated as an absolute measure for cross-team comparison and performance management, all inferences drawn from it become systematically distorted.
50%UnverifiedThe author does not entirely reject story points, but advocates treating them as a shared language for discussing uncertainty rather than as commitments or predictions.
50%UnverifiedThe author believes that story points ultimately failed to solve the problem and instead created a new kind of religious-like belief.
50%UnverifiedThe concept of story points originated in Extreme Programming (XP) and early Scrum practices, and was popularized by Ron Jeffries and others in the late 1990s.
50%