The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
|Content Last Reviewed||
Thanks for visiting the DORA Metrics direction page. This page is actively maintained by the Optimize group. You can contribute or provide feedback by:
Using DORA metrics, Gitlab accelerates engineering work in the context of end-to-end value delivery.
DORA (DevOps Research and Assessment) metrics have become widely recognized and adopted as industry standards for measuring DevOps performance. Software leaders find DORA metrics very useful for measuring the outcome of DevOps because they provide valuable insights into the effectiveness and impact of their DevOps practices. DORA metrics are derived from extensive research conducted by the DevOps Research and Assessment (DORA) team, which has identified a set of key metrics that correlate with high-performing software delivery and operational excellence.
The DORA team, has created a list of four metrics that are straightforward, focused, and easy to implement. They form an excellent foundation for data-driven initiatives, helping improve existing DevSecOps efficiency while also building a bridge to business stakeholders.
These four "DORA" metrics are:
DORA metrics are available in GitLab Value Streams Dashboard, Insights reports and in the CI/CD analytics reports. APIs are also available for all four DORA metrics. In GitLab, DORA metrics are embedded as part of the Value stream management end-to-end DevOps analytics framework. With DORA Metrics, Gitlab's VSM is visualized the work in the context of the value stream - measuring the velocity and stability of software delivery lifecycle through the DORA4 metrics.
The following video provides a brief overview of Gitlab's DORA metrics:
The DORA metrics are not intended to be a one-size-fits-all solution but rather provide a set of key metrics that organizations can use as a starting point to assess their DevOps performance. While there may be variations and adaptations of these metrics based on specific organizational contexts, the core principles and concepts outlined by DORA have had a significant impact on the DevOps community and are widely regarded as industry standards for measuring DevOps success.
To learn more check out the DORA documentation.
Enhance usability: Deliver excellent "out-of-the-box" experience for ~"Category:Value Stream Management" to visualize for everyone the unique power of measuring software delivery value in a single DevSecOps platform. To achieve this, we will focus on:
Demonstrate value of tier upgrades to drive progress on GitLab strategic pillar of Customer Results. To achieve this, we will focus on:
Top 3 Competitors:
Based on our analysis, we've identified Planview-Tasktop as the Best In Class (BIC) competitor over Digital.ai and Plutora.
Digital.ai AI-Powered DevOps platform. Digital.ai has been on a multiyear, multiacquisition journey that includes Arxan, CollabNet VersionOne, Experitest, Numerify, and XebiaLabs. Its plan to be a front-runner in AI-driven software delivery for Global 5000 enterprises.
XebiaLabs' analytics (acquired by Digital.ai) are predominantly focused on the Release Manager and give useful overviews of deployments, issue throughput and stages. The company integrates with JIRA, Jenkins, etc and end users can see in which stage of the release process they are.
Plutora Analytics Plutora is a privately held global software (SaaS) company, providing Value Stream Management solutions for enterprise IT in the areas of Release Management and Orchestration, Test Environment Management, Deployment Management, and Analytics.. Plutora seem to target mainly the release managers with their Time to Value Dashboard. The company also integrates with JIRA, Jenkins, GitLab, CollabNet VersionOne, etc but there is still a lot of configuration that seems to be left to the user.
More competitors in our Landscape:
CloudBees DevOptics is focused on giving visibility and insights to measure, manage and optimize the software delivery value stream. It allows comparisons across teams and integrates with Jenkins and Jira and SVM /VCS solutions.
CollabNet VersionOne provides users with the ability to input a lot of information, which is a double edged sword as it can lead to duplication of effort and stale information when feeds are not automated. It does however, allow a company to visualize project streams from a top level with all their dependencies. End users can also create customizable reports and dashboards that can be shared with senior management.
Targetprocess tries to provide a full overview of the delivery process and integrates with Jenkins, GitHub and JIRA. The company also provides customizable dashboards that can give an overview over the process from ideation to delivery.
Although GitPrime doesn't try to provide a value stream management solution, it focuses on productivity metrics and cycle time by looking at the productivity of a team. It uses only git data.
Similarly to GitPrime, Code Climate focuses on the team and uses git data only.
Similarly to GitPrime, Gitalytics focuses on the team and uses git data only.
CA Agile Central combines data across the planning process in a single integrated page with custom applications available to CA Agile Central users. The applications can be installed in custom pages within CA Agile Central or on a dashboard.
This category is currently at the Minimal maturity level, and our next maturity target is Viable (see our definitions of maturity levels).
For DORA Metrics, we are targeting the following personas (in priority order):
When I am new to value stream practices; I want to learn what’s important, why it’s important and how to use it, so that I can use the tool effectively and adapt to my organisation’s needs.
|When I am new to value stream practices; I want to learn what’s important, why it’s important and how to use it, so that I can use the tool effectively and adapt to my organisation’s needs.||Not validated||Issue|
When I am establishing practices to measure my value stream, I want to define the flow of work required to ship value to my end users so that we can visualize how efficiently and reliably value is delivered.
|When I am establishing practices to measure my value stream, I want to define the flow of work required to ship value to my end users so that we can visualize how efficiently and reliably value is delivered.||Not validated||Issue|
When I track my value stream I want to quickly understand the software delivery status so we can improve our performance in near real-time and enforce DevOps best practices and governance.
|When I track my value stream I want to quickly understand the software delivery status so we can improve our performance in near real-time and enforce DevOps best practices and governance.||Not validated||Issue|
When I am optimizing my value stream, I want to identify opportunities for improvement, or detect risks in the delivery of value to customers.
|When I am optimizing my value stream, I want to identify opportunities for improvement, or detect risks in the delivery of value to customers.||Not validated||Issue|
When evaluating my value stream, I want to link software delivery metrics to value metrics so that I can understand the value of the software workstream.
|When evaluating my value stream, I want to link software delivery metrics to value metrics so that I can understand the value of the software workstream.||Not validated||Issue|
In The Future of DevOps Toolchains Will Involve Maximizing Flow in IT Value Streams, Gartner recommended that "infrastructure and operations leaders responsible for selecting and deploying DevOps toolchains should: drive business ability by using DevOps value stream delivery platforms that reduce the overhead of managing complex toolchains."  By providing an entire DevOps platform as a single application, GitLab is uniquely suited to provide end-to-end visibility throughout the entire lifecycle without the “toolchain tax.” As the place where work happens, GitLab can also unite visualization with action, allowing users to jump from learning to doing at any time, without losing context.
Forrester's New Wave: Value Stream Management Tools, uncovered an emerging market. However, vendors from different niches of the development pipeline are converging to value stream management in response to customers seeking greater transparency into their processes.
Forrester’s vision for VSM includes:
Other Analysts have highlighted that GitLab data gathering has much to offer and much more to mine and enable the insight generation. We have an immediate opportunity to extend the insight generation based on the data gathered in the delivery pipelines. Once this is achieved we will integrate additional data sources beyond the DevOps toolchains.
We have the ability to reach the decision makers that are consuming the insights generated from the GitLab platform, and one of the key elements here is getting beyond the DORA 4 metrics into those that are more specifically targeted: security, compliance, financial, product, but also enterprise architecture, AI/ML delivery teams and the like.