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.
|Category||Value Stream Management|
|Content Last Reviewed||
Thanks for visiting the Value Stream Management direction page. This page is actively maintained by the Optimize group. You can contribute or provide feedback by:
Using The One DevOps Platform Value Stream Management provides end-to-end visibility to the entire software delivery lifecycle - enabling teams and managers to understand all aspects of productivity, quality and delivery without the “toolchain tax”.
Value Stream Management helps organizations understand and optimize the impact of their activities across the DevOps lifecycle by:
To achieve this, users can map Value Streams and finds bottlenecks in their process. Value Stream Analytics provide a high-level overview of end-to-end cycle and stage times and is the starting point for drilling down into each stage of a value stream to identify opportunities for improvements.
In addition to the custom value streams that can be built in VSA, the Optimize group maintains GitLab Insights, which allows users to create custom reports to show the type, velocity, and quality of work.
A new DORA Metrics category was split from Value Stream Management align our messaging with the market. The DORA Metrics will continue to be the core measurements for value stream performance, and will remain embedded in Value Stream Analytics flow.
GitLab will be the tool of choice for the data-driven DevOps organization — enabling teams and managers to understand all aspects of productivity, quality and delivery without any complex configurations or data scientists.
For Value Stream Management, we are targeting the following personas (in priority order):
In order to reach our vision we will focus on:
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|
TaskTop is exclusively focused on Value Stream Management and allows users to connect more than 50 tools together, including Atlassian's JIRA, GitLab, GitHub, JamaSoftware, CollabNet VersionOne, Xebia Labs, and TargetProcess to name a few. Tasktop serves as an integration layer on top of all the software development tools that a team uses and allows for mapping of processes and people in order to achieve a common data model across the toolchain. End users can visualize the flows between the different tools and the data can be exported to a database for visualization through BI tools.
While we understand that not all users of GitLab utilize all of our stages, we believe that there is already a lot of information across planning, source code management and continuous integration and deployment, which can be used to deliver valuable insights.
We are starting to build dashboards, which can help end users visualize a custom-defined value stream flow at a high level and drill down and filter to a specific line of code or MR.
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.
Plutora Analytics 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.
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 exclusively 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.
XebiaLabs' analytics 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.
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.
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.
Forrester's New Wave: Value Stream Management Tools, Q3 2018 uncovered an emerging market with no leaders. 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 i 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 onsuming 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.
Additional functionality, requested by clients includes: