this post was submitted on 02 Sep 2023
236 points (94.4% liked)

Programming

17398 readers
105 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] TehPers@beehaw.org 38 points 1 year ago (2 children)

Story points and velocity always felt to me like a flawed metric. It encourages volume of work, and discourages quality of work. The worse your code is, the more stories and tasks you can create to fix it, and the higher your velocity. It's a bit of a shame that it's used so widely as a measurement of work completed, and I wish a better means of measuring productivity would become more popular instead.

[–] Lichtblitz@discuss.tchncs.de 28 points 1 year ago (1 children)

It's not flawed. Nobody should get rewarded or encouraged by story points. It's solely a planning metric and not a metric of productivity.

[–] TehPers@beehaw.org 6 points 1 year ago* (last edited 1 year ago) (1 children)

I guess the flaw is that it's (almost) never used only for planning and is often used as a metric of productivity, from my experience. It becomes a competition to see who can check off the most story points, and velocity is often used to compare developers against each other.

[–] Lichtblitz@discuss.tchncs.de 7 points 1 year ago (1 children)

[...] and velocity is often used to compare developers against each other.

Wow, that's messed up. Luckily I've never had such a team/such leadership.

[–] Dark_Arc@social.packetloss.gg 2 points 1 year ago

Yeah I've seen it, it about burned the company to the ground too over exodus of talented personnel... so... managers beware

[–] sebsch@discuss.tchncs.de 7 points 1 year ago* (last edited 1 year ago)

Story points are meant to have a shared understanding about complexity during the planning phase. There where never meant (and do not fit) for either capacy planning or to measure the throughput.

If your PO is using this he or she is either not well informed and/or uses this as a tool to create toxic pressure.