Understand how healthy is the activity of your team with an easy-to-read metrics of your engineering teams.
Review engineers non-coding routine to increase the number of active coding days.
Peer review is most effective with small commits. Engineer who is contributing rarely most likely hoards large commits. To confirm, you can check this in Oversized PR’s in Process health.
Working days, nights and weekends is fantastic. But not sustainable in the long term, watch out for burnouts in your teams by tracking active days calendar.
Spotted an abnormally high churn? Whoops, maybe your team needs more training or a consult from an area owner that can be identified on a Confidence map.
Use team activity data and engineer insights to prepare for 1 on 1’s.
Proportion of changes made by the team within the organization or by an engineer within a team.
Proportion of fresh code in relation to all changes made.
Commits that rewrote parts of the freshly committed code authored by the same engineer.
Commits that rewrote parts of the freshly committed code authored by another engineer.
Commits that rewrote parts of the code that no one has changed in a while.
A day counts as active if there was at least 1 commit, review or comment. Median value for longer time periods includes data only from active weeks.
A week counts as active if it includes at least 1 active day.
This page was last revised on March 3, 2021Return to main