Coding Days

Coding days is defined as the number of working days that engineers have done at least 1 git commit.

Computation of the metric

1. Computed using the commit activity of teams and members.
2. GIT/VCS tools provide the data used to analyse the commit activity.
3. Coding days is 100% if there was at least 1 commit for each working day in the week (Mon-Fri)
4. Coding days can be >100% if the number of coding days > number of work days, i.e., there is a commit on Sat/Sun.

Dashboards where this metric is used

1. Dev Summary
2. Dev Metric Grid
3. Dev Throughput

Use cases of this metric

1. Use this metric to understand what % of days an engineer / team is contributing code (via a git commit)
2. If the team does not have a practice of commit code frequently this metric will surface that
3. For developers that routinely have low coding days, use the activity log to understand what other engineering activities are consuming their time - such as PR reviews etc. Also use the Developer Summary dashboard to understand if their time is being spent in meetings
4. Coding days are a potential indicator for low focus and burnout.