Commit f5fd6886 authored by Sid Sijbrandij's avatar Sid Sijbrandij

Merge branch 'clarify-stage-groups' into 'master'

Clarify stage groups

See merge request !18100
parents 5880e60c dd8da86a
Pipeline #43304091 passed with stages
in 14 minutes and 46 seconds
......@@ -109,9 +109,9 @@ Some people think of expertise as hard skills (Ruby, International Employment La
If you would like to be a mentor in a certain area, please add the information to the team page. It is important to note whether you would like to be a mentor internally and/or externally at GitLab. Examples of how to specify in the expertise section of the team page: `Mentor - Marketing, Internal to GitLab` or `Mentor - Development (Ruby), External and Internal to GitLab`.
## Stage Groups
## Groups
Parts of our engineering organization are directly aligned with our [product categories](/handbook/product/categories/). For example we have a Product Manager, an Engineering Manager, Backend Developers, Frontend Developers, and UX Designers who are dedicated to the [stage](/handbook/product/categories/#hierarchy) named "Monitor". Collectively, these individuals form the "Monitor group". The word "Monitor" appears in their titles as a specialty, and in some cases, their team name. A DevOps stage group has no reporting lines because we [don't want a matrix organization](/handbook/leadership/#no-matrix-organization). Instead, we rely on stable counterparts to make a stage group function well.
Our engineering organization is directly aligned with our [product categories](/handbook/product/categories/) structures of Stages, Groups and Categories. Some groups are aligned to Stages, others to Groups or collections of categories. Our groups operate on the principle of [stable counterparts](/2018/10/16/an-ode-to-stable-counterparts/) from multiple functions. For example we have a Product Manager, an Engineering Manager, Backend Developers, Frontend Developers, and UX Designers who are dedicated to the [stage](/handbook/product/categories/#hierarchy) named "Monitor". Collectively, these individuals form the "Monitor group". The word "Monitor" appears in their titles as a specialty, and in some cases, their team name. A group has no reporting lines because we [don't want a matrix organization](/handbook/leadership/#no-matrix-organization). Instead, we rely on stable counterparts to make a group function well.
## GitLab.com isn't a role
......
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