Outcomes versus outputs: the real measure of developer productivity

“Developer productivity” can be an emotive, and occasionally misunderstood term. It is not the output of individuals that we are seeking to understand, but the effectiveness of the development system as a whole.

A few percentage point increases in development efficiency in a large organization can represent hundreds of thousands of dollars in cost reduction, better time to market and improved product quality. That, coupled with the promise of significant productivity increases from AI code companions, means that being able to understand and measure the productivity of the engineering workforce should be a key priority for business leaders.

But doing so can be complex and requires a shift in perspective away from merely counting lines of code, toward evaluating the broader impact on business goals. By adopting modern productivity measures, business leaders can better understand and enhance the effectiveness of their development teams, ultimately leading to more innovative and successful projects.

Dropping esoteric productivity measures

Historically, businesses have looked to metrics like lines of code or story points to gauge developer productivity. However, these measures often don’t reflect the true value that a developer brings to a project and they can also be easily influenced. For example, developers can artificially inflate their productivity by writing verbose code or overestimating story point values.

Separately, such measures can be weaponized by management and business stakeholders to apply to deliver keystrokes more quickly, without appropriate consideration for the real drivers of…