Comment

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.

source

Sort:hotnew top

Lichtblitz@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
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.

source
- TehPers@beehaw.org ⁨1⁩ ⁨year⁩ ago
  I guess the flaw is that it’s (almost) never used only for planning and is often used as a metric of productivity. 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.
  
  source
  - Lichtblitz@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
    
    […] 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.
    
    source
    Dark_Arc@social.packetloss.gg ⁨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
    
    source
sebsch@discuss.tchncs.de ⁨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 the 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.

source