SPACE: Satisfaction, Performance, Activity, Collaboration, and Efficiency
Satisfaction #
| Name | Health | Status |
|---|---|---|
| Quarterly Engineering satisfaction survey NPS score | Okay | |
| Team member retention | Okay |
Performance #
| Name | Health | Status |
|---|---|---|
| Escape Rate | Okay | |
| Flaky Tests | Okay | |
| S1 Bugs | Okay |
Activity #
| Name | Health | Status |
|---|---|---|
| MR Rate | Okay |
Collaboration #
| Name | Health | Status |
|---|---|---|
| Time from hire to first contribution | Okay | |
| MR Group Collaboration Count | Okay |
Efficiency #
| Name | Health | Status |
|---|---|---|
| Review Time to Merge | Okay | |
| Open MR Age (OMA) | Attention | |
| Open Bug Age (OBA) | Okay | |
| Weekly Merge Frequency | Okay |
Metrics for satisfaction #
Quarterly Engineering satisfaction survey NPS score #
Score taken from the Quarterly Engineering satisfaction survey
Target: TBD Health:Okay
Team member retention #
We need to be able to retain talented team members. Retention measures our ability to keep them sticking around at GitLab. Team Member Retention = (1-(Number of Team Members leaving GitLab/Average of the 12 month Total Team Member Headcount)) x 100. GitLab measures team member retention over a rolling 12 month period. This is an internal metric.
Target: at or above 84% Health:Okay
URL(s):
Metrics for performance #
Escape Rate #
This shows the rate that bugs are created. It is the ratio of opened bugs to the number of MRs merged. As an example, an escape rate of 10% indicates that, on average, for every 10 MRs merged we will see 1 bug opened. Looking at the escape rate helps us understand the quality of the MRs we are merging.
Target: Currently no target is set for this metric. We need to establish a baseline and consider the right balance between velocity and quality. Health:Okay
Chart
URL(s):
Flaky Tests #
TBD
Target: TBD Health:Okay
Chart
S1 Bugs #
Number of open S1 bugs over time
Target: TBD Health:Okay
Chart
Metrics for activity #
MR Rate #
This is the ratio of product MRs to the number of team members in the group. It’s important because it shows us how productivity of our projects have changed over time.
Target: Varies by group Health:Okay
Chart
Metrics for collaboration #
Time from hire to first contribution #
This measures the median time it takes for team members to merge their first contribution to the product.
Target: TBD Health:Okay
Chart
MR Group Collaboration Count #
This measures the number of groups involved in an MR.
Target: TBD Health:Okay
Chart
Metrics for efficiency #
Review Time to Merge #
Review Time to Merge (RTTM) tells us on average how long it takes from submitting code for review to being merged.
Target: At or below 3 Health:Okay
Chart
Open MR Age (OMA) #
We want to be more intuitive with calculating how long it takes an MR to merge or close. Open MR Age (OMA) measures the median time of all open MRs as of a specific date. In other words, on any given day, we calculate the number of open MRs and median time in open state for those MRs at that point in time.
Target: At or below 30 Health:Attention
Chart
Open Bug Age (OBA) #
Open Bug Age (OBA) measures the total number of days that all bugs are open within a month divided by the number of bugs within that month.
Target: TBD Health:Okay
Chart
Weekly Merge Frequency #
This is the weekly number of MRs merged. Hovering over the data points will give the daily frequencies.
Target: TBD Health:Okay
Chart
33625584)
