Engineering leaders need actionable insights about what their teams are working on, where things are going well, and where they should devote attention to improvements. These insights can come from a number of reports and metrics in Flow, but engineering leaders need to be able to see them at a glance, all in one place.
Executive summary combines Flow metrics to tell a cohesive story about how engineers are working—what's working, what isn't, and how those things fit together. This report combines git, PR, and ticket metric data to help you understand your team's development, collaboration, portfolio, and delivery patterns. Use and share this report so leaders at your organization can quickly see where their teams stand.
Tip: This report is most useful if you start with longer date ranges—more than a month—and larger teams. This helps you identify wider patterns in your organization before narrowing down to view more specific teams.
In this article
Permissions
You must have the Executive dashboard Report permission to view Executive summary.
Development
Use the Development section to understand how quickly you're delivering value to customers through your coding practices. This section focuses on the core Coding metrics—four metrics that use your git data to show the patterns and impacts of your development work.
Learn more about Coding days, Commits per day, Impact, and Efficiency. Each metric's value and trend is displayed for the selected time period and team.
Note: Trends only display if the selected date range contains four or more full Monday to Sunday weeks. Shorter time frames do not include trend data.
Use the Percentile benchmark indicators to understand where your team's metrics fall within Flow's benchmarks. Use this as a starting point to understand how you compare to other organizations. While every organization is different and you should make sure you understand what good looks like for you, it's generally true that the higher the percentile, the more high-performing your organization is.
To help you understand this at a glance, metrics in the 75th percentile have a green banner, metrics in the 50th percentile have a gray banner, and metrics in the 25th percentile have an orange banner.
Click View details to view each of these metrics broken down per immediate nested team of the parent team selection. Use this to understand how the aggregate metric values are impacted by individual team development patterns.
Delivery Workflow
Once you understand your development and collaboration patterns, use the Delivery Workflow section to understand how efficiently your processes have been set up so you can deliver that work.
Use the Tickets and PRs pie charts to understand what proportion of the PRs and tickets you've created have been able to be completed.
Tickets are only shown in the pie chart if they first moved into an Active status during the time period. Only tickets in a Done or Active status are included.
PRs are only shown in the pie chart if they were created in the selected date range and are currently either in a Merged or Open state.
Tip: Use this to understand how balanced you're able to be between creating and completing work. If you have more yellow uncompleted work than blue completed work, that can be a sign that your processes aren't allowing you to finish what you're working on before moving to something new. This delays customers from being able to benefit from your work and can be a sign of high context switching on your team.
Also use the Time to merge and Cycle time metrics to understand how long pieces of work are open. The longer something remains open before you can complete it, the more you risk delaying releases and causing extra cost to your business.
Portfolio status
Use the Work type allocation breakdown to understand what types of tickets you're working on. Tickets are separated into Feature, Defect, and Maintenance work based on your issue type mappings set up as part of ticket project configurations. This pie chart includes the Work type of all tickets completed during the selected time period.
Use this chart to understand how work of different types is balanced across your teams. Are some teams only doing maintenance work, while others are doing only feature work? Is the balance what you expect? The more this balance reflects the types and proportions of the work you expect your team to be doing, the more confident you can be in your ability to meet your delivery committments.
Tip: If you see any Unassigned work in this chart, review your ticket project configurations to ensure all projects and issue types are configured and mapped correctly
Collaboration
Use the Collaboration section to understand how your team is collaborating to deliver high-quality products to your customers through healthy review patterns.
This section focuses on Unreviewed PRs and Iterated PRs—these two metrics are excellent indicators of how well your teams are giving and reacting to feedback to improve your code. These metrics also are displayed with their matching overall values, trends, where applicable, and percentile indicators.