# of Change Requests per promotion metric
Does anyone have to deal with a metric that looks at the number of Change Requests used to document a promotion?
If we don't have at least 5, then the entire team is 'dinged' on our reviews.
This not only includes software defects (coding bugs not found in testing), but it also includes year-end maintenance, software changes dictated by company policy / procedure change, federal / state changes, the user with power that screams loud enough to get their small enhancement promoted asap...
The Leads in the department are trying to get this changed, but we have to come up with metrics that would help prevent continual 'small' promotions from occuring.
Any suggestions?