In some parts of the industry number of CRs and revisions-per-cr is tracked as a performance metric.
Many people learn to game this to make their "numbers" appear good i.e. high number of CRs and low revisions per CR.
In some parts of the industry number of CRs and revisions-per-cr is tracked as a performance metric.
Many people learn to game this to make their "numbers" appear good i.e. high number of CRs and low revisions per CR.
Easy and fun to put metrics around random things. I'll start to squirm if you ask me to draw the connection between these metrics and NPV.
The interesting phenomenon is the discovery of gamification of such metrics.
I do see the value in breaking down larger chunks of work into logically smaller units of work and then produce multiple pull requests where needed.
But some people are really clever and influential and manage to game these numbers into "apparent success".
It just becomes a huge cycle which is easier for everyone involved than doing actual work that benefits your customers.