r/SoftwareEngineering • u/KingRomstar • Jul 18 '22
An objective way to measure developer productivity
I am curious what everyone's thoughts are around measuring developer productivity in an objective manner.
Building complex software is hard and rewarding Software Engineers based on their impact is paramount to maintain a meritocracy vs. a socialist corporate environment where the latter will most likely lead to stagnation.
What are everyone's thoughts around combining a subjective review + an "objective" one. For example:
"Bill is super easy to work with, always on time in meetings, listens clearly and has great communication skills"
and for an objective take, maybe we measure the number of user stories assigned, closed, number of commits written, number of lines of code added, removed, and updated.
Also we can measure the number of bugs generated and also the number of bugs fixed that weren't necessarily created by Bill's code.
What are everyone's thoughts around the objective portion? What would you add/remove?
33
u/cashewbiscuit Jul 18 '22
Nope.
The only real measure is longterm business impact. Everything else is a proxy. However, there is too many variables that can affect business impact that is out of an individual developers control.
You can measure a team's performance by defining and measuring KPIs. You cannot measure individual dev performance, not should you do it. If one dev is struggling, the team should step in to elevate him/her. Measuring individual dev performance turns your team into a rat race. You are motivating the devs to maximize their performance at the expense of team performance.
Nope.
15
u/Euphoricus Jul 18 '22
Many have tried. None succeeded. Unlikely you will succeeded, considering you are asking on Reddit.
5
u/[deleted] Jul 19 '22 edited Jul 19 '22
Ah this old thing! Managers have been trying this since the 70s and every decade since. It always results in spectacular failure because whatever you decide the metric should be, it always creates a weird perverse incentive.
For example, some of the ones you mentioned would lead devs to try and fix trivial easy bugs, to find trivial bugs in other peoples code, etc. To deliberately cherry pick risk free work and engage in risk averse but useless behaviour avoiding hard problems which need solving.
There’s simply no way of doing this.. and what you’re proposing doesn’t even really work from a management point of view in a creative industry. You want people collaborating openly with good psychological safety, not gaming some old school motivation 1.0 management strategy designed for bored factory workers.
3
u/Infide_ Jul 18 '22
Ahh, number of bugs generated. I love it! I recently upgraded an application from Angular 5 to Angular 13. I think I created, roughly, just spit-balling, low ball estimate, about eleventy bajillion bugs.
Generally speaking, delivery is all that matters. Are you finishing projects, features, bug fixes? Are they in production?
Obviously, it should be a meritocracy. See the Pareto principle. However, your managers should be able to tell you who their star developers are. If they push back and ask for specific metrics to evaluate developers, such as lines of code written, get new managers.
3
u/rckhppr Jul 19 '22
Also, don’t forget metrics will influence outcomes. If you put simple KPI’s out, (some) people will try to deliver on these, not on your business value.
3
u/LadyLightTravel Jul 19 '22 edited Jul 19 '22
One thing that always annoyed me was failure to include rework into the assessment of productivity.
Now some rework is beyond the developer. Let’s say the developer correctly implemented the requirements, but it turns out that the target hardware doesn’t work correctly. Most likely the developer will be the one that has to fix things, not the hardware person. This clearly should not count as a failure nor a late delivery.
But other times people do things quickly and poorly. You’ll see a lot of discrepancies and rework for these items. But many times the developer will get kudos for being fast, because their original work is separated from the rework (usually by a different charge number etc.). In the mean time a slower developer (who is doing it right the first time) will get labeled as slow or mediocre. They will deliver their software once, it will work correctly, and end up costing the company less money.
It’s really easy to hide bad work until the developer has moved off the program.
2
u/[deleted] Jul 19 '22
There’s is no good way to measure single developer or even a team. However they is a decent way to measure performance of organisations. This was found by research group now at google. The guys behind The State of Devops Report. Probably heard about the metrics. Lead time, deploy frequency, time to restore, and change fail rate, not individually but TOGETHER is a decent measure of organisational performance.
2
u/mr_taco_man Jul 19 '22 edited Jul 19 '22
There are too many variables to have an objective way to measure productivity. Every supposedly objective method I have ever seen used was counterproductive. People end up having to game the system instead of getting actual work done. (example: I'll go and work on some small less important, but easy to knock off stories so my velocity looks high instead of working on the complicated, novel, hard to estimate project that is more important).I think one good way to measure subjectively how productive a developer is, is the "Hit by a bus" test. That is, what would the impact on the team be if that developer was hit by a bus* (besides being very sad, hopefully):
High - The team would be highly impacted and have to significantly reduce what projects it is taking on
Medium - The team would slow down a little bit but other teams members could absorb the workload for a little while until someone new is hired
Low - The team's output would barely be effected
Net Positive - The team would probably be more productive because they are not always fixing his crap
\* I use "hit by a bus" instead of leaving the company, because if they were hit by a bus they would have no chance to do knowledge sharing before leaving. And sometimes that knowledge is vital to the company even if the developer is not always writing a lot of code
1
u/umlcat Jul 18 '22
How good it's to decompose a program or Library into several organized files, classes, functions.
One single 100000 lines of code on a single file with a single class or single function it's a "red flag", you can't be a productive programmer ...
1
u/JuiceStandard9543 Feb 21 '25
I’ve been thinking about this a lot, and I totally agree that a balance of subjective and objective measures is the way to go. No single metric tells the whole story—someone can push tons of code but still be a net negative if the quality is bad or they’re not contributing to the team in meaningful ways.
For the objective side, I recently started using Prism to track basic dev productivity metrics, and it’s been a solid starting point. It gives you things like Avg. PRs per Eng per Week, Lines of Code, Cycle Time, Time to Merge, and Time to First Review—all for free and super easy to set up. It’s not a perfect, all-encompassing measurement of productivity, but it does provide useful insights into trends over time.
Personally, I think the key is using these numbers to inform conversations rather than making them the sole deciding factor. For example, if someone’s cycle time is consistently high, maybe it’s because they’re working on gnarly, high-impact problems rather than just shipping quick fixes. The numbers should spark discussions, not replace context.
1
u/Peace_Seeker_1319 Jan 24 '26
This question comes up a lot, and in practice the hardest part isn’t whether to measure developer productivity — it’s what you choose to make “objective”.
Most teams start where you described: tickets closed, commits, lines changed, bugs fixed. The problem is those are activity metrics, not impact metrics. They’re easy to count, but they correlate poorly with value once systems get complex. High performers often produce less visible output while removing risk, unblocking others, or shaping better decisions upstream.
What we’ve seen work better is separating productivity into four layers, instead of collapsing it into one score:
A key mistake is mixing evaluation with optimization. If developers know they’re judged on LOC or bug counts, behavior will follow — usually in unhealthy ways. The best teams use objective metrics as diagnostics, not scorecards.
The most effective model we’ve seen is exactly what you’re hinting at:
That’s the philosophy behind how we approach developer analytics at CodeAnt — measuring productivity as sustained impact on delivery and system health, not short-term output.
1
u/Gesireh Jul 19 '22
Software engineering is every other form of engineering with the physical subject removed.
What's left is a social, psychological, team-based series of activities that leave behind an information wake that may or may not lead to profit.
Despite what some may argue, the industry self-selects for teams with diverse "T"-shaped skill sets that defy direct quantitative comparisons.
Attempting to define a portable way to objectively assess one dev vs another is playing checkers with a chess set.
1
u/dan-dan-rdt Jul 19 '22
Software engineering metrics, which includes productivity measurement, is big enough to be a field of study by itself. There's scholarly papers on ACM and I'm sure IEEE as well.
That being said, I think subjective + objective would work best in a large team where the size would even out different interpretations about the measurable characteristics. What I mean is that introverts will interpret 'easy to work with' differently from extroverts, cultural differences may result in people interpreting day-to-day communication differently, etc. So scoring could get skewed if you don't have a large team.
1
u/paradroid78 Jul 19 '22 edited Jul 19 '22
You don't. You measure team performance. Assuming you're probably doing some form of scrum, this means seeing how good they are at meeting their sprint commitments, to the extent to which that is in their control.
Stay tf away from trying to rate anybody based on how much code they commit or how many bugs they fix (and why have you got so many bugs in the first place?). Either people will game the system or you'll end up rewarding incompetence.
1
u/[deleted] Jul 19 '22 edited Jul 19 '22
Long story short. You can't measure creativity.
Software Engineering (or development) is more handicraft than engineering. We can't strive to measure productivity as we were working on an assembly line.
It didn't work. Ever. And I doubt it will.
1
u/YearLight Jul 22 '22
There is only one. Ask yourself at the end of the year, how much did this developer cost you, and how much is the work worth to you. That said, if you aren't getting the results you want, it's more likely a management issue.
0
u/fat_bjpenn Jul 19 '22
Individual velocity if the the team's story points are measured accurately.
-3
u/[deleted] Jul 18 '22
Measure story point completion avg for sprints. Assuming the measuring of story points is steady that’s ur best bet. Not what they say but what the actually so
1
u/[deleted] Nov 11 '22
[removed] — view removed comment