Define success criteria for New Group Namespace with at least two users added
Update: changes have been made to the KPI https://about.gitlab.com/handbook/product/performance-indicators/#new-group-namespace-with-at-least-two-users-added to clarify. Use cases below are no longer relevant.
Aim
Clarity on success criteria for ~"group::expansion" KPI
The current wording mentions a few scenarios where namespaces are not eligible. The scenarios below expand on the ineligible namespaces, and then attempt to identify scenarios that are eligible.
Eligible namespaces exclude personal namespaces, sub-group namespaces, and group namespaces that belong to a user that is on a paid plan.
Scenario 1 - personal namespace
- I add 2 users to my personal namespace on GitLab.com within 90 days of creation
Scenario 2a - sub-group namespaces
- I do not belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace (namespace-a)
- I create a sub-group (namespace-a/namespace-b)
- I add two new users to this new sub-group
Scenario 2b - sub-group namespaces
- I belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace (namespace-a)
- I create a sub-group (namespace-a/namespace-b)
- I add two new users to this new sub-group
Scenario 3a - namespace owner is on a paid plan for another namespace on GitLab.com
- I belong to namespace-a, which is on a paid plan on GitLab.com
- I create a new group (top level) namespace (namespace-b)
- (any action) on namespace-b
Question: does this exclude the namespace (regardless of how many other users are added), or just that particular user?
Scenario 3b - namespace owner is on a paid plan for this namespace
- I belong to namespace-a, which is a top-level group on a paid plan on GitLab.com
- (any action) on namespace-a
Question: does this exclude the namespace (regardless of how many other users are added)?
Scenario 3c - add a namespace owner who is on a paid plan for another namespace
- I do not belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace
- I add two new users to this new group within 90 days, one (or more) of these users I add as an owner of this namespace, who is already an owner of another paid namespace on GitLab.com
Question: does this exclude the namespace (regardless of how many other users are added)?
Scenario 4a - add new GitLab.com users
- I do not belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace
- I add two new users to this new group within 90 days, neither of whom are already GitLab.com users (and as such, neither are members of a paid namespaces on GitLab.com)
Scenario 4b - add existing GitLab.com users not members of any other namespace on a plan
- I do not belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace
- I add two new users to this new group within 90 days, both of whom are already GitLab.com users, but neither are members of a paid namespaces on GitLab.com
Scenario 4c - add existing GitLab.com users already part of another plan
- I do not belong to a namespace on a paid plan on GitLab.com
- I create a new group (top level) namespace
- I add two new users - but not as owners - to this new group within 90 days, both of whom are already GitLab.com users and members of one or more paid namespaces on GitLab.com
Scenario 5 - namespaces created more than 90 days ago
- I create a new group (top level) namespace
- In the first 90 days this group has 1 new member added to it
- On day 91 the second new user is added
Related Sisense https://app.periscopedata.com/app/gitlab/761347/New-Growth-KPIs-(WIP)