Report metrics

Understanding the Flow 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 Review & Collaborate metrics Review Metrics Team Collaboration Metrics Knowledge Sharing Metrics Code Metrics ...
Code Fundamentals Metrics
In this article Churn and Efficiency Commits per Active Day Coding Days Per Week Impact How are team averages calculated? Churn and Efficiency Churn is code which is deleted or rewritten shortly after being written. Read more on...
Delivery module metrics
Delivery reports use five metrics to help you manage workflow and efficiency: cycle time, queue time, backflow, jitter, and heat. In this article, we will go over the details of these metrics and show you how they correspond to delivery configuratio...
Review Metrics
Our review and collaborations report package 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...
Submit Metrics
As part of the review and collaborations report package, 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 Respons...
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 Risk?
What is a risky commit? 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. Risk is a measure of ...
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-esque...
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 ho...
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 Churn?
Code Churn is when an engineer rewrites or deletes their own code that is less than 3 weeks old. For example, a Churn rate of 9-14% for a senior engineer might be completely expected. Unusual spikes in Churn can be an indicator that an engineer is s...
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 can help you and your team identify potential areas of growth. In this article W...