What project/team-based developer metrics do you track?

Question

Metrics such developer frequency, mean time to restore service, etc.Curious to hear of other metrics being used and how they've proven useful.Cheers!

welder · Accepted Answer

We track dev time spent typing, but only for gamification and individual productivity, using https://wakatime.com.

sethammons · Answer

Cycle time (how long to complete tasks on average), number of customer found defects, MTTR (mean time to resolution) for production issues, SLO violations, velocity (story points completed on average), number of alerts, and probably more. We track it for ourselves, not for comparison with other teams. And these metrics are at the team level, never individual.

tanseydavid · Answer

Planned vs. Unplanned work Fairly easy-to-capture. Can be very coarse-grained and still have lots of meaning.(note: get this one ironed out before trying to calculate a Velocity metric)

tsamtsam · Answer

SLA - time taken per team to resolve tickets filed by users/internal staff
Downtime of services
Number of crash/non-fatal logs seen in logging services (you could be using Sentry, Firebase, etc)
Just a few things tried and monitored at my company.

What project/team-based developer metrics do you track?

Metrics such developer frequency, mean time to restore service, etc.
Curious to hear of other metrics being used and how they've proven useful.
Cheers!

We track dev time spent typing, but only for gamification and individual productivity, using https://wakatime.com.

Planned vs. Unplanned work Fairly easy-to-capture. Can be very coarse-grained and still have lots of meaning.
(note: get this one ironed out before trying to calculate a Velocity metric)

SLA - time taken per team to resolve tickets filed by users/internal staff
Downtime of services
Number of crash/non-fatal logs seen in logging services (you could be using Sentry, Firebase, etc)
Just a few things tried and monitored at my company.

What project/team-based developer metrics do you track?

Metrics such developer frequency, mean time to restore service, etc.Curious to hear of other metrics being used and how they've proven useful.Cheers!

We track dev time spent typing, but only for gamification and individual productivity, using https://wakatime.com.

Planned vs. Unplanned work Fairly easy-to-capture. Can be very coarse-grained and still have lots of meaning.(note: get this one ironed out before trying to calculate a Velocity metric)

SLA - time taken per team to resolve tickets filed by users/internal staffDowntime of servicesNumber of crash/non-fatal logs seen in logging services (you could be using Sentry, Firebase, etc)Just a few things tried and monitored at my company.

Metrics such developer frequency, mean time to restore service, etc.
Curious to hear of other metrics being used and how they've proven useful.
Cheers!

Planned vs. Unplanned work Fairly easy-to-capture. Can be very coarse-grained and still have lots of meaning.
(note: get this one ironed out before trying to calculate a Velocity metric)

SLA - time taken per team to resolve tickets filed by users/internal staff
Downtime of services
Number of crash/non-fatal logs seen in logging services (you could be using Sentry, Firebase, etc)
Just a few things tried and monitored at my company.