Measuring Software Delivery Performance: Introducing Harness Dashboards
Tags: cicd, cloudcostmanagement, continuousdelivery, ci
Published: 2022-02-15 01:49:39

---
title: Measuring Software Delivery Performance: Introducing Harness Dashboards
published: true
date: 2022-02-10 14:00:00 UTC
tags: CICD,CloudCostManagement,ContinuousDelivery,ContinuousIntegration
canonical_url: https://harness.io/blog/harness-dashboards/
---

Harness’ custom dashboards help inform operations, identify bottlenecks, and drive business outcomes by monitoring, analyzing, troubleshooting, and visualizing key performance indicators. In using Harness’ custom dashboards, you will experience the full functionality of a self-service dashboard to help track software delivery velocity and performance, track builds and deployments and analyze cost of infrastructure in real-time. 

Enabling data-driven decisions to measure software delivery metrics involves, at its core, 3 things: capturing the data across different software systems, providing the ability to harness this data with self-service, and enabling collaboration with effective benchmarking. Before diving into how you can track your software delivery performance, let’s take a look at how one may define it. 

## What Is Software Delivery Performance?

In the past, software delivery performance was measured based on “outputs” such as code, velocity, and  acceleration to name a few. Nicole Forsgren et al, in their book [Accelerate: Building and Scaling High Performing Technology Organizations](https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr_1_3?gclid=CjwKCAiAp8iMBhAqEiwAJb94z4bdmqEk06hR8cPwpjfAnOd7vUGcTlgWEiWRuGe_NzgFg95JQVPI2BoC4j0QAvD_BwE&hvadid=256453993652&hvdev=c&hvlocphy=9012115&hvnetw=g&hvqmt=e&hvrand=3258987986894756116&hvtargid=kwd-443770025745&hydadcr=16406_10303876&keywords=accelerate+nicole+forsgren&qid=1636985967&qsid=141-0424641-2034600&sr=8-3&sres=1942788339%2CB078K93HFD%2CB07J63DQB2%2CB01BXLYEQ0%2CB06XC623F4%2CB00N6PD7CO%2CB011N42DXI%2C1942788762%2C1733692940%2CB08BSXH7JJ%2CB007V6237Y%2C1093146621%2C1686534655%2CB00C0E15FI%2CB07CRS4NX6%2C3800659638), make a case for why performance needs to be driven by “outcomes.” They outline [4 criteria](https://harness.io/blog/dora-metrics/) to measure software delivery performance: lead time, deployment frequency, mean-time-to-restore, and change failure rate. 

Besides the above objective measures , there are certain intangibles that impact performance. These intangibles are harder to measure, but not impossible. Google, in its [famous research in 2015](https://cloud.google.com/architecture/devops/devops-culture-westrum-organizational-culture), after 200+ interviews looking at over 250+ attributes, found that “who is on a team matters less compared to how they interact.” Also, [Westrum’s typology of organizational culture](https://cloud.google.com/architecture/devops/devops-culture-westrum-organizational-culture) is an excellent way to measure such intangibles. 

At Harness, we strive for both: measure objective software performance, and periodically keep a pulse on subjective intangibles. Over the past few years, we have been working on disrupting software delivery, one building block at a time – Continuous Delivery, Continuous Integration, Cloud Cost Management, Feature Flags, and more to come! But how does one actually measure it?

## How Does One Measure Performance, Quality, and Efficiency? 

While the above modules help users build and deploy software quickly and efficiently with the right quality gates and governance, it is equally important to visualize this information, track and benchmark key metrics, and share them with the right stakeholders. We interviewed over 50 customers across various industry segments and sizes, and found the need for measuring software delivery performance to be twofold. 

1. Engineers/Dev Managers: Want visibility into the metrics that revolve around the services and applications they manage so they can identify bottlenecks, measure outcomes, and improve them over time.
2. Executives/CIOs/CEOs: Want visibility into how the organization is performing, benchmark metrics across teams and the industry, and determine the outcomes of their investments in software tools as they scale. 

## How Are We Enabling This at Harness?

At Harness, we have been working on [dashboards](https://ngdocs.harness.io/category/id0hnxv6sg-dashboards-custom) that allow you to identify bottlenecks, inform operations, and help drive business decisions. The information and actual metrics may vary based on how engineering teams develop their product. 

We decided to do the following to help our customers with the right level of information. 

1. Offer a library of curated dashboards as part of our upcoming platform update to objectively measure software performance. The DORA metrics covered in the previous section, with the ability to query nearly all of the software inventory and its utilization, are some examples that are made available out of the box. 
2. While it is impossible to predict all the scenarios our users will want to visualize, it is definitely useful to provide a mechanism for them to be able to build their own. We offer a self-service dashboard creation and editing experience. 

Dashboards are available across data that spans all modules – Continuous Delivery, Continuous Integration, Feature Flags, and Cloud Cost Management. 

![Pre-Built Dashboards](https://blog.harness.io/wp-content/uploads/2022/02/image-1-1024x485.jpeg)

The following are some key capabilities that dashboards supports:

- Curated list of dashboards across all modules to measure software delivery performance.
- Ability to create and edit dashboards with access to key metrics that drive software outcomes.
- Robust reporting with the ability to export data, create scheduled reports, and set alerts.
- Access to the underlying data model to create cross-module dashboards for end-to-end visibility.

Here are some examples across each module. Each probably deserves a blog post of its own.

### Continuous Delivery:

![Continuous Delivery Dashboards - Failure Rates](https://blog.harness.io/wp-content/uploads/2022/02/Continuous-Delivery-Dashboards-Failure-Rates-1024x516.png)

![Continuous Delivery Dashboards - Deployment Frequency](https://blog.harness.io/wp-content/uploads/2022/02/Continuous-Delivery-Dashboards-1024x458.png)

### Cloud Cost Management: 

![Cloud Cost Management Dashboards - Most Expensive Clusters, Namespaces, Workloads, Nodes](https://blog.harness.io/wp-content/uploads/2022/02/Cloud-Cost-Management-Dashboards-1024x596.jpg)

![Cloud Cost Management - Build Failure Rate](https://blog.harness.io/wp-content/uploads/2022/02/image4-1024x481.jpg)

### Feature Flags:

![Feature Flags Analytics](https://blog.harness.io/wp-content/uploads/2022/02/Fearture-Flags-Analytics-Dashboards-1024x598.jpg)

## Conclusion

It doesn’t stop here! As we continue adding additional modules to the Harness platform, we’ll of course support data for dashboarding. Our goal is to provide end-to-end visibility across all building blocks that constitute a robust software delivery platform. 

To see dashboards in action, go ahead and [sign up](https://app.harness.io/auth/#/signup/) for your Harness account today. If you need some help on what to dashboard, check out our post on [Dashboarding](https://harness.io/blog/dashboarding-data-visualization/). It has a bunch of examples on what’s important to measure.

The post [Measuring Software Delivery Performance: Introducing Harness Dashboards](https://harness.io/blog/harness-dashboards/) appeared first on [Harness](https://blog.harness.io).