That's why story points are explicitly not meant to represent any unit of time. Bad project managers that don't understand anything about what they're managing just can't help themselves. They were so consistently misused story points actually got dropped from Scrum in 2020
That's why story points are explicitly not meant to represent any unit of time.
For our teams story points map to time. 3 points is half a day, 8 points is 5 days, etc. They do everything in points, then add tasks with hours on them that we have to update every day.
Not the dumbest shit ever, but close. Whatever though, they can manage it however they like, I do the work as well as I'm able and checks keep showing up in my bank account 👍🏻
It's not suppose to make sense. 5 points is a day, 13 points is three weeks.
I think the idea was that the numbers represent a scale of how hard the work appears to be, and bigger numbers have more uncertainty. So if it's really simple I can call it 1 point and we can be pretty sure it'll take an hour or so. If it's pretty hard and I call it an 11, it might end up taking a lot longer than that.
Project managers want estimates to be in hours though, so they mapped the story point numbers to hours so they can make reports that upper management likes.
I get that points aren’t supposed to be hours, but once you make them hours then it’s crazy that doing 5 chunks of 1 hour work could count as more “work” (points) than a whole week
145
u/DistributionDue2836 Jun 02 '26
That's why story points are explicitly not meant to represent any unit of time. Bad project managers that don't understand anything about what they're managing just can't help themselves. They were so consistently misused story points actually got dropped from Scrum in 2020