GitLab Quality Score
Problem Statement
Executives of large enterprises find that despite the many metrics being tracked in engineering for "code quality" they cannot quickly tell if quality is getting better or worse with any leading indicator.
Reach
We think this impacts a fairly small amount of customers who are large enterprises. => 1.5 (~5% - ~25%)
Impact
We think this would have a Medium impact to users who made use of the score / metrics rollup. => 1.0
Confidence
We have a medium confidence that this is a problem for customers based on existing issues requesting dashboards of data. => 80%
Effort
This solution would take a PM, Designer and 2 engineers ~ 6 weeks of effort. => (1.5 months x 4 people) = 6.
Beginnings of a proposal
- This project has examples of many maintainability issues, thanks @iamricecake.
- Code Climate uses this method for maintainability scores.
- We could utilize total remediation points as well like code climate.
- some other possible changes after having this score in place
- We can grade the changes in the MR
- We can warn them if they are changing a file with a low maintainability rating (and maybe combine it with test coverage too)
- As a quick, simple change, maybe we can highlight issues with “major” severity.
RICE score
(1.5 * 80% * 1) / 6 = .2