-25
submitted 2 weeks ago* (last edited 2 weeks ago) by LabPlot@floss.social to c/programming@programming.dev

SAME STATS, DIFFERENT IMPROVEMENTS

@programming

After 12 months of managing #bugs, #developers A, B, and C changed their approach.

Assuming a steady flow of bugs of the same kind, whose change is an improvement❓

Boosts appreciated! 🙂 :boost_love:

More generally, the problem is domain independent.

#OpenSource #FreeSoftware #FOSS #FLOSS #Software #Tech #Development #Engineering #Business #Improvement #Software #Programming #Python #InfoSec #Statistics #Linux

you are viewing a single comment's thread
view the rest of the comments
[-] marcos@lemmy.world 7 points 2 weeks ago

A has been consistently improving it since before the change, so it's only possible that they are managing to the metric if they had earlier access to it.

B may be doing that, but the graph doesn't actually measure how many bugs you closed. Those ones seem to have decided to manage by the metric, removing the variance but targeting a high, comfortable level.

Agreed on C, they did a large "hey, we will be measured by that now" one time effort and then forgot about the metric.

The change didn't improve anybody's performance.

this post was submitted on 14 Dec 2024
-25 points (19.5% liked)

Programming

17701 readers
359 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 2 years ago
MODERATORS