MR Rate Accounting
Description
Revisit MR rate accounting.
At the Development Department level,
- do we pull all part of product issues?
- or only those authored by team members in Development?
- or only those with a group label?
- or some alternative method?
Scope, Context
MR Rate is a measure of productivity and efficiency. The numerator is a collection of merge requests to a set of projects. The denominator is a collection of people. Both are tracked over time (usually monthly).
We have a separate MR rate per department (in the Department PI pages). Currently, the MR rate (previously termed "Narrow" MR rate) pulls MRs authored by team members in a specific group. We determine which group a team member belongs to using legacy.employee_directory_analysis. Per the handbook, managers are responsible for updating the job title speciality field for any/all specialty changes. An alternative way of calculating MR rate is looking at the labels applied on an MR. In other words, instead of looking at who authored the MR, we can look at labels to determine what group this MR belongs to. If there needs to be two types of MR rate, we should label them differently or make a clear note in the K/PI definition.
Implementation Details
Update