* general developer waiting times such as checkout times, build times, CI waiting times, IDE indexing times, build-run-test cycle times, etc
* Engineer % time in meetings based on calendars
* Amount of employee time spent interacting with bug tracker websites
You can also measure on business metric improvements such as profitability, increased revenues and so on.
These aren't good for measuring the productivity of any specific engineer, but they are great for measuring the productivity of the team / firm as a whole. You can also do projects to explicitly improve these metrics. And since they are numbers, they are far more attractive to managers to look at.
* code performance (speed, CPU, memory, frame drops, network speed, etc)
* hardware cost efficiency
* outage rates
* crash-free rates
* app freeze rates
* error rates
* general developer waiting times such as checkout times, build times, CI waiting times, IDE indexing times, build-run-test cycle times, etc
* Engineer % time in meetings based on calendars
* Amount of employee time spent interacting with bug tracker websites
You can also measure on business metric improvements such as profitability, increased revenues and so on.
These aren't good for measuring the productivity of any specific engineer, but they are great for measuring the productivity of the team / firm as a whole. You can also do projects to explicitly improve these metrics. And since they are numbers, they are far more attractive to managers to look at.