It's always a touchy subject (software metrics) but great article talking about the underlying reasons WHY they failed and a better approach to using metrics.
Most bad metrics out there suffer from the same core issues:
- They attempt to compare individuals
- They attempt to boil down 'productivity' into a few simplified metrics
- A 'successful outcomes' for software are always changing
A better way seems to be:
- Measure engineers and teams independently
- Compare relative to individual history
- Look at risks and bottlenecks to productivity. Not just optimize any one metric
Here's the actual article if you're interested: https://www.usehaystack.io/blog/software-development-metrics-pros-cons-and-why-past-attempts-have-failed
submitted by /u/lovedev
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/3jPwEBA