Commit e8424528 authored by Sid Sijbrandij's avatar Sid Sijbrandij

Groups

parent 86abac94
Pipeline #43304787 passed with stages
in 15 minutes and 33 seconds
......@@ -39,8 +39,8 @@ The categories form a hierarchy:
1. **Departments**: Dev, Ops, Sec, and Non DevOps (NDO). Maps to departments in our [organization structure](https://about.gitlab.com/company/team/structure/#table). At GitLab the Dev and Ops split is differently than the infinity loop suggests because our CI/CD functionality is one codebase, so from verify on we consider it Ops so that the codebase falls under one department.
1. **Stages**: Stages start with the 7 **loop stages**, then add Manage and Secure to get the 9 (DevOps) **value stages**, and then add the (Enablement) **team stage**. Values stages are what we all talk about in our marketing.
1. **Group**: Many stages have more than one [stage group](/company/team/structure/#stage-groups). Each of the stage groups has a dedicated backend engineering team. Within shared functions, like quality and product management, individuals are paired to one or more stages so that there are stable counterparts.
1. **Categories**: High-level capabilities that may be a standalone product at another company. e.g. Portfolio Management. There are a maximum of 8 high-level capabilities per stage to ensure we can display this on our website and pitch deck. There may need to be fewer categories, or shorter category names, if the aggregate number of lines when rendered would exceed 13 lines, when accounting for category names to word-wrap, which occurs at approximately 15 characters.
1. **Group**: A stage has one of more [groups](/company/team/structure/#groups). Each of the groups has a dedicated backend engineering team. Within shared functions, like quality and product management, individuals are paired to one or more stages so that there are stable counterparts.
1. **Categories**: A group as one or more categories. High-level capabilities that may be a standalone product at another company. e.g. Portfolio Management. There are a maximum of 8 high-level capabilities per stage to ensure we can display this on our website and pitch deck. There may need to be fewer categories, or shorter category names, if the aggregate number of lines when rendered would exceed 13 lines, when accounting for category names to word-wrap, which occurs at approximately 15 characters.
1. **Features**: Small, discrete functionalities. e.g. Issue weights. Some common features are listed within parentheses to facilitate finding responsible PMs by keyword. Features are maintained in [features.yml](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/features.yml).
Every category listed on this page must have a link, determined by what exists
......@@ -67,6 +67,8 @@ usability in the following ways:
1. Harder to define what level something should be in.
1. Harder to keep this page up to date.
A group might have the same scope as a stage or contain only a single category.
## Changes
The impact of changes to stages and groups is felt [across the company](/company/team/structure/#stage-groups).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment