New accounting method per customer facing work team member per month

This is the latest ask from Sid in the Engineering/PM meeting on the next iteration of the previous MR per Author per Month.

This issue is to prep for the metrics and all the switching cost associate with it. Likely that this will replace the legacy metric when this is ready.

Requirements

The metric should focus on the MRs that are part of the product that we release to customers.

• Include: Development, quality, UX, PM (excluding VP and directors)
• Exclude: Support, Security, Infra (seen as external contributors in this case.
• Include community contributions MRs, no need to capture the Comunity Contribution authors in. Getting that in is still work on our side
• Count toward MRs, but not towards the headcount
• Remove unique authors criteria, we count on who we are paying, even if a person is on vacation or sick we still count as the numerator
• Measure multiple repos like today https://docs.gitlab.com/ee/development/architecture.html#component-legend ;
  • All microservices should count towards work (except external ones like Minio and Mattermost). => Emilie currently 128 projects https://gitlab.com/gitlab-data/analytics/blob/master/transform/snowflake-dbt/data/engineering_productivity_metrics_projects_to_include.csv
  • Do an audit of existing projects
    • Make sure to include all the microservices https://docs.gitlab.com/ee/development/architecture.html#component-legend
    • Do we need to include customer-facing work in GitLab-Triage, GitLab-QA and etc.

Work here is to be done in periscope direcly.

We will plan out other issues we need to file and track it here.

Please review and ask questions @gl-quality/eng-prod.

Implementation

• Sign off on the list of projects: https://docs.google.com/spreadsheets/d/1i3R0OjT_j_OMg-uvJvKW2ENZ9MjaIjuqycgpYfYbFvs/edit#gid=427097875
• Chart added to KPIs dashboard: https://app.periscopedata.com/app/gitlab/516343/Quality-KPIs?widget=6722533&udv=828757

  • Include: Development, quality, UX, PM

  • Exclude: Support, Security, Infra (seen as external contributors in this case.

• Implemented.

  • Include community contributions MRs, no need to capture the Community Contribution authors in. Getting that in is still work on our side

    • Count toward MRs, but not towards the headcount

    • Remove unique authors criteria, we count on who we are paying, even if a person is on vacation or sick we still count as the numerator

• Implemented.

  • Measure multiple repos like today https://docs.gitlab.com/ee/development/architecture.html#component-legend ;

  • All microservices should count towards work (except external ones like Minio and Mattermost). => Emilie currently 128 projects https://gitlab.com/gitlab-data/analytics/blob/master/transform/snowflake-dbt/data/engineering_productivity_metrics_projects_to_include.csv

  • Do an audit of existing projects

    • Make sure to include all the microservices https://docs.gitlab.com/ee/development/architecture.html#component-legend

    • Consider customer facing work in GitLab-Triage and GitLab-QA and etc.

• Factorize the projects list in a macro and expose it as a is_part_of_product column in the gitlab_dotcom_issues_xf and gitlab_dotcom_merge_requests_xf models: https://gitlab.com/gitlab-data/analytics/merge_requests/1739