Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You’re looking at it all wrong, story points are a defensive tool for you the developer. It gives your team a made up unit that no one else understands.

If you told someone on Monday that a ticket takes two days they’ll ask you on Thursday why it’s not done.

Instead story points combined with team velocity give your team a sense of how much work you can commit to.

Of course we all have in our mind that a 5 point story takes a like 3 days.

If some director or product leader comes in and looks at these tickets the won’t see any time estimates on them and thus can’t hold you accountable to them. Sue they can look at your team velocity. But that’s generally a higher level moving average of several sprints.

Of course this is all imprecise and often isn’t implemented well. I’ve seen it work very well for some teams, where it gave us a good sense of our accomplishments and led to more ownership. It often doesn’t work and just adds overhead.

I’ve ditched it for my current team.



I can see how that could be useful for some teams. I guess the teams I've been on just haven't needed that kind of obfuscation.

In any case, I was talking about the many devs who insist it's not time even though it is. Having it be a sort of abstracted or obfuscated time increment is fine imo.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: