Commit 68673dfb authored by Mark Pundsack's avatar Mark Pundsack

Add stage groups

parent 7730bd05
Pipeline #40080340 failed with stages
in 62 minutes and 23 seconds
......@@ -854,7 +854,7 @@ error_tracking:
complete: 2019-12-22
lovable:
production_monitoring:
synthetic_monitoring:
name: "Synthetic Monitoring"
stage: monitor
alt_link: https://gitlab.com/groups/gitlab-org/-/epics/168
......@@ -1013,3 +1013,33 @@ runtime_application_security:
available: 2019-05-22
complete: 2019-05-22
lovable:
# Defend
ids_ips:
name: "Intrusion detection / prevention"
stage: defend
description:
roi: false
available: 2019-12-22
storage_security:
name: "Storage security"
stage: defend
description:
roi: false
available: 2019-12-22
siem:
name: "Security information and event management"
stage: defend
description:
roi: false
available: 2019-12-22
data_loss_prevention:
name: "Data loss prevention"
stage: defend
description:
roi: false
available: 2019-12-22
This diff is collapsed.
......@@ -105,8 +105,7 @@ If you would like to be a mentor in a certain area, please add the information t
## Stage 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. Similar to a crew, 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.
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.
## GitLab.com isn't a role
......
......@@ -41,9 +41,9 @@ product categories defined on this page:
The categories form a hierarchy:
1. **Departments**: Dev and Ops. Dev and Ops map to departments in our [organization structure](https://about.gitlab.com/company/team/structure/#table). At GitLab the Dev and Ops split is different then 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.
The stages that are the difference between the value stages and the team stages are part of the Dev department.
1. **Stages**: Stages start with the 7 **loop stages**, then add Manage and Secure to give the 9 (DevOps) **value stages**, and then add Distribution, Geo, Gitaly, Growth & Gitter to get the 13 **team stages**. Values stages are what we all talk about in our marketing. Each of the team stages has a dedicated engineering team, product manager. Within shared functions, like quality and product management, individuals are paired to one or more stages so that there are stable counterparts.
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, Secure,and Defend to get the 10 (DevOps) **value stages**, and then add (Non-DevOps) **team stages** such as Distribution, Geo, Growth, and Gitaly & Gitter. 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.
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).
......@@ -53,7 +53,7 @@ in the following hierarchy:
Marketing product page > docs page > epic > label query > issue
E.g if there's no marketing page, link to the docs. If there's no docs, link to
the Epic. Etc.
the Epic. etc.
[Solutions](#solutions) can consist of multiple categories as defined on this
page, but there are also other ones, for example industry verticals. Solutions typically represent a customer challenge, how GitLab capabilities come together to meet that challenge, and business benefits of using our solution.
......@@ -100,19 +100,7 @@ to be approved by:
**Key** \| PM: Product Manager \| PMM: Product Marketing Manager \| EM: Engineering Manager \| FEM: Frontend Engineering Manager \| CM: Content Marketing \| TW: Technical Writer
<%= partial("includes/product/categories", locals: { dev_ops: 'dev'}) %>
4. **Distribution** \| PM: [Joshua Lambert] \| PMM: [William Chia] \| EM: [Marin Jankovski] \| FEM: [Clement Ho] \| TW: [Axil]
- [Omnibus](https://docs.gitlab.com/omnibus/)
- [Cloud Native Installation](https://docs.gitlab.com/ee/install/kubernetes/) <kbd>New in 2018</kbd>
5. **Gitaly and Gitter** \| PM: [James Ramsay] \| PMM: [John Jeremiah] \| EM: [Tommy (interim)] \| FEM: [Tim Z (Interim)] \| TW: [Axil]
6. **Geo** \| PM: [Andreas Kämmerle] \| PMM: [John Jeremiah] \| EM: [Rachel Nienaber] \| FEM: [André Luís (Interim)] \| TW: [Evan Read]
7. [**Growth**](growth-team/) \| PM: [Tamas Szuromi] \| EM: [Liam McAndrew] \| FEM: [Dennis Tang (Interim)]
8. **Sync** \| Currently part of Manage
- [License Sync](https://gitlab.com/groups/gitlab-org/-/epics/456)
- license.gitlab.com
- version.gitlab.com
- customers.gitlab.com (Subscription portal)
- Usage data
<%= partial("includes/product/categories", locals: { dept: 'dev'}) %>
## Ops department
......@@ -128,7 +116,49 @@ to be approved by:
**Key** \| PM: Product Manager \| PMM: Product Marketing Manager \| EM: Engineering Manager \| FEM: Frontend Engineering Manager \| CM: Content Marketing \| TW: Technical Writer
<%= partial "includes/product/categories", locals: { dev_ops: 'ops'} %>
<%= partial "includes/product/categories", locals: { dept: 'ops'} %>
## Sec department
### Sec leadership
- Product: [Kenny Johnston]
- Backend: [Dalia Havens]
- Product Marketing: [Ashish Kuthiala]
- Content Marketing: [Erica Lindberg]
- Technical Writing: [Mike Lewis]
### Sec stages
**Key** \| PM: Product Manager \| PMM: Product Marketing Manager \| EM: Engineering Manager \| FEM: Frontend Engineering Manager \| CM: Content Marketing \| TW: Technical Writer
<%= partial "includes/product/categories", locals: { dept: 'sec'} %>
## Non-DevOps department
- Product: [Job van der Voort]
- Backend: [Tommy Morgan]
- Product Marketing: [Ashish Kuthiala]
- Content Marketing: [Erica Lindberg]
- Technical Writing: [Mike Lewis]
### Non-DevOps stages
**Key** \| PM: Product Manager \| PMM: Product Marketing Manager \| EM: Engineering Manager \| FEM: Frontend Engineering Manager \| CM: Content Marketing \| TW: Technical Writer
<%= partial "includes/product/categories", locals: { dept: 'ndo'} %>
4. **Distribution** \| PM: [Joshua Lambert] \| PMM: [William Chia] \| EM: [Marin Jankovski] \| FEM: [Clement Ho] \| TW: [Axil]
- [Omnibus](https://docs.gitlab.com/omnibus/)
- [Cloud Native Installation](https://docs.gitlab.com/ee/install/kubernetes/) <kbd>New in 2018</kbd>
5. **Gitaly and Gitter** \| PM: [James Ramsay] \| PMM: [John Jeremiah] \| EM: [Tommy (interim)] \| FEM: [Tim Z (Interim)] \| TW: [Axil]
6. **Geo** \| PM: [Andreas Kämmerle] \| PMM: [John Jeremiah] \| EM: [Rachel Nienaber] \| FEM: [André Luís (Interim)] \| TW: [Evan Read]
7. [**Growth**](growth-team/) \| PM: [Tamas Szuromi] \| EM: [Liam McAndrew] \| FEM: [Dennis Tang (Interim)]
8. **Sync** \| Currently part of Manage
- [License Sync](https://gitlab.com/groups/gitlab-org/-/epics/456)
- license.gitlab.com
- version.gitlab.com
- customers.gitlab.com (Subscription portal)
- Usage data
## Maturity
......@@ -180,6 +210,10 @@ Maybe we should make our features easier to search to replace the section below.
- [gitlab-shell](https://gitlab.com/gitlab-org/gitlab-shell)
- [gitlab-workhorse](https://gitlab.com/gitlab-org/gitlab-workhorse)
### Other functionality in Verify
- Runner
[Mark Pundsack]: /company/team/#MarkPundsack
[Job van der Voort]: /company/team/#Jobvo
[Ashish Kuthiala]: /company/team/#kuthiala
......
<% data.stages.stages.each do |stageKey, stage| %>
<% next unless (stage.dev_ops == dev_ops) %>
<% next unless (stage.dept == dept) %>
<%= "1. **#{stage.display_name}<a name=\"#{stageKey}\"></a>** \\| PM: [#{stage.pm}] \\| PMM: [#{stage.pmm}] \\| EM: [#{stage.engineering_manager}] \| FEM: [#{stage.frontend_engineering_manager}] \\| CM: [#{stage.cm}] \| TW: [#{stage.tech_writer}]" %>
<% data.categories.each do |categoryKey, category| %>
<% next unless (category.stage == stageKey) %>
......
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