Changes and re-organization of KPIs for Infrastructure-Quality Dept.

Why is this change being made?

Initial changes to Infrastructure-Quality KPIs and PIs in handbook:

• Added DRIs to KPIs
• Moved S1 Open Bug Age, S2 Open Bug Age to PIs
• Moved S1 Open Customer Bug Age, S2 Open Customer Bug Age to KPIs
• Removed Quality MR Rate and Infrastructure MR Rate PIs
• Removed Quality Budget Plan vs Actuals PI
• Changed paths for KPIs to /handbook/engineering/infrastructure-quality/performance-indicators/

Not done in this MR:

• Merging of metrics from Infrastructure and Quality into unified department-wide metric (e.g., Handbook MR rate, Promotion rate, Discretionary Bonus rate)
  • This is because the changes have not happened in Sisense yet.
  • There is also open discussion on whether these should even be PIs, if they are not actively used.
• Change in title and/or description for Time to First Failure and MR pipeline duration to reflect change of measuring average or median to meaasuring 80th percentile ("p80")
  • That discussion hasn't been resolved, and no changes have been made yet to Sisense charts for these metrics.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---