Ось знайшов цікавий текст, з яким я цілком згоден, про сторі пойнтс і естімейтс
'''
The whole point of Story Points is that we're TERRIBLE in estimating time, but we know the difference between Easy, Normal, Hard, Super Hard, and Impossible. How long does it take to go to the bank, deposit a check, and get back to the office? 30 minutes? 1 hour? WE DON'T KNOW! Monday it'll take an hour, Wednesday it'll take 45 minutes, and Friday it'll take an hour and a half! Debugging code takes either 10 minutes or seven days! There's no real way to estimate ACCURATELY the time.
BUT, we know that the bank trip is medium effort because of traffic and lines. We know that debugging this particular piece of code is Hard because it's intricate and that this other issue is probably Easy because the problem statement is a known behavior and simple to diagnose.
Story Points are NOT to track or inform the business on time for a Gannt chart. It's for the TEAM to estimate workload and what can be done in the current/future sprints. That's the end of it. The only thing you do with Story Points after you close the story is "do we think that we were right on our estimate? If not, what did we learn from it being easier/harder than we originally thought so that we do better in the future?" That's it, that's the end of it. Lessons learned so that we can empirically improve on our process down the road. And again, it's JUST for the team, not the PMO.
'''
