Product sections, stages, groups, and categories

Maintained by:

Interfaces

We want intuitive interfaces both within the company and with the wider community. This makes it more efficient for everyone to contribute or to get a question answered. Therefore, the following interfaces are based on the product categories defined on this page:

Home page
Product page
Product Features
Pricing page
DevOps Lifecycle
DevOps Tools
Product Direction
Stage visions
Documentation
Engineering Engineering Manager/Developer/Designer titles, their expertise, and department, and team names.
Product manager responsibilities which are detailed on this page
Our pitch deck, the slides that we use to describe the company
Strategic marketing specializations

Hierarchy

The categories form a hierarchy:

Sections: Are a collection of stages. We attempt to align these logically along common workflows like Dev, Sec and Ops. Sections are maintained in data/sections.yml.
Stages: Stages start with the 7 loop stages, then add Manage, Secure, and Protect to get the 10 (DevOps) value stages, and then add the Growth and Enablement team stages. Values stages are what we all talk about in our marketing. Stages are maintained in data/stages.yml. Each stage has a corresponding devops::<stage> label under the gitlab-org group.
Group: A stage has one or more groups. Groups are maintained in data/stages.yml. Each group has a corresponding group::<group> label under the gitlab-org group.
Categories: A group has one or more categories. Categories are high-level capabilities that may be a standalone product at another company. e.g. Portfolio Management. To the extent possible we should map categories to vendor categories defined by analysts. There are a maximum of 8 high-level categories per stage to ensure we can display this on our website and pitch deck. (Categories that do not show up on marketing pages show up here in italics and do not count toward this limit.) 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. Categories are maintained in data/categories.yml. Each category has a corresponding Category:<Category> label under the gitlab-org group.
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 data/features.yml. It's recommended to associate feature labels to a category or a group with feature_labels in the data/categories.yml or data/stages.yml.

Notes:

Groups may have scope as large as all categories in a stage, or as small as a single category within a stage, but most will form part of a stage and have a few categories in them.
Stage, group, category, and feature labels are used by the automated triage operation "Stage and group labels inference from category labels".
We don't move categories based on capacity. We put the categories in the stages where they logically fit, from a customer perspective. If something is important and the right group doesn't have capacity for it, we adjust the hiring plan for that group, or do global optimizations to get there faster.
We don't have silos. If one group needs something in a category that is owned by another group, go ahead and contribute it.

Naming

Anytime one hierarchy level's scope is the same as the one above or below it, they can share the same name.

For groups that have two or more categories, but not all categories in a stage, the group name must be a unique word or a summation of the categories they cover.

If you want to refer to a group in context of their stage you can write that as "Stage:Group". This can be useful in email signatures, job titles, and other communications. E.g. "Monitor:Health" rather than "Monitor Health" or "Monitor, Health."

More Details

Every category listed on this page must have a link to a direction page. Categories may also have documentation and marketing page links. When linking to a category using the category name as the anchor text (e.g. from the chart on the homepage) you should use the URLs in the following hirearchy:

Marketing product page > docs page > direction page

E.g Link the marketing page. If there's no marketing page, link to the docs. If there's no docs, link to the direction page.

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.

Capabilities

Capabilities can refer to stages, categories, or features, but not solutions.

Layers

Adding more layers to the hierarchy would give it more fidelity but would hurt usability in the following ways:

Harder to keep the interfaces up to date.
Harder to automatically update things.
Harder to train and test people.
Harder to display more levels.
Harder to reason, falsify, and talk about it.
Harder to define what level something should be in.
Harder to keep this page up to date.

We use this hierarchy to express our organizational structure within the Product and Engineering organizations. Doing so serves the goals of:

Making our groups externally recognizable as part of the DevOps lifecycle so that stakeholders can easily understand what teams might perform certain work
Ensuring that internally we keep groups to a reasonable number of stable counterparts

As a result, it is considered an anti-pattern to how we've organized for categories to move between groups out of concern for available capacity.

When designing the hierarchy, the number of sections should be kept small and only grow as the company needs to re-organize for span-of-control reasons. i.e. each section corresponds to a Director of Engineering and a Director of Product, so it's an expensive add. For stages, the DevOps loop stages should not be changed at all, as they're determined from an external source. At some point we may change to a different established bucketing, or create our own, but that will involve a serious cross-functional conversation. While the additional value stages are our own construct, the loop and value stages combined are the primary stages we talk about in our marketing, sales, etc. and they shouldn't be changed lightly. The other stages have more flexibility as they're not currently marketed in any way, however we should still strive to keep them as minimal as possible. Proliferation of a large number of stages makes the product surface area harder to reason about and communicate if/when we decide to market that surface area. As such, they're tied 1:1 with sections so they're the minimal number of stages that fit within our organizational structure. e.g. Growth was a single group under Enablement until we decided to add a Director layer for Growth; then it was promoted to a section with specialized groups under it. The various buckets under each of the non-DevOps stages are captured as different groups. Groups are also a non-marketing construct, so we expand the number of groups as needed for organizational purposes. Each group usually corresponds to a backend engineering manager and a product manager, so it's also an expensive add and we don't create groups just for a cleaner hierarchy; it has to be justified from a span-of-control perspective or limits to what one product manager can handle.

Changes

The impact of changes to stages and groups is felt across the company.

All new category creation needs to be specifically approved via our Opportunity Canvas review process. This is to avoid scope creep and breadth at the expense of depth and user experience.

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

EVP of Product
VP of Product Management
The Director of Product relevant to the stage group(s)
The Director of Engineering relevant to the stage group(s)
CEO

The following people need to be on the merge request so they stay informed:

EVP of Engineering
VP of Development
Director of Quality Engineering
Engineering Productivity (by @ mentioning @gl-quality/eng-prod)
The Product Marketing Manager relevant to the stage group(s)

After approval and before merging, obtain final confirmation from the Engineering Manager for Quality Engineering before proceeding with changes that:

Adds a new category, group or stage
Moves an existing category to a new or existing group
Moves an existing group to a new or existing stage
Renames a group or stage
Deletes a group or stage

This is to ensure that GitLab Bot auto-labeling can be updated prior to the change, which can be disruptive if missed.

Examples

Because it helps to be specific about what is a significant change and what should trigger the above approval process, below are two non-exhaustive lists of examples that would and would not, respectively, require approval.

Changes that require the above approvers include:

Changes to a stage, group, or category name
Removal or addition of a stage, group, or category

Changes that require approval only from the relevant Product Director include:

Changing a category maturity date
Changes to section or group member lists
Changes to a category vision page

DevOps Stages

Dev section

Manage stage

Product Management: Jeremy Watson

Access group

Engineering totals: 2 Frontend, 8 Backend

Product Manager: Melissa Ushakov | Product Marketing Manager: Cormac Foster | Support: Blair Lunceford | Backend Engineering Manager: Liam McAndrew | Frontend Engineering Manager: Dennis Tang | Software Engineer in Test: Sanad Liaquat | Backend Engineering: Drew Blessing, Liam McAndrew, Alex Pooley, Imre Farkas, Serena Fang, Manoj M J, Sebastián Arcila-Valenzuela, Małgorzata Ksionek | Frontend Engineering: Dennis Tang, Peter Hegman | Product Design Manager: Mike Long | UX Researcher: Anne Lasch | Product Designer: Daniel Mora | Content Marketing: Suri Patel | Technical Writer: Mike Jang | Application Security Engineer: Ron Chan | Customer Success: Yolanda Feldstein, Adrian Waters | Internal Customers: Customer Support Department (TBD), Security Department (TBD), Infrastructure Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Manage Access Paid GMAU | Features in this Group

Authentication and Authorization Complete | Documentation • Direction Page
Subgroups Complete | Documentation • Direction Page
Users | Documentation • Direction Page

Compliance group

Engineering totals: 3 Frontend, 4 Backend

Audit Events Viable | Documentation • Direction Page
Audit Reports Minimal | Documentation • Direction Page
Compliance Management Minimal | Documentation • Direction Page

Import group

Engineering totals: 2 Frontend, 3 Backend

Importers | Documentation • Direction Page
Internationalization | Documentation • Direction Page
Templates | Documentation • Direction Page

Optimize group

Engineering totals: 3 Frontend, 4 Backend

Product Manager: Larissa Lane | Product Marketing Manager: Cormac Foster | Support: TBD | Backend Engineering Manager: Dan Jensen | Frontend Engineering Manager: Martin Wortschack (Interim) | Software Engineer in Test: TBD | Backend Engineering: Adam Hegyi, Magdalena Frankiewicz, Pavel Shutsin, Dan Jensen | Frontend Engineering: Martin Wortschack, Brandon Labuschagne, Ezekiel Kigbo | Product Design Manager: Mike Long | UX Researcher: Anne Lasch | Product Designer: Nick Post | Content Marketing: Suri Patel | Technical Writer: Mike Jang | Application Security Engineer: Ron Chan | Customer Success: Yolanda Feldstein | Internal Customers: Engineering Department (TBD), Product Department (TBD), Quality Department (TBD), Development Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Manage Optimize GMAU | Features in this Group

DevOps Reports Minimal | Documentation • Direction Page
Planning Analytics Minimal | Documentation • Direction Page
Code Analytics Minimal | Documentation • Direction Page
Value Stream Management Viable | Marketing Page • Documentation • Direction Page
Insights Viable | Documentation

Plan stage

Product Management: Jeremy Watson

Project Management group

Engineering totals: 4 Frontend, 5 Backend

Handbook | Product Manager: Gabe Weaver | Product Marketing Manager: Cormac Foster | Support: Ben Prescott | Backend Engineering Manager: Jake Lear | Frontend Engineering Manager: Donald Cook | Software Engineer in Test: Désirée Chevalier | Backend Engineering: Brett Walker, Mario de la Ossa, Heinrich Lee Yu, Alexandru Croitor, Jake Lear | Frontend Engineering: Simon Knox, Natalia Tepluhina, Scott Stern, Coung Ngo | Product Design Manager: Mike Long | UX Researcher: Anne Lasch | Product Designer: Holly Reynolds | Content Marketing: Suri Patel | Technical Writer: Marcin Sędłak-Jakubowski | Application Security Engineer: Costel Maxim | Customer Success: Christiaan Conover, Edmond Chan | Internal Customers: Engineering Department (TBD), Product Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Plan Project Management Paid GMAU | Features in this Group

Issue Tracking Viable | Documentation • Direction Page
Boards Viable | Marketing Page • Documentation • Direction Page
Time Tracking Viable | Marketing Page • Documentation • Direction Page
Jira Importer Available | Documentation • Direction Page
Projects | Documentation

Product Planning group

Engineering totals: 4 Frontend, 6 Backend

Epics Viable | Marketing Page • Documentation • Direction Page
Roadmaps Minimal | Marketing Page • Documentation • Direction Page
Design Management Minimal | Documentation • Direction Page

Certify group

Requirements Management Minimal | Documentation • Direction Page
Quality Management Minimal | Documentation • Direction Page
Service Desk Viable | Marketing Page • Documentation • Direction Page

Create stage

Product Management: James Ramsay

Source Code group

Engineering totals: 3 Frontend, 4 Backend

Source Code Management Lovable | Marketing Page • Documentation • Direction Page

Code Review group

Engineering totals: 5 Frontend, 5 Backend

Handbook | Product Manager: Kai Armstrong | Product Marketing Manager: Brian Glanz | Support: TBD | Backend Engineering Manager: Michelle Gill | Frontend Engineering Manager: André Luís | Software Engineer in Test: Tomislav Nikić | Backend Engineering: Patrick Bajao, Kerri Miller, David Sincheol Kim, Gary Holtz, Marc Shaw | Frontend Engineering: André Luís, Phil Hughes, Justin Boyson, Thomas Randolph, Tomas Vik | Product Design Manager: Marcel van Remmerden | UX Researcher: Katherine Okpara | Product Designer: Pedro Moreira da Silva | Content Marketing: Suri Patel | Technical Writer: Marcia Ramos | Application Security Engineer: [Michael Henriksen] | Customer Success: | Internal Customers: Engineering Department (TBD), Marketing Department (TBD), Product Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: [Create Code Review GMAU] | Features in this Group

Code Review Lovable | Marketing Page • Documentation • Direction Page
Editor Extension Minimal | Documentation • Direction Page

Editor group

Engineering totals: 4 Frontend, 2 Backend

Handbook | Product Manager: Eric Schurter | Product Marketing Manager: Brian Glanz | Support: John Long | Frontend Engineering Manager: Roman Kuba | Software Engineer in Test: Anastasia McDonald | Backend Engineering: Francisco Javier López, Chad Woolley | Frontend Engineering: Paul Slaughter, Denys Mishunov, Himanshu Kapoor, Enrique Alcántara | Product Design Manager: Marcel van Remmerden | UX Researcher: Katherine Okpara | Product Designer: Michael Le | Content Marketing: Suri Patel | Technical Writer: Marcia Ramos | Application Security Engineer: [Michael Henriksen] | Customer Success: Sophie Pouliquen, Simon Mansfield | Internal Customers: Marketing Department (TBD), Engineering Department (TBD), Finance Department (TBD), People Operations (TBD), Product Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Create Editor GMAU | Features in this Group

Web IDE Viable | Documentation • Direction Page
Snippets Complete | Documentation • Direction Page
Live Preview Minimal | Documentation • Direction Page
Wiki Viable | Documentation • Direction Page
Static Site Editor Viable | Documentation • Direction Page
GitLab Documentation Site | Documentation • Direction Page
Navigation & Settings | Direction Page

Gitaly group

Engineering totals: 8 Backend

Product Manager: Mark Wood | Product Marketing Manager: Brian Glanz | Support: Will Chandler | Backend Engineering Manager: Zeger-Jan van de Weg | Software Engineers in Test: Mark Lapierre, Tomislav Nikić | Backend Engineering: Christian Couder, Toon Claes, James Fargher, Pavlo Strokov, Sami Hiltunen, Paul Okstad, Patrick Steinhardt, Ævar Arnfjörð Bjarmason | Technical Writer: Evan Read | Application Security Engineer: TBD | Customer Success: Sophie Pouliquen, Simon Mansfield | Internal Customers: Quality Department (TBD), Infrastructure Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Create Gitaly GMAU | Features in this Group

Gitaly | Documentation • Direction Page

Ecosystem group

Engineering totals: 3 Frontend, 6 Backend

Slack Channel: g_ecosystem | GitLab Group: @gitlab-org/ecosystem-team | Handbook | Product Manager: Patrick Deuley | Product Marketing Manager: [] | Support: TBD | Backend Engineering Manager: Matt Nohr | Frontend Engineering Manager: Lukas Eipert | Software Engineer in Test: TBD | Backend Engineering: Ash McKenzie, Luke Duncalfe, Markus Koller, Arturo Herrero, Andy Soiron, Alex Kalderimis | Frontend Engineering: Mike Greiling, Tom Quirk, Justin Ho | Product Design Managers: Marcel van Remmerden, Taurie Davis (FE/UX Foundations) | UX Researcher: Katherine Okpara | Product Designers: Libor Vanc (Integrations), Jarek Ostrowski (FE/UX Foundations), Jeremy Elder (FE/UX Foundations) | Content Marketing: Erica Lindberg | Technical Writer: Evan Read | Application Security Engineer: [Michael Henriksen] | Customer Success: Sophie Pouliquen, Simon Mansfield | Internal Customers: Alliances Department (TBD), Customer Success (TBD), Quality Department (TBD), Infrastructure Department (TBD), Engineering Department (TBD) | Infrastructure Manager: Gerardo Lopez Fernandez | Focus: Create Ecosystem GMAU | Features in this Group

API Viable | Documentation • Direction Page
Integrations Viable | Documentation • Direction Page
GDK Viable | Documentation • Direction Page
FE/UX Foundations Viable | Documentation • Direction Page

Ops section

Verify stage

Product Management: Jackie Porter

Continuous Integration group

Engineering totals: 3 Frontend, 4 Backend

Product Manager: Thao Yeager | Product Marketing Manager: Parker Ennis | Support: Nathan Black | Backend Engineering Manager: Cheryl Li | Frontend Engineering Manager: Sam Beckham | Software Engineer in Test: Tiffany Rea | Backend Engineering: Grzegorz Bizon, Matija Čupić, Fabio Pitino, Allison Browne | Frontend Engineering: Jose Ivan Vargas, Payton Burdette, Mireya Andres | Product Design Manager: Rayana Verissimo | UX Researcher: Lorie Whitaker | Product Designer: Veethika Mishra | Content Marketing: Aricka Flowers | Technical Writer: Marcel Amirault | Application Security Engineer: Dominic Couture | Customer Success: Jamie Reid, Vladimir Dzalbo | Internal Customers: Quality Department (Joanna Shih), UX Department (TBD), Infrastructure Department (TBD), Engineering Department (TBD), AutoDevOps and Kubernetes Group (TBD) | Focus: Verify CI & Runner SMAU | Features in this Group

Continuous Integration (CI) Lovable | Marketing Page • Documentation • Direction Page
Merge Trains Viable | Documentation • Direction Page
Jenkins Importer | Direction Page

Pipeline Authoring group

Engineering totals: 3 Frontend, 2 Backend

Product Manager: Dov Hershkovitch | Product Marketing Manager: Parker Ennis | Support: Nathan Black | Backend Engineering Manager: Cheryl Li | Frontend Engineering Manager: Sam Beckham | Backend Engineering: Marius Bobin, Furkan Ayhan | Frontend Engineering: Miguel Rincon, Sarah Groff Hennigh-Palermo, Frédéric Caplette | Product Design Manager: Rayana Verissimo | UX Researcher: Lorie Whitaker | Product Designer: Nadia Sotnikova | Content Marketing: Aricka Flowers | Technical Writer: Marcel Amirault | Application Security Engineer: Dominic Couture | Customer Success: Jamie Reid, Vladimir Dzalbo | Internal Customers: Quality Department (Joanna Shih), UX Department (TBD), Infrastructure Department (TBD), Engineering Department (TBD), AutoDevOps and Kubernetes Group (TBD) | Focus: Verify CI & Runner SMAU | Features in this Group

Pipeline Authoring Lovable | Marketing Page • Documentation • Direction Page

Runner group

Engineering totals: 6 Backend

Product Manager: Darren Eastman | Product Marketing Manager: Parker Ennis | Support: Alexander Tanayno, Nourdin el Bacha | Backend Engineering Manager: Elliot Rushton | Frontend Engineering Manager: Sam Beckham | Software Engineer in Test: Zeff Morgan | Backend Engineering: Tomasz Maczukin, Steve Azzopardi, Georgi Georgiev, Pedro Pombeiro, Arran Walker, Adrien Kohlbecker | Product Design Manager: Rayana Verissimo | UX Researcher: Lorie Whitaker | Product Designer: Rayana Verissimo | Content Marketing: Aricka Flowers | Technical Writer: Suzanne Selhorn | Application Security Engineer: Dominic Couture | Customer Success: Jamie Reid, Vladimir Dzalbo | Internal Customers: Infrastructure Department (TBD), Engineering Department (TBD) | Focus: Verify CI & Runner SMAU | Features in this Group

GitLab Runner Lovable | Documentation • Direction Page

Testing group

Engineering totals: 2 Frontend, 3 Backend

Product Manager: James Heimbuck | Product Marketing Manager: Parker Ennis | Support: TBD | Backend Engineering Manager: Ricky Wiens | Frontend Engineering Manager: Ricky Wiens | Backend Engineering: Drew Cimino, Erick Bajao, Maxime Orefice | Frontend Engineering: Miranda Fluharty, Scott Hampton | Product Design Manager: Rayana Verissimo | UX Researcher: Lorie Whitaker | Product Designer: Rayana Verissimo | Content Marketing: Aricka Flowers | Technical Writer: Marcel Amirault | Application Security Engineer: Dominic Couture | Customer Success: Jamie Reid, Vladimir Dzalbo | Internal Customers: Quality Department (Kyle Wiebers), UX Department (TBD), Infrastructure Department (TBD), AutoDevOps and Kubernetes Group (TBD) | Focus: Verify Testing Paid GMAU | Features in this Group

Code Quality Minimal | Documentation • Direction Page
Code Testing and Coverage Viable | Documentation • Direction Page
Load Testing Minimal | Documentation • Direction Page
Web Performance Minimal | Documentation • Direction Page
Usability Testing Minimal | Documentation • Direction Page
Accessibility Testing Viable | Documentation • Direction Page

Package stage

Slack Channel: s_package | Handbook | Product Management: Kenny Johnston

Package group

Engineering totals: 1 Frontend, 5 Backend

Container Registry Viable | Documentation • Direction Page
Package Registry Viable | Documentation • Direction Page
Helm Chart Registry Minimal | Documentation • Direction Page
Dependency Proxy Viable | Documentation • Direction Page
Dependency Firewall Planned 2021 | Direction Page
Git LFS Minimal | Documentation • Direction Page
Release Evidence Minimal | Documentation • Direction Page

Release stage

Slack Channel: s_release | Product Management: Kevin Chu

Release group

Engineering totals: 2 Frontend, 4 Backend

Product Manager: Orit Golowinski | Product Marketing Manager: Parker Ennis | Support: James McGrew | Backend Engineering Manager: Nicole Williams | Backend Engineering: Shinya Maeda, Vladimir Shushlin, Amy Troschinetz, Jaime Martínez | Frontend Engineering: Andrew Fontaine, Nathan Friend | Product Design Manager: Rayana Verissimo | UX Researcher: Lorie Whitaker | Product Designer: Iain Camacho | Content Marketing: Aricka Flowers | Technical Writer: Nick Gaskill | Application Security Engineer: Dominic Couture | Customer Success: | Internal Customers: Delivery Team (TBD), Distribution Team (TBD), Gitter (TBD), Security Department (TBD), Tech Writers (TBD), AutoDevOps and Kubernetes Group (TBD) | Focus: [Release SMAU] | Features in this Group

Continuous Delivery Complete | Marketing Page • Documentation • Direction Page
Advanced Deployments Viable | Documentation • Direction Page
Review Apps Complete | Marketing Page • Documentation • Direction Page
Feature Flags Viable | Documentation • Direction Page
Release Orchestration Viable | Documentation • Direction Page
Pages Complete | Marketing Page • Documentation • Direction Page

Configure stage

Slack Channel: s_configure | GitLab Group: @gitlab-org/configure | Handbook | Product Management: Kevin Chu

Configure group

Engineering totals: 7 Backend

Slack Channel: s_configure | Slack Alias: @Configure Group | Handbook | Product Manager: Viktor Nagy | Product Marketing Manager: William Chia | Support: Lewis Brown | Backend Engineering Manager: Nicholas Klick | Backend Engineering: Thong Kuah, Hordur Freyr Yngvason, João Cunha, Tiger Watson, Mikhail Mazurskiy, Matt Kasa, Emily Ring | Product Design Manager: Justin Mandell | UX Researcher: Andrej Kiripolský | Product Designer: Maria Vrachni | Content Marketing: Aricka Flowers | Technical Writer: Amy Qualls | Application Security Engineer: Vitor Meireles De Sousa | Customer Success: Tim Poffenbarger, Chester Nwachukwu | Internal Customers: Quality Department (Joanna Shih), Delivery Team (John Skarbek), Reliability Engineering (Devin Sylva) | Focus: Configure Other | Features in this Group

Auto DevOps Viable | Marketing Page • Documentation • Direction Page
Infrastructure as Code Viable | Documentation • Direction Page
Kubernetes Management Viable | Marketing Page • Documentation • Direction Page
Cluster Cost Management Minimal | Documentation • Direction Page
Serverless Minimal | Marketing Page • Documentation • Direction Page
Secrets Management Viable | Documentation • Direction Page
ChatOps Minimal | Documentation • Direction Page
Runbooks Minimal | Documentation • Direction Page

Monitor stage

Slack Channel: s_monitor | Slack Alias: @Monitor Group | GitLab Group: @gitlab-org/monitor | Handbook | Product Management: Kevin Chu

Monitor group

Engineering totals: 3 Frontend, 4 Backend

Error Tracking Viable | Documentation • Direction Page
Incident Management Viable | Documentation • Direction Page
Metrics Viable | Documentation • Direction Page
Tracing Minimal | Documentation • Direction Page
Logging Viable | Documentation • Direction Page
Synthetic Monitoring Planned 2021 | Direction Page
GitLab Self-Monitoring | Documentation • Direction Page

Sec section

Secure stage

Slack Channel: s_secure | GitLab Group: @gitlab-org/secure | Handbook

Static Analysis group

Engineering totals: 1 Frontend, 6 Backend

Slack Channel: g_secure-static-analysis | Slack Alias: @secure_static_analysis_be | GitLab Group: @gitlab-org/secure/static-analysis-be | Product Manager: Taylor McCaslin | Product Marketing Manager: Cindy Blake | Support: Thiago Presa | Backend Engineering Manager: Thomas Woodham | Frontend Engineering Manager: Neil McCorrison | Backend Engineering: Thomas Woodham, Lucas Charles, Ross Fuhrman, Daniel Searles, Zach Rice, Saikat Sarkar | Frontend Engineering: Paul Gascou-Vaillancourt | Product Design Manager: Justin Mandell | UX Researcher: Tali Lavi | Product Designer: Rebecca "Becka" Lippert | Content Marketing: Erica Lindberg | Technical Writer: Russell Dickenson | Application Security Engineer: Nikhil George | Customer Success: Chloe Whitestone, Brian Wald, Bryan Miller | Internal Customers: Security Department (TBD), Engineering Department (TBD) | Infrastructure Manager: Anthony Sandoval | Focus: Static Analysis Paid GMAU | Features in this Group

SAST Viable | Documentation • Direction Page
Secret Detection Viable | Documentation • Direction Page

Dynamic Analysis group

Engineering totals: 2 Frontend, 5 Backend

Slack Channel: g_secure-dynamic-analysis | Slack Alias: @secure_dynamic_analysis_be | GitLab Group: @gitlab-org/secure/dynamic-analysis-be | Product Manager: Derek Ferguson | Product Marketing Manager: Cindy Blake | Support: Thiago Presa | Backend Engineering Manager: Seth Berger | Frontend Engineering Manager: Neil McCorrison | Backend Engineering: Seth Berger, Avielle Wolfe, Cam Swords, Philip Cunningham, Craig Smith | Frontend Engineering: Fernando Arias, Mark Florian | Product Design Manager: Justin Mandell | UX Researcher: Tali Lavi | Product Designer: Annabel Dunstone Gray | Content Marketing: Erica Lindberg | Technical Writer: Russell Dickenson | Application Security Engineer: Nikhil George | Customer Success: Chloe Whitestone, Brian Wald, Bryan Miller | Internal Customers: Security Department (TBD), Engineering Department (TBD) | Infrastructure Manager: Anthony Sandoval | Focus: Dynamic Analysis Paid GMAU | Features in this Group

DAST Viable | Documentation • Direction Page
IAST Planned 2022 | Direction Page
Attack Emulation Planned 2022

Composition Analysis group

Engineering totals: 1 Frontend, 5 Backend

Slack Channel: g_secure-composition-analysis | Slack Alias: @secure_composition_analysis_be | GitLab Group: @gitlab-org/secure/composition-analysis-be | Product Manager: Nicole Schwartz | Product Marketing Manager: Cindy Blake | Support: Katrin Leinweber | Backend Engineering Manager: Olivier Gonzalez | Frontend Engineering Manager: Neil McCorrison | Software Engineer in Test: Will Meek | Backend Engineering: Olivier Gonzalez, Fabien Catteau, Tetiana Chupryna, Adam Cohen, Igor Frenkel | Frontend Engineering: Dheeraj Joshi | Product Design Manager: Justin Mandell | UX Researcher: Tali Lavi | Product Designer: Kyle Mann | Content Marketing: Erica Lindberg | Technical Writer: Russell Dickenson | Application Security Engineer: Nikhil George | Customer Success: Chloe Whitestone, Brian Wald, Bryan Miller | Internal Customers: Security Department (TBD), Engineering Department (TBD) | Infrastructure Manager: Anthony Sandoval | Focus: Composition Analysis Paid GMAU | Features in this Group

Dependency Scanning Viable | Documentation • Direction Page
License Compliance Viable | Documentation • Direction Page

Fuzz Testing group

Engineering totals: 1 Frontend, 4 Backend

Fuzz Testing Minimal | Documentation • Direction Page

Threat Insights group

Engineering totals: 5 Frontend, 4 Backend

Vulnerability Management Viable | Documentation • Direction Page

Vulnerability Research group

Engineering totals: 4 Backend

Vulnerability Database | Direction Page
Security Benchmarking | Direction Page

Protect stage

Slack Channel: s_protect | GitLab Group: @gitlab-org/threat-management | Handbook

Container Security group

Engineering totals: 3 Frontend, 3 Backend

WAF Minimal | Documentation • Direction Page
Security Orchestration Planned 2021 | Direction Page
Container Network Security Minimal | Documentation • Direction Page
Container Host Security Minimal | Documentation • Direction Page
Container Scanning Viable | Documentation • Direction Page

Growth section

Growth stage

Slack Channel: s_growth | GitLab Group: @gitlab-org/growth | Handbook | Internal Customers: Sales Department (TBD), Marketing Department (TBD), Product Department (TBD), Finance Department (TBD)

Activation group

Engineering totals: 2 Backend

Conversion group

Engineering totals: 2 Backend

Expansion group

Engineering totals: 2 Backend

Adoption group

Engineering totals: 2 Backend

Product Intelligence group

Engineering totals: 1 Frontend, 4 Backend

Product Analytics Minimal | Documentation
Usage Ping Viable
Privacy Control Center

Fulfillment section

Fulfillment stage

Product Management: Justin Farris

Purchase group

Engineering totals: 6 Frontend, 5 Backend

Slack Channel: g_purchase | Product Manager: Amanda Rueda | Product Marketing Manager: TBD | Support: Donique Smit | Backend Engineering Manager: Chris Baus | Frontend Engineering Manager: [Ragnar Hardarson] | Software Engineer in Test: Chloe Liu | Backend Engineering: Josianne Hyson, Reuben Pereira, Ryan Cobb, Qingyu Zhao, Shreyas Agarwal | Frontend Engineering: Jake Burden, Michael Lunøe, Vitaly Slobodin, Ammar Alakkad, Andrei Stoicescu, Angelo Gulina | Product Design Manager: Jacki Bauer | UX Researcher: Jeff Crow | Product Designer: Emily Sybrant | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Application Security Engineer: Andrew Kelly | Customer Success: Hugo Azevedo | Internal Customers: Sales Department (TBD), Marketing Department (TBD), Product Department (TBD), Customer Success (TBD) | Infrastructure Manager: Dave Smith | Features in this Group

Purchase

License group

Engineering totals: 6 Backend

Slack Channel: g_license | Product Manager: Amanda Rueda | Product Marketing Manager: John Jeremiah | Support: Donique Smit | Backend Engineering Manager: James Lopez | Software Engineer in Test: Dan Davison | Backend Engineering: Rubén Dávila, Mark Chao, Amparo Luna, Corinna Wiesner, Tyler Amos, Vladlena Shumilo | Product Design Manager: Jacki Bauer | UX Researcher: Jeff Crow | Product Designers: Emily Sybrant, Tim Noah, Matthew Nearents | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Application Security Engineer: Andrew Kelly | Customer Success: Hugo Azevedo | Internal Customers: Sales Department (TBD), Marketing Department (TBD), Product Department (TBD), Customer Success (TBD) | Infrastructure Manager: Dave Smith | Features in this Group

License

Utilization group

Utilization

Enablement section

Enablement stage

Slack Channel: s_enablement | GitLab Group: @gitlab-org/enablement-section | Handbook

Distribution group

Engineering totals: 8 Backend

Slack Channel: g_distribution | Slack Alias: @distributionteam | GitLab Group: @gitlab-org/distribution | Handbook | Product Manager: Joshua Lambert (Interim) | Product Marketing Manager: William Chia | Support: Diana Stanley | Backend Engineering Manager: Steven Wilson | Software Engineers in Test: Nailia Iskhakova, Nick Westbury | Backend Engineering: David 'DJ' Mountney, Jason Plum, Gerard Hickey, Balasankar "Balu" C, Robert Marshall, Hossein Pursultani, Dustin Collins, Mitch Nielsen | Product Design Manager: Jacki Bauer | UX Researcher: Andrej Kiripolský | Product Designer: Sunjung Park | Technical Writer: Axil | Application Security Engineer: Andrew Kelly | Internal Customers: Quality Department (Kyle Wiebers), Infrastructure Department (TBD), Customer Success (TBD) | Infrastructure Manager: Dave Smith | Focus: Distribution PPI | Features in this Group

Omnibus Package Lovable | Documentation • Direction Page
Cloud Native Installation Viable | Documentation • Direction Page

Geo group

Engineering totals: 1 Frontend, 7 Backend

Geo-replication Viable | Marketing Page • Documentation • Direction Page
Disaster Recovery Minimal | Documentation • Direction Page
Backup/Restore of GitLab instances Minimal | Documentation • Direction Page

Memory group

Engineering totals: 4 Backend

Memory | Direction Page

Global Search group

Engineering totals: 3 Backend

Global Search Viable | Documentation • Direction Page

Database group

Engineering totals: 3 Backend

Database

Infrastructure group

Infrastructure | Documentation • Direction Page

Single-Person Groups section

Learn stage

Slack Channel: s_learn | Product Management: David DeSanto | Development: Stan Hu

Machine Learning group

Slack Channel: g_machine-larning | Features in this Group

MLOps | Direction Page
Insider Threat | Direction Page

Mobile stage

Product Management: David DeSanto

DevOps for Mobile Apps group

Slack Channel: g_mobile_devops | Features in this Group

Mobile App Signing & Deployment Management | Direction Page

Deploy stage

Product Management: Kenny Johnston

Five Minute Production App group

Engineering totals: 2 Backend

Slack Channel: five-minute-production-app | Product Sponsor: Kenny Johnston | Backend Engineering: Darby Frey, Sri Rangan | Focus: [Five Minute Production App AMAU] | Features in this Group

5 Minute Production App | Direction Page

Possible future Stages

We have boundless ambition, and we expect GitLab to continue to add new stages to the DevOps lifecycle. Below is a list of future stages we are considering:

Data, maybe leveraging Meltano product
ML/AI, maybe leveraging Kubeflow
Networking, maybe leveraging some of the open source standards for networking and/or Terraform networking providers
Design, we already have design management today
Govern, combined dashboards for secure, protect, and maybe things like requirements management

Stages are different from the application types you can service with GitLab.

Maturity

Not all categories are at the same level of maturity. Some are just minimal and some are lovable. See the category maturity page to see where each category stands.

Solutions

GitLab also does the things below that are composed of multiple categories.

Software Composition Analysis (SCA) = Dependency Scanning + License Compliance + Container Scanning
Project Management = Issue Tracking + Kanban Boards + Time Tracking
Agile Portfolio Management = Epics + Roadmaps + Issue Tracking + Kanban Boards + Time Tracking

We are intentional in not defining SCA as containing SAST and Code Quality despite some analysts using the term to also include those categories.

Other functionality

This list of other functionality so you can easily find the team that owns it. Maybe we should make our features easier to search to replace the section below.

Other functionality in Plan stage

markdown functionality
assignees
milestones
due dates
labels
issue weights
quick actions
email notifications
todos
GraphQL API foundational code

Other functionality in Create stage

Source Code group

Other functionality in Verify

Runner

Other functionality in Secure stage

Composition Analysis group

Dependency List

Threat Insights group

Pipeline and Merge Request Security reports
Interacting with Vulnerabilities
Security Dashboards
Security Approvals
Security Reports Integration

Other functionality in Protect stage

Container Security group

Policy Settings

Other functionality in Monitor stage

Health group

Facilitated functionality

Some product areas are have a broad impact across multiple stages. Examples of this include, among others:

Navigation used throughout the application, including the top bar and side bar.
Shared project views, like the project overview and settings page.
Functionality specific to the admin area and not tied to a feature belonging to a particular stage.
UI components available through our design system, Pajamas.

While the mental models for these areas are maintained by specific stage groups, everyone is encouraged to contribute within the guidelines that those teams establish. For example, anyone can contribute a new setting following the established guidelines for Settings. When a contribution is submitted that does not conform to those guidelines, we merge it and "fix forward" to encourage innovation.

If you encounter an issue falling into a facilitated area:

For issues that relate to updating the guidelines, apply the group::category label for the facilitating group.
For issues that relate to adding content related to a facilitated area, apply the group::category label for the most closely related group. For example, when adding a new setting related to Merge Requests, apply the group::source code label.

Categories A-Z

Category	Group
5 Minute Production App (`five_minute_production_app`)	Five Minute Production App
API (`api`)	Ecosystem
Accessibility Testing (`accessibility_testing`)	Testing
Advanced Deployments (`advanced_deployments`)	Release
Attack Emulation (`attack_emulation`)	Dynamic Analysis
Audit Events (`audit_events`)	Compliance
Audit Reports (`audit_reports`)	Compliance
Authentication and Authorization (`authentication_and_authorization`)	Access
Auto DevOps (`auto_devops`)	Configure
Backup/Restore of GitLab instances (`backup_restore`)	Geo
Boards (`boards`)	Project Management
ChatOps (`chatops`)	Configure
Cloud Native Installation (`cloud_native_installation`)	Distribution
Cluster Cost Management (`cluster_cost_management`)	Configure
Code Analytics (`code_analytics`)	Optimize
Code Quality (`code_quality`)	Testing
Code Review (`code_review`)	Code Review
Code Testing and Coverage (`code_testing`)	Testing
Compliance Management (`compliance_management`)	Compliance
Container Host Security (`container_host_security`)	Container Security
Container Network Security (`container_network_security`)	Container Security
Container Registry (`container_registry`)	Package
Container Scanning (`container_scanning`)	Container Security
Continuous Delivery (`continuous_delivery`)	Release
Continuous Integration (CI) (`continuous_integration`)	Continuous Integration
DAST (`dynamic_application_security_testing`)	Dynamic Analysis
Database (`database`)	Database
Dependency Firewall (`dependency_firewall`)	Package
Dependency Proxy (`dependency_proxy`)	Package
Dependency Scanning (`dependency_scanning`)	Composition Analysis
Design Management (`design_management`)	Product Planning
DevOps Reports (`devops_reports`)	Optimize
Disaster Recovery (`disaster_recovery`)	Geo
Editor Extension (`editor_extension`)	Code Review
Epics (`epics`)	Product Planning
Error Tracking (`error_tracking`)	Monitor
FE/UX Foundations (`foundations`)	Ecosystem
Feature Flags (`feature_flags`)	Release
Fuzz Testing (`fuzz_testing`)	Fuzz Testing
GDK (`gdk`)	Ecosystem
Geo-replication (`geo_replication`)	Geo
Git LFS (`git_lfs`)	Package
GitLab Documentation Site (`gitlab_docs`)	Editor
GitLab Handbook (`gitlab_handbook`)	Not owned
GitLab Runner (`runner`)	Runner
GitLab Self-Monitoring (`self_monitoring`)	Monitor
Gitaly (`gitaly`)	Gitaly
Global Search (`global_search`)	Global Search
Helm Chart Registry (`helm_chart_registry`)	Package
IAST (`interactive_application_security_testing`)	Dynamic Analysis
Importers (`importers`)	Import
Incident Management (`incident_management`)	Monitor
Infrastructure (`infrastructure`)	Infrastructure
Infrastructure as Code (`infrastructure_as_code`)	Configure
Insider Threat (`insider_threat`)	Machine Learning
Insights (`insights`)	Optimize
Integrations (`integrations`)	Ecosystem
Internationalization (`internationalization`)	Import
Issue Tracking (`issue_tracking`)	Project Management
Jenkins Importer (`jenkins_importer`)	Continuous Integration
Jira Importer (`jira_importer`)	Project Management
Kubernetes Management (`kubernetes_management`)	Configure
License (`license`)	License
License Compliance (`license_compliance`)	Composition Analysis
Live Preview (`live_preview`)	Editor
Load Testing (`load_testing`)	Testing
Logging (`logging`)	Monitor
MLOps (`mlops`)	Machine Learning
Memory (`memory`)	Memory
Merge Trains (`merge_trains`)	Continuous Integration
Metrics (`metrics`)	Monitor
Mobile App Signing & Deployment Management (`mobile_signing_deployment`)	DevOps for Mobile Apps
Navigation & Settings (`navigation`)	Editor
Omnibus Package (`omnibus_package`)	Distribution
Package Registry (`package_registry`)	Package
Pages (`pages`)	Release
Pipeline Authoring (`pipeline_authoring`)	Pipeline Authoring
Planning Analytics (`planning_analytics`)	Optimize
Privacy Control Center (`privacy_control_center`)	Product Intelligence
Product Analytics (`product_analytics`)	Product Intelligence
Projects (`projects`)	Project Management
Purchase (`purchase`)	Purchase
Quality Management (`quality_management`)	Certify
Release Evidence (`release_evidence`)	Package
Release Orchestration (`release_orchestration`)	Release
Requirements Management (`requirements_management`)	Certify
Review Apps (`review_apps`)	Release
Roadmaps (`roadmaps`)	Product Planning
Runbooks (`runbooks`)	Configure
SAST (`static_application_security_testing`)	Static Analysis
Secret Detection (`secret_detection`)	Static Analysis
Secrets Management (`secrets_management`)	Configure
Security Benchmarking (`security_benchmarking`)	Vulnerability Research
Security Orchestration (`security_orchestration`)	Container Security
Serverless (`serverless`)	Configure
Service Desk (`service_desk`)	Certify
Snippets (`snippets`)	Editor
Source Code Management (`source_code_management`)	Source Code
Static Site Editor (`static_site_editor`)	Editor
Subgroups (`subgroups`)	Access
Synthetic Monitoring (`synthetic_monitoring`)	Monitor
Templates (`templates`)	Import
Time Tracking (`time_tracking`)	Project Management
Tracing (`tracing`)	Monitor
Usability Testing (`usability_testing`)	Testing
Usage Ping (`usage_ping`)	Product Intelligence
Users (`users`)	Access
Utilization (`utilization`)	Utilization
Value Stream Management (`value_stream_management`)	Optimize
Vulnerability Database (`vulnerability_database`)	Vulnerability Research
Vulnerability Management (`vulnerability_management`)	Threat Insights
WAF (`web_firewall`)	Container Security
Web IDE (`web_ide`)	Editor
Web Performance (`web_performance`)	Testing
Wiki (`wiki`)	Editor

Product sections, stages, groups, and categories

Maintained by:

On this page

Interfaces

Hierarchy

Naming

More Details

Solutions

Capabilities

Layers

Changes

Examples

DevOps Stages

Dev section

Manage stage

Access group

Compliance group

Import group

Optimize group

Plan stage

Project Management group

Product Planning group

Certify group

Create stage

Source Code group

Code Review group

Editor group

Gitaly group

Ecosystem group

Ops section

Verify stage

Continuous Integration group

Pipeline Authoring group

Runner group

Testing group

Package stage

Package group

Release stage

Release group

Configure stage

Configure group

Monitor stage

Monitor group

Sec section

Secure stage

Static Analysis group

Dynamic Analysis group

Composition Analysis group

Fuzz Testing group

Threat Insights group

Vulnerability Research group

Protect stage

Container Security group

Growth section

Growth stage

Activation group

Conversion group

Expansion group

Adoption group

Product Intelligence group

Fulfillment section

Fulfillment stage

Purchase group

License group

Utilization group

Enablement section

Enablement stage

Distribution group

Geo group

Memory group

Global Search group

Database group

Infrastructure group

Single-Person Groups section

Learn stage

Machine Learning group

Mobile stage

DevOps for Mobile Apps group

Deploy stage

Five Minute Production App group