Category Direction - DevOps Reports

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.

Introduction and how you can help
Overview
- Themes
Jobs to be done
What's Next and Why
Maturity Plan

Category	DevOps Reports
Stage	Plan
Group	Optimize
Maturity	Minimal
Content Last Reviewed	`2023-03-31`

Introduction and how you can help

Thanks for visiting the direction page for DevOps Reports in GitLab. This page is being actively maintained by the Product Manager for the Optimize group. If you'd like to contribute or provide feedback on our category direction, you can:

Comment and ask questions regarding this category vision by commenting in the roadmap epic for this category.
Search for specific issues in this category using the Category:Devops Reports label.

Overview

GitLab has extraordinary breadth for a single application, providing an entire DevOps platform from portfolio planning all the way through to monitoring and service desk. As such, GitLab is uniquely positioned to provide a complete picture of your organization's DevOps journey and your return on investment in automation and DevOps practices.

GitLab shows adoption of key GitLab features across an organization, with a breakdown by sub groups. This provides insight into which groups are using each feature. The DevOps Reports category aims to extend the current functionality to answer questions such as:

How many of my teams are doing security scans?
How much progress has my organization made on our DevOps journey?
How has the adoption of DevOps practices changed software delivery performance?
Which teams have achieved the highest performance? What tooling did they use to accomplish this?
Which teams need help with DevOps adoption? Which teams are best positioned to provide this help?

Themes

Adoption insights
- Understand how teams are using GitLab
- See which teams across your organization have adopted specific DevOps practices and learn from their experiences.
- Find teams that have not adopted specific practices and find out how you can help with adoption
- View the percentage of key DevOps practices your organization has adopted to understand the status of your DevOps journey and the return of investment you are getting from GitLab
- Measure progress on initiatives such as the adoption of security scanning to comply with industry regulations, or the addition of Codeowners to help identify who needs to review contributions to a repository
- Track progress on migrating to GitLab from other tools that serve a single stage of the software development lifecycle. See which teams are yet to transition across.
Adoption trends
- See how GitLab adoption is changing over time
- See which GitLab features are being adopted most rapidly
- Identify potential issues such as adoption of a feature followed by decline in usage of that feature. This could indicate a need for training on how to use the feature
- Find where uptake has been slow. This may indicate a lack of awareness of the feature.
Maturity of adoption
- It's not always enough to know whether a feature or DevOps practice has been adopted. DevOps Reports aims to go a step further and show maturity of adoption such as how often security scans are being run.
Correlation between adoption and performance
- See how adoption of DevOps practices has improved the speed and reliability of code development by viewing DORA metrics alongside DevOps adoption data.
- Identify highest performing teams based on DORA metrics and see what DevOps practices contributed to their success. Apply those learnings to other teams and track their progress on DORA metrics.
- Find teams that are struggling with a specific DORA metric, such as Deployment Frequency. Put together a set of recommendations aimed at improving performance in that area.
Customized insights
- Not all GitLab features are applicable for your application. We plan to support customizations to show only the data that is important to you. If you don't build web applications, hide features like Browser Performance Testing so they don't count towards your DevOps maturity score.
- Pick the three GitLab features you wish your organization was using better and customize the dashboard to track progress of just those features.
- Filter the dashboard to show only Ultimate features to more easily understand the value you are getting from the Ultimate tier.
Deep dive
- For each feature represented in DevOps Reports, link to key resources such as documentation so users can learn about the value of these features and how to use them
- Link to corresponding areas in the GitLab UI so users can drill in and get more detailed information on feature usage

Jobs to be done

Tracking DevOps transformation

When my organization is going through a DevOps transformation, I want to know how far along our DevOps journey we are and how this has impacted performance, so that I can monitor progress and report to leadership.

Job statements	Confidence	Source
When renewing my contract with a vendor, I want to demonstrate to leadership that the tool is being adopted and providing value, so I can justify the tool's expense.	Researched	Issue
When looking to upgrade my contract with a vendor, I want to demonstrate to leadership that teams have heavily adopted features in the current tier and are ready to get value from higher tier features, so I can justify the additional expense.	Researched	Issue
When consolidating my DevOps toolchain and/or migrating to a new platform, I want to track the progress of adoption across my organization, so that we can get the most out of our new investment and remove other tools.	Researched	Issue
When trying to improve organizational productivity with DevOps, I want to know which tools & practices are being used in high/low-performing teams, so that we can learn from their experience.	Researched	Issue

What's Next and Why

Adding "AI Adoption view" by adding "AI features" to the DevOps Adoption report
Make DevOps adoption report more granular.
Add a new Dashboard for Executive to enable decision-makers to identify trends, patterns, and opportunities for digital transformation improvements. In the first phases, we will focus on the following:
- Executive-level summary of key metrics related to software performance and flow of value across the organization.
- Visualizing metrics comparisons to help decision-makers understand how different metrics are performing relative to each other or to identify trends and patterns in the data.
- Filtering and drill-down into the underline data to get a deeper understanding of specific metrics or trends to identify actionable insights.
- Customizable widgets to show data that is relevant to user's goals and needs. Group Optimize is currently focused on usability improvements, aligned with the company goal to improve the SUS score.

Maturity Plan

This category is currently Minimal. The next step in our maturity plan is achieving a Viable state of maturity. We are tracking progress to reach this next maturity state in gitlab&1499.

You can read more about GitLab's maturity framework here, including an approximate timeline.