Commit 4b23bb48 authored by Dan Jensen's avatar Dan Jensen Committed by Mike Jang

Improve Value Stream Analytics documentation

This clarifies that Value Stream Analytics exists at the project and
group levels, but the group level feature is EE-only. This also
clarifies that the 7 stages referenced are the default, and can be
customized at the group level.
parent 455cca72
...@@ -12,26 +12,26 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -12,26 +12,26 @@ info: To determine the technical writer assigned to the Stage/Group associated w
Value Stream Analytics measures the time spent to go from an Value Stream Analytics measures the time spent to go from an
[idea to production](https://about.gitlab.com/blog/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#from-idea-to-production-with-gitlab) [idea to production](https://about.gitlab.com/blog/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#from-idea-to-production-with-gitlab)
(also known as cycle time) for each of your projects. Value Stream Analytics displays the median time (also known as cycle time) for each of your projects or groups. Value Stream Analytics displays the median time
spent in each stage defined in the process. spent in each stage defined in the process.
For information on how to contribute to the development of Value Stream Analytics, see our [contributor documentation](../../development/value_stream_analytics.md).
Value Stream Analytics is useful in order to quickly determine the velocity of a given Value Stream Analytics is useful in order to quickly determine the velocity of a given
project. It points to bottlenecks in the development process, enabling management project. It points to bottlenecks in the development process, enabling management
to uncover, triage, and identify the root cause of slowdowns in the software development life cycle. to uncover, triage, and identify the root cause of slowdowns in the software development life cycle.
Value Stream Analytics is tightly coupled with the [GitLab flow](../../topics/gitlab_flow.md) and For information on how to contribute to the development of Value Stream Analytics, see our [contributor documentation](../../development/value_stream_analytics.md).
calculates a separate median for each stage.
## Project Level Value Stream Analytics **CORE**
Project Level Value Stream Analytics is available via **Project > Analytics > Value Stream**.
## Overview ## Group Level Value Stream Analytics **PREMIUM**
Value Stream Analytics is available: From GitLab 12.9, group level Value Stream Analytics is available via **Group > Analytics > Value Stream**.
- From GitLab 12.9, at the group level via **Group > Analytics > Value Stream**. **(PREMIUM)** ## Default stages
- At the project level via **Project > Analytics > Value Stream**.
There are seven stages that are tracked as part of the Value Stream Analytics calculations. The stages tracked by Value Stream Analytics by default represent the [GitLab flow](../../topics/gitlab_flow.md). These stages can be customized in Group Level Value Stream Analytics.
- **Issue** (Tracker) - **Issue** (Tracker)
- Time to schedule an issue (by milestone or by adding it to an issue board) - Time to schedule an issue (by milestone or by adding it to an issue board)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment