Report metrics

Understand Flow's metrics.

Articles

Can’t you just "game" the metrics?
This question comes up quite a bit, and the answer is please do! Let's take a look at what gaming the numbers on a few key metrics might look like: Unreviewed PRs: Unreviewed PRs is the percentage of merged pull requests that did not receive...
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...
Delivery metrics
The delivery metrics are found in the Ticket log , Retrospective , and Sprint movement reports. The delivery metrics help you manage workflow and efficiency. This article goes over the details of these metrics and show you how they correspond to...
Review Metrics
Review metrics provides a way for software teams to see the ground truth of what’s happening in the code review process. The package is split into three sets of metrics: Submit , Review, and Team collaboration . The four Review metr...
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 Recept...
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?
What is a commit complexity? On a large team, picking which commits to review can be pretty arbitrary. Even with diligent, daily code review, it's very difficult to know which of the 100+ commits should be selected for review. Commit complexit...
What is a Coding Day?
On large teams, it can be very difficult to see who is succeeding and who is struggling, or how the team as a whole is doing. Setting a standard around checking in code every day is a simple yet powerful target, acting as a Getting Things Done-esq...
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 helps you see the different types of work: New work—Brand new code that does not replace other code.   Legacy refactor—Code that updates or edits old code. Help others—where a developer modifies someone else&rsqu...
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 ...
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 at how ...
Industry benchmarks
Industry benchmarks are reference points 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 article Whe...
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 creation time i...
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 ...
Reaction time
Reaction time is the average number of hours it takes for an individual or team to respond to a set of PRs where they are a reviewer. In this article Which reports use Reaction time? What does Reaction time measure? How is Reaction time...