Investigate using Deployment Frequency VSA instead of a Sisense
The GitLab-org Value Stream dashboard could be a better way to track deployments compared to our existing MTTP chart. Benefits include:
- Better discovery of the metrics for people outside of Delivery
- A dogfooding opportunity for us to use and feedback on GitLab features
- Displays the deployment metrics alongside other DORA metric to create a full picture
- Removes a Sisense chart
This issue tracks a comparison of Deployment Frequency VSA against MTTP.
Deployment Frequency VSA vs. SiSense deployment report
Item | Existing SiSense report | Deployment Frequency VSA |
---|---|---|
Chart perspective | Previous 12 months | Previous 6 months (last 180 days in detail) |
Average displayed? | No | Yes |
Metric format | Number per month | Number per day |
Numbers being measured comparable? | 32 for month of July, 64 for month of June | Avg 108 per day for June |
Summary
The most significant difference is the actual numbers being tracked. Less than 100 per month on the SiSense report, compared to 108 per day for June on the VSA. This is related to how we have environments set up but would need some investigation to allow us to switch over without losing the value of our measurements. Alternatively, we could officially switch over at the beginning of the year so we have a consistent metric to track progress.
The format of the Deployment Frequency VSA is comparable and in some cases better than the existing SiSense report. We would gain an "Average" measure if we switched over but would lose a bit of perspective from on;y being able to closely see the past 180 days compared to 12 months in SiSense.
Next steps:
- Understand why the metrics being tracked are differing. Decide if we can correct.