Introducing GitLab Value Stream Analytics

Value Stream Analytics measures the time it takes to go from planning to monitoring for each project in your portfolio.

Documentation

What is GitLab Value Stream Analytics?

Real data on your project

Estimates of a software development process are often incorrect. Stop estimating. Value Stream Analytics lets you know how long it takes your team to complete each stage in their workflow, from planning to monitoring.

Built for managers and teams

GitLab Value Stream Analytics allow for one shared view of the team's velocity. With insights into how long it takes the team to move from planning to monitoring, you can pinpoint areas for improvement.

No setup required

Value Stream Analytics is pre-configured and ready to track your workflow. It follows the GitLab Flow and records the median time it takes the team to complete each stage.

Value Stream Analytics Overview

Watch our webcast!

Learn more about Value Stream Analytics and our overall Analytics direction
Watch on YouTube

Understanding GitLab Value Stream Analytics

Value Stream Analytics is available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition.

Navigate to Project > Analytics > Value Stream Analytics within a project to access the dashboard.

[ stage 01 ]

Issue

How long until you start working on an issue?

This stage measures the time between creating an issue and taking action to solve it, by either assigning it to a milestone or moving it into a list on your Issue Board, whichever comes first.

[ stage 02 ]

Plan

How long until your first commit?

This stage measures the time between the action you took for the previous stage, and pushing the first commit to the repository.

GitLab tracks this using the issue closing pattern like closes #xxx, where xxx is the number of the issue related to this commit.

[ stage 03 ]

Code

How long until you create a merge request (MR)?

This stage measures the time between pushing a first commit (previous stage) and creating a merge request related to that commit.

GitLab tracks this using the issue closing pattern like closes #xxx in the MR description, where xxx is the number of the issue related to this merge request.

[ stage 04 ]

Test

How much time does it take GitLab CI/CD to test your code?

This stage measures the time to run the entire pipeline for that project.

It's related to the time GitLab CI/CD takes to run every job for the commits pushed to that MR defined in the previous stage.

[ stage 05 ]

Review

How much time do you spend on code review?

This stage measures the time taken to review the MR, from the moment it's created until the moment it's merged.

[ stage 06 ]

Staging

We're ready to go now! What's the length of time between merging and deploying to production?

This stage measures the time spent in staging, from merging the MR until the app is deployed to production.

It's tracked by the environment set to production in your GitLab CI/CD configuration.

[ stage 07 ]

Total

Total lifecycle time: how fast is my team?

This is the measure of the time taken to run entire process, from creating an issue to deploying the code to production.

In fact, this is the time your team takes to go from planning to monitoring!

Read through the Value Stream Analytics documentation to learn more.

30天免费试用极狐GitLab专业版

极狐GitLab不仅是源代码管理或CI/CD工具,它是一个覆盖完整软件开发生命周期和DevOps的开放式一体化平台。

免费试用
Git为Software Freedom Conservancy的注册商标,GitLab为GitLab B.V.的注册商标,我们已获授权使用“极狐GitLab”。