Welcome
Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
Value stream metrics
Assess project quality, progress, and performance with the HCL DevOps Velocity (Velocity) metric data tools.
Customizing metric definitions for Lead Time, Cycle Time, and Dev Cycle Time

Release Notes
This document includes information about the new features introduced, defects fixed, and known issues identified in this version of HCL DevOps Velocity (Velocity). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document contains information about hardware and software requirements for HCL DevOps Velocity (Velocity).
Getting Started
This document provides an overview of HCL DevOps Velocity (Velocity).
High-Level Overview
Use HCL DevOps Velocity (Velocity) to automate your release lifecycle and manage your DevOps value streams.
Learning
Learn how to complete frequently-used tasks such as creating value streams.
Managing licenses
Configure your license or apply a trial key.
Administering
This guide describes how to install HCL DevOps Velocity (Velocity). After you install Velocity, you can perform administrative tasks such as license configuration, upgrading, migrating, managing access permissions and security. This guide is intended for system administrators.
Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
- Creating value streams
  Create a value stream and then customize it by defining phases and stages that reflect your typical workflow.
- Viewing value streams
  Viewing value streams using list and card view layouts.
- Value stream metrics
  Assess project quality, progress, and performance with the HCL DevOps Velocity (Velocity) metric data tools.
  - Displaying the metrics
    You can enable the Metric bar to display the metrics on the value stream.
  - Customizing metric definitions for Lead Time, Cycle Time, and Dev Cycle Time
  - Implementing custom metrics
    Provide custom metric data to your value streams and dashboards.
  - DORA metrics
    You can use DORA metrics to evaluate the performance of the team.
  - Milestone-risk estimation
    Milestone risk is a metric which measures the probability of a team that may not complete all of the current in-scope work in an active development iteration (sprint). The milestone risk estimator plug-in uses a stochastic machine learning (ML) algorithm to estimate and predict the potential percentage risk of non-completion of all work during an on-going sprint. To calculate this metric, the model uses all historical work items available in the selected value stream to train the model and extracts the required information to make the prediction.
  - Bottleneck detection
    Bottleneck detection monitors, detects, and alerts user of restrictions in a value stream.
  - Metrics FAQs
    Metrics frequently asked questions
- Navigating value streams
  Manage a value stream's displayed data by applying filters and queries.
- DevOps query language
  Use the DevOps query language to filter the information displayed in your value stream.
- External YAML configuration
  You can create a minimal value realization of different DevOps tools into HCL DevOps Velocity (Velocity) quickly using external YAML configuration file.
- Pipelines
  Pipelines provide a streamlined method to manage the applications in your development lifecycle. With pipelines, you can auto-generate deployment plans and deploy applications versions to all environments.
- Solution versions
Developing Data Insights
The Insights feature provides DevOps metrics for your project data.
Releasing Software
A release is a repeatable plan that is used to drive deployments.
Extending Product Functions
Learn how to extend the function of HCL DevOps Velocity (Velocity)
How to
The topics in this section describe how to work with HCL DevOps Velocity (Velocity) features. Tutorials and workbooks are available for users of all experience levels.
Troubleshooting
Before you contacting support, gather background information and perform tasks that will assist in solving the problem. It helps to be as specific as possible and include all relevant information.
Notices for DevOps Velocity
This document provides information about copyright, trademarks, terms and conditions for the product documentation.
DevOps Velocity GDPR statement
General Data Protection Regulation (GDPR) has been adopted by the European Union (EU) and applies from May 25, 2018.
Glossary

Customizing metric definitions for Lead Time, Cycle Time, and Dev Cycle Time

You can now select multiple start and end stage for a metric, enabling a more accurate representation of the actual workflow across teams. Because the definition of work start and end times can vary depending on the tools, processes, and delivery practices used. This provides teams and stakeholders with clearer insights into the actual flow of work, supporting better decision-making, increased transparency, and continuous improvement adaptability for the team.

The metric is calculated as the median duration between all selected start and end stages. This ensures the measurement reflects the entire workflow and accurately captures the time spent across all phases.

To customize the metric definitions for calculating the Lead Time, Cycle Time, and Dev Cycle Time metrics, perform the following steps:

Hover over the metric, click and then select Edit.
The Edit Metric dialog is displayed.
Select one or more stages from the drop-down list of Start Stage and End Stage for the metric.
Click Update.
The updated metric definitions are saved in the vsm.json file, and the static metric graphs are updated for Lead Time, Cycle Time, and Dev Cycle Time in Insights dashboard.

Example: Calculation of Cycle time when multiple stages selected for end stage

The following setup describes how the Cycle time is calculated when multiple End stages are selected. In this example, Start stage is selected as Active, whereas Production and Closed are selected as End stage.

Work item	Start Stage	Start date	End Stage	End date	Duration
A	Active	June 1	Closed	June 7	6 days
B	Active	June 3	Production	June 10	7 days
C	Active	June 3	Production	June 7	4 days
D	Active	June 2	Production	June 5	3 days
E	Active	June 7	Production	June 12	5 days
F	Active	June 5	Production	June 10	5 days

Cycle time calculation: The distribution of the cycle times of all work items completed during the last 30 days. The calculated durations from the above table are sorted in ascending order. For example, if the duration values are [6, 7, 4, 3, 5, 5], they are reordered as [3, 4, 5, 5, 6, 7]. The Median Cycle time over this period is 5 days, with 75 percent of items reaching completion within approximately 6.25 days.