3 ms·
For more detail about the numbers see https://gitlab.com/help/user/project/cycle_analytics#how-the-data-is-measured https://gitlab.com/help/user/project/cycle_a
by sytse 10y ago
For more detail about the numbers see https://gitlab.com/help/user/project/cycle_analytics#how-the-data-is-measured https://gitlab.com/help/user/project/cycle_analytics#how-the...
Do you mean that number are to coarse to indicate a specific problem?
Of course there is the problem of gaming the numbers. But we do think that compared to many other ways of measuring productivity (for example the number of issues solved) this is relatively robust against manipulation. Getting something out sooner is better most of the time.
But thanks for the thoughts and I hope you try it out soon.
- jacques_chester 10y ago> relatively robust against manipulation My own view is that robustness to manipulation can't come from metric design, it can only come from culture. If metrics are tied to reward or punishment, then no matter how clever they are, they will be gamed.
- sytse 10y agoI agree that everything will be gamed and that culture is the best protection. I do think that some metrics are easier to manipulate (cyclomatic complexity comes to mind) and some metrics don't correspond with effectiveness (lines of code written).