Re:Ask HN: Why can't anyone tell me what story points equate...
by topkai22 on Tuesday March 30, 2021 @03:20AM
(#26631981)
This is exactly right. The only other things I’ll add is that story points can be used to encompass estimated risk better than hours can, and they encourage focusing on team accomplishments rather than individual optimization.
If my team was to an estimate that included task A and task B with estimates of 20 hours but then task A took 5 hours and task B took 35 hours there is a good chance that a PM or some other manager is going to be all over us on why task 5 took 35 hours without any discussion of our success on task A. Abstracting to story point estimations (that explicitly encompass risk) of 5 and 5 a piece let’s the team celebrate that they accomplished what they set out to do in aggregate.
As others have said, they are convertible to time. But what's the conversion factor? You don't know until you measure it. "The team is doing an average of 22 story points per two-week sprint over the last three sprints." OK, now you know what a story point equates to - for that team, working on that project, with the same people doing the estimates. That doesn't mean anything for the same team on a different project, or a different team, or different people doing the estimates. They are not portable whatsoever. But within the context of the project, you can estimate reasonably well how much you can get done in the next several sprints.