Dispatch #15/23

The discussion about measuring Developers' productivity is peaking -again. This topic feels like an evergreen, a long dispute without a clear answer. Productivity is a complicated concept in development. Problematic because of multiple reasons:

  • Complex Calculation: We do not do the same repeatedly (with exceptions) in development. If we produced, for example, always the same table again and again, it would be easier to calculate. We could see how much time and material we need. If we need less time or material, that would be productivity improvement.

  • Misleading Incentive: By measuring and reporting productivity, developers might tread productivity for quality or scope. Depending on the incentives, some might even begin to game the system. 

  • Mental Work vs. Physical Work: Productivity is a concept from physical work. Where to produce more is always good. That's not the case in software development. More lines of code do not mean it's better.

Now we are entering a recession phase. As a result, enterprises are asking again for cost reduction and productivity increases. So, let's see what answers are out there. 

Here are some fascinating articles that we came across this week:

  • Article: Software developer productivity depends on their skills, knowledge, tools, and working process. But what is about their happiness? Happiness and productivity

Now, we want to know your thoughts:

  • Is your company measuring developers' productivity?

  • What do you take into account when measuring?

  • Is anyone still using Functional Points or Velocity to report improvements?

We would like to hear from you; write us a comment or mail!

Regards, Florian

hoeppnerflorian@gmail.com

www.TechAccelerationAndResilience.com

Published weekly in a row: 15

Previous
Previous

Dispatch #16/23

Next
Next

Dispatch #14/23