Engineering team KPIs

[MeltyBot]

Migrated from GitLab: https://gitlab.com/meltano/squared/-/issues/68

Originally created by @aaronsteers on 2022-03-01 03:25:41

---

I'd like to create the following metrics within the squared project for the Engineering team:

• # MRs Merged, with these variants/dimensions:
  • Roadmap items vs non-roadmap items
  • Bugs / docs
  • Exclude non-product
  • Filtered for specific projects
  • By team member, team rollup
  • From community contributions (author not in team member list)
  • By week (iteration), by month
  • Lines of code
• # Story Points Completed (weight in gitlab)
  • Roadmap items vs non-roadmap items
  • Special labels: Bugs, Docs, etc.
  • Exclude "non-product" labels
  • Filtered for specific projects
  • Filtered per team member, and rolled up for the Engineering team
  • By week (iteration), by month
  • Derived metrics:
  • Lines of code per point (lines / weight)
  • Lines of code per elapsed business day (lines / elapsed biz days)
• Avg MR Age
  • Avg Age per Story Point

To start off, we can get this just from tap-gitlab, but we should also eventually pull in metrics from tap-github and the MeltanoLabs project.

After looking at https://gitlab.com/meltano/squared/-/blob/master/data/meltano.yml, it looks like the data should be there for at least most of these.

@tayloramurphy, @pnadolny13 - Obviously this will be an incremental effort but I'd like to start this effort ASAP as soon as !67 is resolved. The current tap-gitlab config gets projects, issues, and merge_requests - which should be sufficient for the first iteration of these metrics.

I expect the first iteration I'll likely create myself (maybe on hack day?) and then I'll be able to say better if Data Team support is needed to continue progressing towards sufficient metric visibility. (As of now, we're pretty blind to these metrics and it makes proper dev pipeline management difficult.)

Cc @pandemicsyn

[MeltyBot]

View 3 previous comments from the original issue on GitLab