top of page


Empower Your CI/CD Cycle Combining DORA Metrics and Development Behaviors

Instead of looking for static reports on DORA metrics, understand your capabilities on the delivery process with additional 10+ other insights to improve your development cycle in every aspect.


DORA Metrics Overview

DORA metrics are one of the key components analyzing the CI/CD performance of your company. Your team can understand the missing parts and explore new approaches to improve the continuous delivery process.

Deployment Frequency

How frequently the team can successfully release software updates to production.

Lead Time For Changes (LTC)

Reflects the time from a commit change to a deployable state of the commit.

Mean Time To Recover (MTTR)

When any interruption occurs in the deployment process, this measures the time from the incident to full recovery and successful deployment.

Change Failure Rate (CFR)

Measures the rate of failures caused by the changes or fixes after the code deployment.


Explore the details of your deployment process and complete the missing parts to improve your CI/CD capabilities.

New Approach To Have Better DORA Metrics

Valven Atlas offers DORA Metrics insights and correlates these insights with other development cycle behaviors of your team to take you beyond the DORA Metrics and introduce new ways to improve the performance on feature, product shipping capabilities. 


Valven Atlas uses data it gets from the integrations to your Version control systems and issue management systems. We combine DORA metrics with various other analyses to highlight the issues better.

Deployment_Cycle-Time .jpg

Deployment Frequency

Deployment Frequency defines how fast a team can finalize releases with deployment into production.


By combining the frequency analysis with PR volumes and cycle time analysis Valven Atlas helps you identify the issues in the process and highlights the parts your team needs to improve.

Lead Time Changes

Lead Time Changes metric reflects the time for each commit to deploy into production and be enabled for the customer 


Combining this metric with the most inefficient step in the development cycle and the number of PRs in the defined period enables us to highlight the relation between development behaviors and the success of applying new code changes.


Mean Time To Recover

Mean Time to Recover shows the performance of the team in terms of the team’s ability to recover from a faulty release. 


While combining this metric with the largest recovery releases to identify the problems in these releases, Valven Atlas also highlights the team effort on recovery releases to realize the effort put into such releases.

Change Failure Rate

Change Failure Rate shows the faulty release ratio in the total releases your team completes in different time periods.


Since faulty releases may be a result of an insufficient review process, Valven Atlas correlates the review focus with the failure rate to eliminate the additional time you may lose to find the review-related problems.


Explore What Is Possible For Your Team

Start your journey for the better

bottom of page