We’ve streamlined several Flow reports and metrics so you can have the best experience across Flow. These changes make it easier for you to see the data you need without having to look in several places. We’re reducing complexity in Flow so it’s easier to focus on what matters to you.
As part of this, several changes are happening:
The most important Reviewer and Submitter metrics are now available in the Team health insights report. Since everything you need is now in Team health insights, we’ve removed the Reviewer and Submitter fundamentals reports.
The information from Player card is being added to Check-in.
Reaction time and Responsiveness have been refined according to customer feedback and are being added to Team health insights and Email reporting.
Five metrics that were better captured via other measures have been removed.
Review collaboration is updated with new metrics and redesigned to match other Flow experiences.
We’re excited about these changes, so in this article we’ll share more about why these changes are happening and how it will positively impact your experience with Flow.
Team health insights is now your one-stop-shop for coding and pull request metrics
In order for you to see everything you need in one place, we’ve removed Submitter and Reviewer fundamentals and added their most important metrics to Team health insights. This reduces the number of reports you need to visit in Flow to get clear visibility into your team’s coding and PR metrics.
Team health insights lets you select which metrics you want to view at once, so you can hone in on what’s important to your team. Our filter lets you easily change which metrics you see as your team’s needs change.
Learn more about how to use Team health insights to see where your team is succeeding and how you can help them.
Merged Check-in with Player card
We’ve moved Player card to a tab in Check-in so you can easily move between the context in Check-in and Player card when in 1:1s, instead of having to load two different reports during your conversation. This gives you more context so you can spark meaningful conversations with your team members.
You can customize what metrics appear in Player card so you can quickly see the information most important to you.
Refined definitions for Responsiveness and Reaction time
Responsiveness and Reaction time are two popular metrics featured in Reviewer and Submitter fundamentals. These metrics drive important insights into how your team members are reacting to each other’s comments and other activity in pull requests.
Because these metrics improve team performance and knowledge sharing, we’ve added them to Team health insights and made sure they’re also available in Email reporting.
Additionally, we’ve refined the way these metrics are calculated based on customer feedback so they better represent the work your team is doing.
Fewer metrics means you can easily see what’s most meaningful
When we looked at consolidating our fundamentals reports into Team health insights, we took the opportunity to evaluate how much value each metric added. In this investigation, we highlighted several metrics that weren’t frequently being used, were hard to understand or explain, didn’t measure what was most important, or some combination of the above.
After careful consideration, we removed five metrics so you can more easily see the measures that drive the most value in your organization.
Receptiveness and Influence
These metrics aimed to measure team collaboration dynamics by showing relationships between comments and follow-on commits, but we found they did not tell the whole story. If you want to understand if pull request reviews are happening and when they’re making a difference, check out the Iterated PRs metric.
Comments addressed and Review coverage
These metrics looked at data related to reviewer comments on pull requests. Because not every comment needs a commit, they were not always actionable.
If you want to understand how helpful reviewer feedback is on your pull requests, check out the Thoroughly reviewed PRs metric to see how often pull requests are getting detailed reviews.
Involvement measured what percentage of pull requests a reviewer participated in. When we looked at how this metric was being used, we realized any insights about how often reviewers were involved in PRs added more confusion than they did clarity or visibility.
If you want to see who is reviewing submitted code, check out the interactive mapping in Review collaboration to see how your team is collaborating.
Updated design and metrics for Review collaboration
As part of these changes, Review collaboration is updated to:
Match designs from the Retrospective report
Remove metrics that are captured elsewhere
Include Time to merge, Time to first comment, PR iteration time, Iterated PRs, and Thoroughly reviewed PRs
If you need help, please contact Pluralsight Support.