For many years, software program engineering has been tormented by “productiveness theater.” Each few years, the business aligns round a brand new self-importance metric — often one which latches onto no matter know-how occurs to be in vogue on the time. For a self-discipline rooted in creativity and problem-solving, this can be a poor approach to show progress. But, we discover ourselves on this place as soon as once more. The sample is usually the identical: attain for one thing we are able to simply rely, and in doing so, lose sight of what we are literally making an attempt to realize.
Amount over high quality: the mistaken measurement, each time
I recall after I was developing as a software program engineer within the Nineties, a small variety of corporations took up the follow of paying their engineers by every line of code. This will likely have been productiveness theater at its worst, resulting in adverse incentives, inefficient processes, and simply typically unhealthy engineering. Builders have been rewarded for writing way more code than the issues they have been going through required — basic “amount over high quality” — and the end result was bloated, brittle codebases that have been all however inconceivable to take care of. The purpose — to create dependable software program that solved actual consumer issues — obtained buried below the motivation to provide.
Then within the 2000s, the rise of Agile brought us story points, an summary approach to estimate activity complexity, effort, and threat relative to different work. Fairly than answering “How lengthy will this take?,” story factors have been meant to reply, “How massive is that this in comparison with what we’ve executed earlier than?” This strategy sounds good in concept, however in follow, some improvement groups realized to sport the system by inflating estimates, over-engineering options to look productive, and shedding sight of whether or not the work they produced truly created worth. As soon as once more, the metric turned the purpose, and the precise purpose — delivering outcomes that mattered to the enterprise — turned secondary.