Estimates are often incorrect. Stop estimating. Cycle Analytics lets you know how long it takes your team to complete each stage in their workflow from planning to monitoring.
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.
Cycle 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.
Cycle Analytics is available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition.
Navigate to your Project's Pipelines > Cycle Analytics to access the dashboard.
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.
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.
How long until you create a merge request (MR)?
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.
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.
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.
Total lifecycle time: how fast is my team?