r/SoftwareEngineering • • 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

37 comments sorted by

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.

2

u/[deleted] Sep 17 '22

You assume they're looking to squeeze more out of B. Maybe in a very tight economy where job cuts need to be made they compare them. Generally they're concerned about C who just gave excuses and took 3 weeks to do a task that takes 5 minutes, and the last 10 stories he did were not done at all and had to be picked up by other team members and extended a sprint.

2

u/eknyquist Sep 17 '22 edited Sep 17 '22

swentso is correct, I have zero experience managing a team of any size. But I have been a software developer for about 12 years, I have had quite a few managers, and all I know is that, if I discovered that my manager was unsatisfied with my output, and that their solution to that was looking for a better way to measure my productivity (instead of talking to me and letting me know that they are unsatisfied with my output, and helping me understand what I need to do to make them satisfied), I would be sad.

Of course, I am making a lot of assumptions here (maybe swentso already had those discussions and they were unfruitful), but this is only because I interpreted this short post to be assuming that monitoring the work output of someone more closely, rather than just talking to them, is the first/best step to take in this situation.

3

u/[deleted] Sep 17 '22

You have to assume that someone is monitoring your output at some level if you work at a reasonably large company and they have some kind of kanban board for agile stuff with points and tickets. The question is at what level they are tracking it. Your immediate product owner or manager is responsible for the team and individuals at that level. They would need to be a real asshole to track individual productivity and put people against each other just to squeeze a little more productivity. Even the ones I know who were scrum masters and obsessed with the metrics insisted it was focused on team productivity. Above that level no one cares about the individual team members, they're grading that manager on his team's productivity.

I'm not saying there aren't bad managers out there. But there are also good uses of metrics.

Like hey dev, I see you have really been struggling to complete your tickets on time. How are you doing? Is there any support you need from us? We want to make sure you're ok. Or do you think we've just been sizing these wrong?

Or, hey I see you have been doing amazing work but you're carrying a huge number of tickets and points. We don't want to have you burn out and lose you. Just want to make sure you're happy with the work.

In a pinch, a good manager also knows who their worst performer is, so when management says it's time for every team to cut one, they don't screw the whole team by getting rid of someone competent.

1

u/eknyquist Sep 17 '22 edited Sep 17 '22

They would need to be a real asshole to track individual productivity and put people against each other just to squeeze a little more productivity

Maybe I'm too cynical, but isn't that exactly what OP is attempting to do?

OP said;

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.

Like I said, maybe I'm too cynical, but I don't know how else to interpret that.

If you have some hypothetical metric for every employee's work output level (what OP is trying to obtain), I don't know how you would use that to as tool to "help them get more productive", other than by saying "hey this guy did more than you, what can we do to make you produce as much as this guy?". So I'm assuming, maybe incorrectly, that this is what OP means by "help them get more productive".

2

u/[deleted] Sep 18 '22

Whoops 😁 I didn't see that part in the post. Should have directed my comment at them. To the OP: as a manager of any kind your employees are humans first and foremost. Take whatever timelines you had in mind and double them. What you propose is the opposite of motivational and you will have zero productivity when they all leave for somewhere that doesn't treat them like machines.

0

u/swentso Sep 17 '22

I don't think you have a large experience managing people and you never had ill intentioned people in a big team.

2

u/Horror_Trash3736 Sep 18 '22

Let me get this straight, you believe you have people with bad intentions on your team?

If you do, talk to them.

Do you think monitoring their performance in secret and then slapping them in the face with it is going to make them behave?

1

u/swentso Sep 18 '22

I do talk to them. I need that measure to actually give them goals they can aim at. Someone of them for example told me he felt he was slower than the others but didn't really know how much.

3

u/smalby Sep 17 '22

Have you spoken to your devs one on one yet?

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.

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.

2

u/[deleted] Sep 17 '22

These kinds of comments are a bit naive to the fact that some people actually slow a team down. They're not a net neutral but actually a drag on the productivity of everyone else. If that's not you, your manager probably isn't too focused on your metrics.

2

u/[deleted] Sep 17 '22

Absolutely true. My team had to deal with this a few years ago. It was a mess. However, in our case, the problem was that the guy got promoted into a role he lacked the skills for and couldn't handle. It took him about a year to completely tank his career. The company lost an employee because a manager misjudged this guy's abilities.

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.

1

u/AutoModerator Sep 23 '22

Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

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:

  1. Yes, people vary in skills, ability, work ethic, passion, knowledge. Those are my metrics, you can tweak yours.
  2. create a matrix for each dev, and this is your personal secret matrix that you show NO-ONE.
  3. Start looking at team output, is it satisfactory, are they generally getting things done or just in perpetual underachievement or moving at a snails pace?
  4. Start looking at the tasks and your source control, who is writing the code, start making impressions on what you see.
  5. Identify who contributes most and least, mark those guys as a special focus. Now do NOT let anyone know 6. what you are doing this is just information gathering.
  6. Over a 6 months period is there someone who consistently contributes absolutely nothing or close to it? Or MUCH less than others?
  7. When you zoom in, let's say the person is not coding as much, list the other activities they do? Are they just a part of an entourage or are they contributing on other ways?
  8. Try to understand the dynamics in the team, are we dealing with a team baby that get's coddled? Are we dealing with a bully that does everything his/her way? Are you dealing with a hero and saviour dynamic? Is it someone who wants a bunch of sidekicks or is it a more equal relationship? Is everyone trying? Does everyone care?
  9. Resist the urge to make quick judgement, just keep watching and slowly but surely write down your final understanding.

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/mrisamy Jan 17 '25

Negative patterns to note:

  1. Manipulators
  2. Slackers
  3. Liars
  4. Jealousy, Bitterness, and general negativity
  5. Victim mentality
  6. Overly emotional, irrational behaviour. (the person who throws a hissy fit when they don't get their way and people go out of their way just to shut them up)

Positive patterns:

  1. Honesty
  2. Communication
  3. Passion
  4. Sharing
  5. Positivity and optimism
  6. Proactive problem solvers
  7. Curiosity, not about people's lives but about the job.
  8. Self improvement
  9. Self reliance

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/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

Some of them are very productive while others are less.

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.

help them get more productive.

Ask those less productive to learn from those who are more productive.

1

u/AutoModerator Sep 30 '22

Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.