Understanding Metrics Dashboards

Your Metrics tab has several pre-built dashboards available. You can also build as many personal custom dashboards as you would like. Learn more about building custom dashboards here: How Do I Build a Metrics Dashboard?

What can I do with a Metrics Dashboard?

Change Date Ranges

Click on the start and end dates to set the date range you'd like to observe. (Free plans can gather up to 45 days past, Pro subscribers 6 months, Enterprise plans 3 years.)

Switch Between Teams, Repos, and Services

Use the Filter by: option to quickly switch between teams, repos, or services to compare performance. You can learn more about making your own services within LinearB here: Service Metrics

Click Into Metrics Inflections to Investigate Spikes

Click on any date point in your Delivery dashboard to be taken to a list of the repos that contributed to that date-range.

Export PNG and PDF Reports

Use the icon to print PNG and PDF images of your report to share in presentations.

Available Metrics Dashboards

Delivery

The delivery dashboard breaks out your cycle-time into segments. Showing overall cycle time and individually coding, pickup, review, and deploy time.

Use this dashboard to identify increases in any segment of your development pipeline. Inefficiencies in any of these segments reduce your entire throughput.

Source: Data in the dashboard is gathered from Git, broken out by contributions by your selected team, team member, or specific repo.

Metrics included: Cycle Time, Coding Time, Pickup Time, Review Time, Deploy Time

Quality

Quality dashboards identify potential issues in code quality. Spikes in unreviewed PRs, or a drop in PR depth (the number of comments per PR) can lead to bugs down the line. I high refactor or rework rate indicates recently released code was not properly vetted prior to release. A high amount of new code should be reviewed carefully before release. An increase in PR size could be an indicator that projects need to be broken down into smaller, more manageable iterations.

Source: Data in the dashboard is gathered from Git, broken out by contributions by your selected team, team member, or specific repo.

Metrics included: PRs Merged w/o Review, PR Size, Review Depth, New Code, Refactor, Rework

Throughput

Monitor the amount of changes pushed through by teams, or conducted on your services using the throughput dashboard. From this dashboard you can see PRs opened vs PRs merged, the number of code changes and commits.

Compare throughput to your delivery and quality dashboards, spikes in cycle time, or a rise in code rework, will often correlate to a drop in throughput.

Set your dashboard to view specific repositories in order to monitor the activity on your specific services.

Source: Data in the dashboard is gathered from Git, broken out by contributions by your selected team, team member, or specific repo.

Metrics included: Code Changes, Commits, PRs Opened, PRs Merged, Reviews, Deploy Frequency

Project Management

This dashboard allows you to quickly see throughput of your project management issues. See issues completed, story points done, and MTTR (Mean Time To Restore). By default MTTR measures the time from between when a bug issue is opened to when the bug ticket is resolved.

Source: Data in the dashboard is gathered from your project management platform. If you haven't connected project management yet, you can learn how here: Connect LinearB to your Project Management Platform

Metrics included: MTTR, Issues Done, Story Points of Issues Done

Velocity

This provides a breakdown of how many tasks were completed during an iteration. Issues are determined by the ticket-types available in the project management board linked to your team.

You can display the performance of specific teams or issues-types. Use the search bar to isolate specific iterations. Read more about the Velocity report here: Metrics Dashboards: Velocity

Source: Data in the dashboard is gathered from your project management platform. If you haven't connected project management yet, you can learn how here: Connect LinearB to your Project Management Platform

Investment Profile

Critical in connecting engineering metrics to business value, this dashboard shows the total time spent in an iteration on different issue types. Use this to communicate with non-technical team-members how resources are being used.

You can use the search bar to view the time investment per sprint. Filter by project management board, issue type, and number of iterations. Read more about the Investment Profile report here: Metrics Dashboards: Investment Profile

Source: Data in the dashboard is gathered from your project management platform. If you haven't connected project management yet, you can learn how here: Connect LinearB to your Project Management Platform

Time Distribution

Similar to Cycle Time, but using project management data! This dashboard takes Jira or Shortcut (formerly Clubhouse) data and breaks it out by time spent in each ticket phase. Read more about the Time Distribution report here: Metrics Dashboards: Time Distribution

Source: Data in the dashboard is gathered from your project management platform. If you haven't connected project management yet, you can learn how to do so here: Connect LinearB to your Project Management Platform