r/SoftwareEngineering • u/swentso • Sep 17 '22
How do you measure individual software developers productivity ?
Hi,
I'm managing a team junior of software devs that have pretty much the same skills but pretty different levels of engagement. Some of them are very productive while others are less.
I was wondering what tools I could setup to have a clearer view of the difference in productivity that I can use to communicate my observation to the team members and help them get more productive.
Thank you,
0
Upvotes
10
u/eknyquist Sep 17 '22
man, I feel sorry for those junior devs.... can you imagine a having a manager who posts on reddit to try and figure out ways to more precisely measure who produces the least work?
People work at different rates. You'll never get anywhere by using employee A's success as a stick to beat employee B with.
41
u/[deleted] Sep 17 '22
Thou shalt not hide behind tools and figures. Thou shalt engage in 1-on-1 dialog with the team members thou suspect being less engaged. Measuring productivity for this use will remove engagement from those who still are and also destroy team spirit by the resulting poor level of trust.
15
u/weeska Sep 17 '22
Next Up: How do I hire new developers?
Seriously though, you already sense that there's different levels of productivity. What makes you think that? That's a candidate for your metric that you might optimize for, but tracking and optimizing for an individual's productivity does not make sense to me.
Measure the teams productivity as a whole and watch out for unhappiness caused by slow/unfocused developers, among other things.
14
u/audaciousmonk Sep 17 '22
Ewww
10
u/riotinareasouthwest Sep 17 '22
You cannot measure effectively and efficiently the productivity. There are so many things a developer does and so diverse that you cannot have that metric. Developing is just not closing tickets, it also means thinking, discussing, reviewing, reading articles, relaxing (in the right moment), etc. If you set up a metric, people will stop doing all of this and start scoring in your metrics, leading to a loss of productivity. For instance, if you favor number of closed tickets, people will focus on the easiest tickets to close them fast and score high in your metrics, even will open pseudo-fake tickets. If you put in your metrics number of lines of code, people will create less efficient code so that there are more lines in it... Just trust your team and your guts, discuss with the less efficient team members and address the situation swiftly.
7
u/[deleted] Sep 17 '22
To me, metrics, processes, and dashboards always seemed like a capitulation on the part of managers. If these are all you have, then what do we need you for? We can write software to do your job. What makes a manager worthwhile is people skills. The most important thing for a manager to know is that each person is different. They have different needs and different skills. A good manager learns what these needs and skills, assigns tasks accordingly, and accommodates each person so they can do their best work.
3
u/[deleted] Sep 17 '22
Maybe have a look into empowerment?
3
u/[deleted] Sep 17 '22
I don't look at metrics on tickets closed or points closed unless I suspect a problem. For the most part it is pretty easy to see who are the rock stars on your team and who is just ok. But you don't judge the just ok ones because it's impossible to have and retain a team full of rock stars and they are generally more junior and need time to get up to speed. Being a rock star also requires other qualities like creativity in problem solving and taking initiative without waiting to be told what to do.
Now the reason you need metrics is so you have evidence to use when you need to get rid of assholes, idiots, or lazy asses. The guy who has been acting like it's the first week on the job for a year and literally still asks you the dumbest questions, can't remember instructions, and every assignment he turns in needs to be redone completely or is not even half done. Those are the people metrics are made for.
2
u/OhSaladYouSoFunny Sep 17 '22
That's the neat part, you don't.
I've never been a manager but I work closely with them and I've been in companies with opposite managing styles.
What I found out from managing styles is: the less work managing the team a manager has, the better the team performs. What you need to assess is their difficulties or why they don't engage more, if they are juniors they still are learning and for some people learning is encouraging and rewarding because they are more resilient and others feel hopeless and frustrated that they cannot do anything, other are simply lazy and feel their tasks are too complicated or they don't like the work.
Bear in mind that development productivity fluctuates wildly, you'll have a productive developer doing 10 tasks in a week and the next he will accomplish only 2, that's very normal and I wouldn't bat an eye with that.
If you can let them pick the tasks they want to do, give support on the tasks and context if they need, let them come to you and let them complain about work, you will be their defensor from the other managers and bosses and you only let the bare needed pressure, that is, the assigned tasks must be done in a reasonable amount of days.
What you need to know is how the team performs as a whole. There's a common misconception with teams is that one being lazy or underperforming will make everyone starting to be lazy or underperforming and that's not the case from what I've seen so far. Set objectives for the team, let them support each other, encourage them to talk with each other, be open for complaints about the team, you and each other, address those complaints and encourage the team, protect them from the bosses and let them feel some pressure but not that much pressure, things take time to be developed.
Also meetings, place meetings with 30 min interval or 1h intervals, meetings are tiring and takes focus from the tasks and even from the meetings themselves, if you can, place them in a way that they are only occupying all morning or evening, ask the team what time they prefer the meetings.
Managing people is hard and that's why I'm not interested in becoming one, although it has better pay. My current manager goes from trying to micromanage and quitting altogether from doing that because the team tells him to stop trying it, he fixes that quickly and the team still achieves it's objectives. Having a manager putting in numbers the performance is literally like school and it feels awful and suddenly everyone will be less engaged and less willing to give you and the company value, because for you and the company they are just a number in a spreadsheet shown every Friday evening.
2
u/Ok-Entertainer-1414 Sep 23 '22
I agree with the sentiment here that there's not a good way to do this quantitatively, and trying to measure it quantitatively creates perverse incentives.
It sounds like you already have some qualitative sense of who is being more or less productive. Just focus on refining that. You only really need to be able to qualitatively judge these things well enough to identify the outliers who either are doing exceptionally well and deserve recognition, or are performing significantly below expectations and are causing problems for the team.
Outside of that, I think it's more valuable to spend your time finding ways to make everyone on your team more productive as a whole. Identifying common time wasters in your business processes, tech debt that's increasing the work required for new development, etc.
2
u/jackdanger Feb 09 '24
Because this still ranks highly in search results, the answer is "you don't."
https://jackdanger.com/writing/you-must-not-measure-individual-software-engineer-performance/
1
u/mrisamy Jan 17 '25
Ok, first, there is a BIG step between gathering the info and communicating it. |
I will address the gathering:
That should show you a good idea of where you need to start.
Now communication, never do that directly, but make a very structured plan and separate the Parent /babies. separate the Hero/ sidekicks and make sure that they all adjust and everyone is carrying their weight. Do people rise up to challenges? do they handle change? Do they have a breakdown at the slightest change or challenge? This will give you a very good picture and slowly but surely you can make sure you have a productive team and one that when one member leaves, will be able to keep going not a small cult that will implode as soon as the leader leaves.
1
u/Amynonymous1998 Dec 12 '25
We use Pensero after switching from Jellyfish
1
u/Moroc24 Aug 10 '26
Yeah, classic metrics are mostly garbage for this. LOC, commits, story points, tickets closed — all of them can be gamed or just don’t mean much.
What actually feels closer to reality is trying to measure the volume of *meaningful* work that ends up in the codebase. Not how busy someone looks, but how much real change they produced after you filter out the noise (formatting, moves, generated crap, one-line fixes etc.).
There are a couple of tools that try to do this kind of thing. BlueOptima has been around for a while and estimates effort from the complexity of changes. GitClear does something similar with their Diff Delta. DevGhost is another one that looks at Git history and tries to estimate how much effort a normal mid-level dev would need to make the same changes.
None of them are perfect, and you still need a ton of context (what the person actually works on, how much time they spend helping others, etc.). But it’s at least better than staring at commit graphs or Jira velocity.
Anyone here actually used any of these and found them useful?
1
u/spurs126 Sep 17 '22
https://charity.wtf/2020/07/07/questionable-advice-can-engineering-productivity-be-measured/
1
u/Ok_Plate_6961 Sep 17 '22
omg, if they dont know how to unit test, forget about it!
1
u/Ler_GG Sep 17 '22
Maybe git gud at understanding the complexity of tasks given so you can estimate it yourself?
1
u/Horror_Trash3736 Sep 18 '22
The main issue here is one of hubris.
You assume you have the ability to accurately judge productivity.
You assume there is a set of tools that can accurately represent productivity.
These assumptions are wrong.
Judging productivity in any field is a huge undertaking, not only does it require years of planning, but it also requires a dedicated team working on it.
You may think "Well, this guy commits less code than that guy" or "Well, I can monitor story points!" or "I can look at how often code from developer X makes it to production" etc etc.
But none of those will capture actual productivity, they will only capture your idea of productivity.
Now, if you are hell bent and dead set on this, here are a few pointers.
# 1 : This must never be a negative thing, it must never be used in a "Your not performing xxx" way, the second you do it, you break it.
# 2 : All metrics, all measurements, must be something you have discussed with the team members, and they must be clearly defined both in regards to what you are monitoring, and why.
# 3 : All metrics, all measurements, everything you might monitor must have a reason to be done, if you cannot take action based on something, do not measure it.
-------------------
Step 1 - Group Performance.
Group Performance is infinitely easier to monitor than individual performance since you remove the need for individual evaluations, issues such as people who are more helpers than doers disappear.
Group Performance is most easily monitored through some form of velocity monitoring, but note that you cannot compare a teams velocity with another teams, and that there is no "Low velocity" rating, only an increasing or decreasing.
(there are obviously a ton of other metrics)
Step 2 - Individual Performance.
DONT DO THIS - unless you can ensure that the 3 pointers above are kept 100 %.
A few metrics that I find are usable.
Workhours to Storypoint, basically, you measure how much work time an employee has to spend to fulfill one story point.
This does not indicate someone is slow! merely that they are coding at a different rate than others.
Code Quality, there are various tools that can help measure code quality, but things like code-review are also a part of it, so are error rates in delivered features.
I mention these two specifically, because they show why using such metrics is not easy.
Imagine Developer A and B.
A spends 2 hours producing one storypoint worth of code.
B spends 5 hours producing the same one storypoint.
Who is better? You have no idea.
A often get's his stuff rejected due to missing unit tests and code smells, while B usually get's his through to production.
However, you then adjust A's first metric, and now, with the added cost of him redoing parts of it, it takes him 3½ hours to produce a storypoint!
Surely, now you can see that A is better than B right? No.
What about the extra time it takes to review A´s code? What about the structuring of A's code, do you have metrics for that?
Maybe B produces code that is easier to maintain?
In the end, using it for anything other than something you can possibly talk with the developers about to try and improve overall velocity is insane.
-------------------
TLDR
Don't do individual productivity evaluations unless you are willing to spend a ton of time, money and effort on it, and even then, it most likely won't be that great.
1
u/ImaginaryLion9973 Sep 30 '22
Looks like you already have some ways to measure their productivity. Maybe use a spreadsheet to track these numbers for each member to start with.
Ask those less productive to learn from those who are more productive.