Advanced Cycle Analytics
Description
In its current form cycle analytics is a nice MVP for the concept of visualising an improving your cycle time or time to value. But it's not nearly as good as it can be.
Cycle analytics should help you improve your time to value actively and show you progress.
Proposal
This is issue is to be preceded by fixing the data in cycle analytics, so that it works across almost all projects.
- record history and show this (past performance, % improved, graphs)
- Show how much you've improved for each step over past period
- Graph on top showing overall and step-by-step speed over time
- To help you improve: comparison with other projects in your instance?
Initially, let's make cycle analytics more useful at GitLab to help us monitor and improve our process:
- reduce duration of CI tests
- current median test time is 90 minutes for GitLab CE, let's visualize and track improvements #3718
- reduce merge request age and size
- merge request age is highly variable across teams and type of work. In a large project with many teams, it is therefore hard to gain a meaningful understanding of merge request age and size at team level where process changes can more easily be made and evaluated. #3759 (closed) #3760
Links / references
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml
Edited by Job van der Voort