Commit dd8da86a authored by Kenny Johnston's avatar Kenny Johnston

remove stage

parent 5e75b29c
Pipeline #43300609 passed with stages
in 13 minutes and 5 seconds
......@@ -103,9 +103,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. In the case where a Stage is too large to be organized into one team, that stage is broken down into Groups. An example of this is Serverless, one of two groups within the "Configure" stage. 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