Report metrics

Understand Flow's metrics.

Team health insights metrics

Learn about the Team health insights metrics.

Articles

Can’t you just "game" the metrics?
This question comes up quite a bit, and the answer is complicated. First, what do you mean by gaming metrics? If you’re asking about whether you should change all of your coding habits just to get “good” metrics without considerin...
Flow metrics
A list of common metrics, their definitions and why they are important. In this article Coding metrics Submit metrics Review metrics Team collaboration metrics Knowledge sharing metrics Code metrics Coding days What...
Coding metrics
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 deleted or rewritten shortly after being written. Learn more...
Ticket metrics
Ticket metrics are found in the Ticket log , Retrospective , and Sprint movement reports. Ticket metrics help you manage workflow and efficiency. This article goes over the details of these metrics and how these metrics correspond to ticket co...
Review Metrics
Review metrics provide software teams insight into what’s happening in the code review process. Review metrics include: Reaction time is the average number of hours it takes for a reviewer to respond to a set of PRs as a reviewer. Invo...
Submit Metrics
The Submitter metrics make it easy to understand how PR submitters are responding to and incorporating feedback during the code review process. In this article Submit Metrics Responsiveness Unreviewed PRs Comments Addressed Recepti...
Team Collaboration Metrics
The Team Collaboration Metrics are designed to give managers a birds-eye view of how a team is behaving in the code review process. These metrics illuminate knowledge concentration centers, code that may require your attention, and bottlenecks to a...
How do you calculate commit complexity?
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
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? ...
What is Impact?
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 cognit...
What is New work vs. other work?
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. ...
What is rework?
Rework is when an engineer rewrites or deletes their own code that is less than 3 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 indicate v...
What is Time to 100?
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...
Industry benchmarks
Industry benchmarks are reference points for metrics based on the software development industry. Use industry benchmarks to see how your team compares with the industry. This helps you and your team identify potential areas of growth. In this art...
Time to merge
Time to merge is the average time in hours from when pull requests are created to when they are merged, rounded to the nearest tenth of an hour.   Note: If your Pull request tracking is set to First commented , the pull request cre...
Time to first comment
Time to first comment is the average time in hours from when pull requests are created to when they receive their first comment, rounded to the nearest tenth of an hour.   Note: If your Pull request tracking is set to First commen...
Unreviewed PRs
Unreviewed PRs is the percentage of merged pull requests that have no comments or approvals from non-submitter reviewers, rounded to the nearest tenth of a percent. In this article Which reports use Unreviewed PRs? What does Unreviewed PRs...
Responsiveness
Responsiveness is the average number of hours it takes for a submitter to respond after a reviewer action, rounded to the nearest tenth of an hour. In this article Which reports use Responsiveness? What does Responsiveness measure? How i...
Reaction time
Reaction time is the average number of hours it takes for an individual or team to respond to a set of PRs as a reviewer. In this article Which reports use Reaction time? What does Reaction time measure? How is Reaction time calculated? ...
Commits per day
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...