Measuring Individual Engineer Productivity
Individual engineer productivity is extremely difficult to measure. It is not simply looking at a single metric and then stack ranking based off of that metric. By definition, software engineers often spend their time working on branches that do not end up merged into production. So simply looking at PRs or commits often doesn’t take into account the work done on these “algorithm building” branches. Nor does it account for the work done by engineers reviewing and assisting others. Additionally there may be times where a lead engineer or architect is asked to spend time optimizing code or assisting in design work. Bottom line it is very hard to measure individual engineer productivity or effectiveness by looking at numbers.
Metrics do provide directional guidance in determining if an engineer needs help, is overwhelmed or for some unknown reason is delivery less work than their norm.
Director of Engineering
Monthly, Quarterly, On Demand
Monitoring Developer Productivity
Navigate to Reports (note: the Developer Productivity report is only available to administrators in paid accounts)
Select the metric you want to include on the Developer Productivity report
Issue Points Resolved
Create the report
What to look for? / What to do?
When reviewing individual delivery over time, the key is consistency. Individual delivery metrics should be about the same or trending upwards.
However, if you see something such as points or coding efficiency heading in the wrong direction, it is a worthwhile endeavor to check with the engineer on why??
If merited, track key engineer metrics over time with the engineer.
But overall - recognize that metrics only provide part of the picture and engineer’s influence often cannot be measured using numbers.
Do not hide the metrics from the individual engineer, include them in 1:1s as appropriate, but let them know that they are not being evaluated solely based on metrics.