SAME STATS, DIFFERENT IMPROVEMENTS

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

-24 points · 5 comments · view on lemmy.world

5 Comments

deegeese@sopuli.xyz · 18 pts · 1y (1 reply)

A changed nothing, and I worry they’re managing to the metric.

B stopped opening and closing a large number of trivial bugs.

C did a cull of old bugs and changed their intake behavior but is growing a backlog.

marcos@lemmy.world · 7 pts · 1y

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.

bear@lemmynsfw.com · 8 pts · 1y
[ removed ]
sukhmel@programming.dev · 8 pts · 1y

Also, if this is only a change in managing bugs, nothing may have changed except for more bug tracking for trivial bugs, or the opposite, ignoring more severe bugs

IanSudbery@genomic.social · 3 pts · 1y (1 reply)

@LabPlot @programming I'd say its difficult to tell without at formal statistical assessment, but if I had to pick, i'd say B. The difference between pre and post in A is just a continuation of a pre=existing trend. The difference in C looks like it might be reverting to mean over time, or even getting worse than it was prior to the change if the study went on longer.

LabPlot@floss.social · 0 pts · 1y

@IanSudbery @programming

Assuming a steady flow of bugs of the same kind, we share the same line of reasoning.