Coding metrics

Learn more about the four core Coding metrics in Flow In this article Rework and efficiency Commits per active day Coding days per week Impact How are team averages calculated? Rework and efficiency Rework is code delet...

On a large team, picking which commits to review is often arbitrary. Even with diligent, daily code review, it's very difficult to know which of your commits should be selected for review.   Commit complexity is a measure of how like...

Coding days is the average number of days per week a developer contributes to the code base by making at least one commit. In this article Which reports use Coding days? What does Coding days measure? How is Coding days calculated? ...

Impact is a way to measure the ‘bigness’ of code changes that are happening, in a way that goes beyond simplistic measurements like lines of code.   Impact attempts to answer the question: “Roughly how much cognitive lo...

Flow breaks work types into four metrics: New work tracks new code that doesn't replace other code. Legacy refactor tracks old code that gets updates or edits. Help others tracks when a developer modifies someone else’s recent work. ...

Rework is when an engineer rewrites or deletes their own code that is less than three weeks old. Some rework is expected. For example, a rework rate of 9-14% for a senior engineer can be normal.   But unusual spikes in rework can indica...

Time to 100 , or tt100, is the amount of time it takes an engineer to write 100 productive lines of code and a way to assess how quickly the codebase is being meaningfully edited.   How the time part is calculated We start by looking a...

Commits per day is the average of included commits a developer submitted on coding days . In this article Which reports use Commits per day? What does Commits per day measure? How is Commits per day calculated? What data does Com...