Product stages, groups, and categories

1. You are here:
2. Handbook
3. Product
4. Product stages, groups, and categories

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
      • Analytics group
    • Plan stage
      • Project Management group
      • Portfolio Management group
      • Certify group
    • Create stage
      • Source Code group
      • Knowledge group
      • Editor group
      • Gitaly group
      • Gitter group
  • CI/CD section
    • Verify stage
      • Continuous Integration group
      • Runner group
      • Testing group
    • Package stage
      • Package group
    • Release stage
      • Progressive Delivery group
      • Release Management group
  • Ops section
    • Configure stage
      • Orchestration group
      • System group
    • Monitor stage
      • APM group
      • Health group
  • Secure section
    • Secure stage
      • Static Analysis group
      • Dynamic Analysis group
      • Composition Analysis group
  • Defend section
    • Defend stage
      • Runtime Application Security group
      • Threat Management group
      • Application Infrastructure Security group
  • Growth section
    • Growth stage
      • Acquisition group
      • Conversion group
      • Expansion group
      • Retention group
      • Fulfillment group
      • Telemetry group
  • Enablement section
    • Enablement stage
      • Distribution group
      • Geo group
      • Memory group
      • Ecosystem group
      • Search group
      • Database group
• Possible future Stages
• Maturity
• Solutions
• Other functionality
  • Other functionality in Plan stage
  • Other functionality in Create stage
    • Source Code group
  • Other functionality in Verify
  • Other functionality in Secure stage
    • Static & Dynamic Analysis group
    • Composition Analysis group
  • Other functionality in Monitor stage
    • APM group
    • Health group
  • Shared functionality

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 Vision
• 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
• Product marketing specializations

Hierarchy

The categories form a hierarchy:

1. Sections: These map to sections within the Development department of the Engineering division in the R&D (Research and Development) cost center. All of Product Management is in the Product Management department of the Product division in the R&D cost center.
2. Stages: Stages start with the 7 loop stages, then add Manage, Secure, and Defend 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.
3. 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.
4. 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.
5. 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".

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. For such groups, their name should be written as "Stage:Group" when the writer wants to give extra context. 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, determined by what exists in the following hierarchy:

Marketing product page > docs page > strategy page > 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.

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:

1. Harder to keep the interfaces up to date.
2. Harder to automatically update things.
3. Harder to train and test people.
4. Harder to display more levels.
5. Harder to reason, falsify, and talk about it.
6. Harder to define what level something should be in.
7. 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 Enablment 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. 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:

1. VP of Product
2. VP of Product Strategy
3. The Product Director relevant to the stage group(s)
4. The Engineering Director relevant to the stage group(s)
5. CEO

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

1. VP of Engineering
2. Senior Director of Development
3. Director of Quality

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

Product Director: Eric Brinkman | Engineering Director: Tim Zallmann | Support Manager: Shaun McCann | Product Marketing Manager: John Jeremiah | Quality: Ramya Authappan | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Jose Finotto

Manage stage

Access group

Product Manager: Jeremy Watson | Product Marketing Manager: John Jeremiah | Support: Blair Lunceford | Backend Engineering Manager: Liam McAndrew | Frontend Engineering Manager: Dennis Tang | Test Automation Engineer: Sanad Liaquat | UX Manager: Shane Bouchard | Product Designer: Matej Latin | Content Marketing: Suri Patel | Technical Writer: Evan Read | Application Security Engineer: Jeremy Matos | Internal Customers: Support Department, Security Department, Infrastructure Department | Infrastructure Manager: Jose Finotto

• Authentication and Authorization Complete | Documentation • Strategy
• Groups | Documentation • Strategy
• Users | Documentation • Strategy

Compliance group

Product Manager: Matt Gonzales | Product Marketing Manager: John Jeremiah | Support: Blair Lunceford | Backend Engineering Manager: Liam McAndrew | Frontend Engineering Manager: Dennis Tang | Test Automation Engineer: Sanad Liaquat | UX Manager: Shane Bouchard | Product Designer: Matej Latin | Content Marketing: Suri Patel | Technical Writer: Evan Read | Application Security Engineer: Jeremy Matos | Internal Customers: Support Department, Security Department, Infrastructure Department | Infrastructure Manager: Jose Finotto

• Audit Management Viable | Documentation • Strategy
• Workflow Policies Planned 2019 | Strategy

Import group

Product Manager: Jeremy Watson (Interim) | Product Marketing Manager: John Jeremiah | Backend Engineering Manager: Liam McAndrew | Frontend Engineering Manager: Dennis Tang | Test Automation Engineer: Sanad Liaquat | UX Manager: Shane Bouchard | Product Designer: Daniel Mora | Content Marketing: Suri Patel | Technical Writer: Evan Read | Application Security Engineer: Jeremy Matos | Internal Customers: Support Department, Product Department | Infrastructure Manager: Jose Finotto

• Importers
• Templates | Documentation
• Internationalization | Documentation • Strategy

Analytics group

Product Manager: Virjinia Alexieva | Product Marketing Manager: John Jeremiah | Support: Blair Lunceford | Backend Engineering Manager: Dan Jensen | Frontend Engineering Manager: Dennis Tang | Test Automation Engineer: Désirée Chevalier | UX Manager: Shane Bouchard | Product Designer: [Nick Post] | Content Marketing: Suri Patel | Technical Writer: Evan Read | Application Security Engineer: Jeremy Matos | Internal Customers: Engineering Department, Product Department, Quality Department, Development Department | Infrastructure Manager: Jose Finotto

• DevOps Score Minimal | Documentation • Strategy
• Code Analytics New in 2019 | Strategy
• Value Stream Management Minimal | Marketing Page • Strategy

Plan stage

Project Management group

Product Manager: Gabe Weaver | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: Sean McGivern | Frontend Engineering Manager: Donald Cook | Test Automation Engineer: Walmyr Lima e Silva Filho | UX Manager: Shane Bouchard | Product Designers: Annabel Dunstone Gray, Alexis Ginsberg | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Application Security Engineer: Costel Maxim | Internal Customers: Engineering Department, Product Department | Infrastructure Manager: Jose Finotto

• Issue Tracking Complete | Documentation • Strategy
• Kanban Boards Viable | Marketing Page • Documentation • Strategy
• Time Tracking Viable | Marketing Page • Documentation • Strategy

Portfolio Management group

Product Manager: Keanon O'Keefe | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: John Hope | Frontend Engineering Manager: Donald Cook | Test Automation Engineer: Walmyr Lima e Silva Filho | UX Manager: Shane Bouchard | Product Designers: Annabel Dunstone Gray, Alexis Ginsberg | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Application Security Engineer: Costel Maxim | Internal Customers: Engineering Department, Product Department | Infrastructure Manager: Jose Finotto

• Agile Portfolio Management Viable | Marketing Page • Strategy

Certify group

Product Manager: Mark Wood | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: John Hope | Frontend Engineering Manager: Donald Cook | Test Automation Engineer: Walmyr Lima e Silva Filho | UX Manager: Shane Bouchard | Product Designers: Annabel Dunstone Gray, Alexis Ginsberg | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Application Security Engineer: Costel Maxim | Internal Customers: Quality Department, Support Department | Infrastructure Manager: Jose Finotto

• Requirements Management Planned 2020 | Strategy
• Quality Management Planned 2020 | Strategy
• Service Desk Viable | Marketing Page • Documentation • Strategy

Create stage

Source Code group

Product Manager: James Ramsay (Interim) | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: Michelle Gill | Backend Team | Frontend Engineering Manager: André Luís | Test Automation Engineer: Mark Lapierre | UX Manager: Shane Bouchard | Product Designer: Pedro Moreira da Silva | Content Marketing: Suri Patel | Technical Writer: Marcia Ramos | Application Security Engineer: Juan Broullon | Internal Customers: Engineering Department, Marketing Department, Product Department | Infrastructure Manager: Jose Finotto

• Source Code Management Lovable | Marketing Page • Documentation • Strategy
• Code Review Lovable | Marketing Page • Documentation • Strategy

Knowledge group

Product Manager: Christen Dybenko | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: Darva Satcher | Backend Team | Frontend Engineering Manager: André Luís | Test Automation Engineer: Tomislav Nikić | UX Manager: Shane Bouchard | Product Designer: Jarek Ostrowski | Content Marketing: Suri Patel | Technical Writer: Marcia Ramos | Application Security Engineer: Juan Broullon | Internal Customer: UX Department | Infrastructure Manager: Jose Finotto

• Design Management New in 2019 | Documentation • Strategy
• Wiki Viable | Documentation • Strategy

Editor group

Product Manager: Kai Armstrong | Product Marketing Manager: John Jeremiah | Support: TBD | Backend Engineering Manager: Darva Satcher | Backend Team | Frontend Engineering Manager: André Luís | Test Automation Engineer: Tomislav Nikić | UX Manager: Shane Bouchard | Product Designer: Marcel van Remmerden | Content Marketing: Suri Patel | Technical Writer: Marcia Ramos | Application Security Engineer: Juan Broullon | Internal Customers: Marketing Department, Engineering Department, Finance Department, People Operations, Product Department | Infrastructure Manager: Jose Finotto

• Web IDE Viable | Documentation • Strategy
• Live Coding Planned 2020 | Strategy
• Snippets Minimal | Documentation • Strategy

Gitaly group

Product Manager: James Ramsay | Support: Will Chandler | Backend Engineering Manager: ZJ (Interim) | Frontend Engineering Manager: Tim Z (Interim) | Test Automation Engineer: Mark Lapierre | UX Manager: Shane Bouchard | Product Designer: Pedro Moreira da Silva | Technical Writer: Axil | Application Security Engineer: Juan Broullon | Internal Customers: Quality Department, Infrastructure Department | Infrastructure Manager: Jose Finotto

• Gitaly | Documentation • Strategy

Gitter group

Product Manager: James Ramsay (Interim) | Support: TBD | Backend Engineering Manager: ZJ (Interim) | Frontend Engineering Manager: Tim Z (Interim) | Test Automation Engineers: Mark Lapierre, Tomislav Nikić | UX Manager: Shane Bouchard | Product Designer: Jarek Ostrowski | Technical Writer: Axil | Application Security Engineer: Juan Broullon | Infrastructure Manager: Jose Finotto

• Gitter | Strategy

CI/CD section

Product Director: Jason Lenny | Engineering Director: Darby Frey | Support Manager: Lyle Kozloff | Product Marketing Manager: William Chia | Quality: Mek Stittri | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Dave Smith

Verify stage

Continuous Integration group

Product Manager: Jason Lenny (Interim) | Product Marketing Manager: William Chia | Support: Namho Kim | Backend Engineering Manager: Elliot Rushton | Frontend Engineering Manager: John Hampton (Interim) | Test Automation Engineer: Zeff Morgan | UX Manager: Nadia Udalova | Product Designer: Dimitrie Hoekstra | Content Marketing: Aricka Flowers | Technical Writer: [Marcel Amirault] | Internal Customers: Quality Department, UX Department, Infrastructure Department, Engineering Department, AutoDevOps and Kubernetes Group | Infrastructure Manager: Dave Smith

• Continuous Integration (CI) Lovable | Marketing Page • Documentation • Strategy

Runner group

Product Manager: Darren Eastman | Product Marketing Manager: William Chia | Support: Namho Kim | Backend Engineering Manager: Elliot Rushton | Frontend Engineering Manager: John Hampton (Interim) | Test Automation Engineer: Zeff Morgan | UX Manager: Nadia Udalova | Product Designer: Juan J. Ramirez | Content Marketing: Aricka Flowers | Technical Writer: Evan Read | Internal Customers: Infrastructure Department, Engineering Department | Infrastructure Manager: Dave Smith

• GitLab Runner | Documentation • Strategy

Testing group

Product Manager: James Heimbuck | Product Marketing Manager: William Chia | Support: Namho Kim | Backend Engineering Manager: Elliot Rushton | Frontend Engineering Manager: John Hampton (Interim) | Test Automation Engineer: Zeff Morgan | UX Manager: Nadia Udalova | Product Designer: Juan J. Ramirez | Content Marketing: Aricka Flowers | Technical Writer: Evan Read | Internal Customers: Quality Department, UX Department, Infrastructure Department, AutoDevOps and Kubernetes Group | Infrastructure Manager: Dave Smith

• Code Quality Minimal | Documentation • Strategy
• Unit Testing Minimal | Strategy
• Integration Testing Planned 2020 | Strategy
• Load Testing Planned 2020 | Strategy
• Web Performance Minimal | Documentation • Strategy
• System Testing Planned 2020 | Strategy
• Usability Testing New in 2019 | Documentation • Strategy
• Accessibility Testing Planned 2020 | Strategy

Package stage

Package group

Product Manager: Tim Rizzi | Product Marketing Manager: William Chia | Support: Sara Ahbabou | Backend Engineering Manager: Daniel Croft | Frontend Engineering Manager: John Hampton | UX Manager: Nadia Udalova | Product Designer: Iain Camacho | Content Marketing: Aricka Flowers | Technical Writer: Axil | Internal Customers: Distribution Team, Infrastructure Department | Infrastructure Manager: Dave Smith

• Container Registry Viable | Documentation • Strategy
• Package Registry Minimal | Strategy
• Helm Chart Registry Planned 2020 | Strategy
• Dependency Proxy New in 2019 | Documentation • Strategy

Release stage

Progressive Delivery group

Product Manager: Orit Golowinski | Product Marketing Manager: William Chia | Support: TBD | Backend Engineering Manager: Darby Frey | Frontend Engineering Manager: John Hampton | UX Manager: Nadia Udalova | Product Designers: Rayana Verissimo, Mike Nichols | Content Marketing: Aricka Flowers | Technical Writer: Marcia Ramos | Internal Customers: Delivery Team, Distribution Team, Gitter, Security Department, Tech Writers, AutoDevOps and Kubernetes Group | Infrastructure Manager: Dave Smith

• Continuous Delivery Complete | Marketing Page • Documentation • Strategy
• Incremental Rollout Minimal | Documentation • Strategy
• Review Apps Complete | Marketing Page • Documentation • Strategy
• Feature Flags Viable | Documentation • Strategy

Release Management group

Product Manager: Orit Golowinski (Interim) | Product Marketing Manager: William Chia | Support: TBD | Backend Engineering Manager: Darby Frey | Frontend Engineering Manager: John Hampton | UX Manager: Nadia Udalova | Product Designers: Rayana Verissimo, Mike Nichols | Content Marketing: Aricka Flowers | Technical Writer: Marcia Ramos | Internal Customers: Distribution Team, Gitter, Security Department, Tech Writers, Marketing Department, UX Department | Infrastructure Manager: Dave Smith

• Release Orchestration Minimal | Documentation • Strategy
• Secrets Management New in 2019 | Strategy
• Release Governance New in 2019 | Strategy
• Pages Complete | Marketing Page • Documentation • Strategy

Ops section

Product Director: Kenny Johnston | Engineering Director: Daniel Croft | Support Manager: Lee Matos | Product Marketing Manager: William Chia | Quality: Mek Stittri | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Jose Finotto

Configure stage

Orchestration group

Product Manager: Daniel Gruesso | Product Marketing Manager: William Chia | Support: Lewis Brown | Backend Engineering Manager: Seth Engelhard (Interim) | Frontend Engineering Manager: Jean du Plessis | Test Automation Engineer: Dan Davison | UX Manager: Aaron K. White | Product Designers: Taurie Davis, Maria Vrachni | Content Marketing: Aricka Flowers | Technical Writer: Evan Read | Internal Customers: Quality Department, Delivery Team, Reliability Engineering, Engineering Department | Infrastructure Manager: Jose Finotto

• Auto DevOps Minimal | Marketing Page • Documentation • Strategy
• Kubernetes Configuration Viable | Marketing Page • Documentation • Strategy
• Chaos Engineering Planned 2019 | Strategy
• Cluster Cost Optimization Planned 2019 | Strategy

System group

Product Manager: Viktor Nagy | Product Marketing Manager: William Chia | Support: Lewis Brown | Backend Engineering Manager: Nicholas Klick | Frontend Engineering Manager: Jean du Plessis | Test Automation Engineer: Dan Davison | UX Manager: Aaron K. White | Product Designers: Taurie Davis, Maria Vrachni | Content Marketing: Aricka Flowers | Technical Writer: Evan Read | Internal Customers: Quality Department, Delivery Team, Reliability Engineering | Infrastructure Manager: Jose Finotto

• Serverless Minimal | Marketing Page • Documentation • Strategy
• Infrastructure as Code New in 2019 | Strategy
• ChatOps Minimal | Documentation • Strategy
• Runbooks Minimal | Documentation • Strategy

Monitor stage

APM group

Product Manager: Dov Hershkovitch | Product Marketing Manager: William Chia | Support: Cody West | Backend Engineering Manager: Matt Nohr | Frontend Engineering Manager: Adriel Santiago (Interim) | UX Manager: Aaron K. White | Product Designer: Amelia Bauerly | Content Marketing: Aricka Flowers | Technical Writer: Axil | Internal Customers: Infrastructure Department, Engineering Department | Infrastructure Manager: Jose Finotto

• Metrics Viable | Documentation • Strategy
• Tracing Minimal | Documentation • Strategy
• Logging Minimal | Documentation • Strategy

Health group

Product Manager: Sarah Waldner | Product Marketing Manager: William Chia | Support: Cody West | Backend Engineering Manager: Seth Engelhard | Frontend Engineering Manager: Clement Ho | UX Manager: Aaron K. White | Product Designer: Amelia Bauerly | Content Marketing: Aricka Flowers | Technical Writer: Axil | Internal Customers: Infrastructure Department, Engineering Department | Infrastructure Manager: Jose Finotto

• Error Tracking Minimal | Documentation • Strategy
• Cluster Monitoring Viable | Documentation • Strategy
• Synthetic Monitoring Planned 2020 | Strategy
• Incident Management New in 2019 | Documentation • Strategy
• Status Page Planned 2020 | Strategy

Secure section

Product Director: David DeSanto | Engineering Director: Todd Stadelhofer | Support Manager: Tom Atkins | Product Marketing Manager: Cindy Blake | Quality: Tanya Pazitny | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Anthony Sandoval

Secure stage

Static Analysis group

Product Manager: Sam Kerr (Life Support) | Product Marketing Manager: Cindy Blake | Support: Thiago Presa | Backend Engineering Manager: Thomas Woodham | Frontend Engineering Manager: Lukas Eipert (Interim) | Test Automation Engineer: Aleksandr Soborov | UX Manager: Valerie Karnes | Product Designers: Camellia X. YANG, Annabel Dunstone Gray | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customers: Security Department, Engineering Department | Infrastructure Manager: Anthony Sandoval

• SAST Viable | Documentation • Strategy
• Secret Detection New in 2019 | Documentation • Strategy
• Language-specific

Dynamic Analysis group

Product Manager: Sam Kerr (Life Support) | Product Marketing Manager: Cindy Blake | Support: Thiago Presa | Backend Engineering Manager: Seth Berger | Frontend Engineering Manager: Lukas Eipert (Interim) | Test Automation Engineer: Aleksandr Soborov | UX Manager: Valerie Karnes | Product Designers: Camellia X. YANG, Annabel Dunstone Gray | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customers: Security Department, Engineering Department | Infrastructure Manager: Anthony Sandoval

• DAST Viable | Documentation • Strategy
• IAST Planned 2020 | Strategy
• Fuzzing Planned 2020 | Strategy

Composition Analysis group

Product Manager: Nicole Schwartz | Product Marketing Manager: Cindy Blake | Support: Greg Myers | Backend Engineering Manager: Olivier Gonzalez (Interim) | Frontend Engineering Manager: Lukas Eipert (Interim) | Test Automation Engineer: Aleksandr Soborov | UX Manager: Valerie Karnes | Product Designer: Kyle Mann | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customers: Security Department, Engineering Department | Infrastructure Manager: Anthony Sandoval

• Dependency Scanning Viable | Documentation • Strategy
• Container Scanning Viable | Documentation • Strategy
• License Compliance Minimal | Documentation • Strategy
• Vulnerability Database Minimal | Strategy

Defend section

Product Director: David DeSanto | Engineering Director: Todd Stadelhofer | Support Manager: Tom Atkins | Product Marketing Manager: Cindy Blake | Quality: Mek Stittri | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Anthony Sandoval

Defend stage

Runtime Application Security group

Product Manager: Sam Kerr | Product Marketing Manager: Cindy Blake | Support: Greg Myers | Backend Engineering Manager: Thomas Woodham | Frontend Engineering Manager: Lukas Eipert (Interim) | UX Manager: Valerie Karnes | Product Designer: Rebecca "Becka" Lippert | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customers: Security Department, Infrastructure Department | Infrastructure Manager: Anthony Sandoval

• RASP Planned 2020 | Strategy
• WAF New in 2019 | Documentation • Strategy

Threat Management group

Product Manager: Matt Wilson | Product Marketing Manager: Cindy Blake | Support: Greg Myers | Backend Engineering Manager: Thomas Woodham | Frontend Engineering Manager: Lukas Eipert (Interim) | UX Manager: Valerie Karnes | Product Designers: Andy Volpe, Rebecca "Becka" Lippert | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customer: Security Department | Infrastructure Manager: Anthony Sandoval

• Threat Detection Planned 2020 | Strategy
• UEBA Planned 2020 | Strategy
• Vulnerability Management Planned 2019 | Strategy

Application Infrastructure Security group

Product Manager: Sam Kerr | Product Marketing Manager: Cindy Blake | Support: Greg Myers | Backend Engineering Manager: Thomas Woodham | Frontend Engineering Manager: Lukas Eipert (Interim) | UX Manager: Valerie Karnes | Product Designers: Andy Volpe, Rebecca "Becka" Lippert | Content Marketing: Erica Lindberg | Technical Writer: Axil | Internal Customers: Security Department, Infrastructure Department | Infrastructure Manager: Anthony Sandoval

• DLP Planned 2020 | Strategy
• Storage Security Planned 2020 | Strategy
• Container Network Security Planned 2019 | Strategy

Growth section

Product Director: Scott Williamson (Interim) | Engineering Director: Bartek Marnane | Support Manager: Shaun McCann | Product Marketing Manager: Ashish Kuthiala | Quality: Mek Stittri | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Dave Smith

Growth stage

Internal Customers: Sales Department, Marketing Department, Product Department, Finance Department

Acquisition group

Product Manager: Jensen Stava | Engineering Manager: Phil Calder (Interim) | Support: Amanda Rueda | UX Manager: Jacki Bauer | Product Designer: Kevin Comoli | Technical Writer: Russell Dickenson | Infrastructure Manager: Dave Smith

Conversion group

Product Manager: Sam Awezec | Engineering Manager: Phil Calder (Interim) | Support: Amanda Rueda | UX Manager: Jacki Bauer | Product Designer: Kevin Comoli | Technical Writer: Russell Dickenson | Infrastructure Manager: Dave Smith

Expansion group

Product Manager: Tim Hey | Engineering Manager: Phil Calder | UX Manager: Jacki Bauer | Product Designer: Matej Latin | Technical Writer: Russell Dickenson | Infrastructure Manager: Dave Smith

Retention group

Product Manager: Michael Karampalas | Engineering Manager: Phil Calder | Support: Amanda Rueda | UX Manager: Jacki Bauer | Product Designer: Matej Latin | Technical Writer: Russell Dickenson | Infrastructure Manager: Dave Smith

Fulfillment group

Product Manager: Luca Williams | Product Marketing Manager: John Jeremiah | Support: Amanda Rueda | Backend Engineering Manager: James Lopez (Interim) | Frontend Engineering Manager: Chris Baus | UX Manager: Jacki Bauer | Product Designers: Tim Noah, Emily Sybrant | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Internal Customers: Sales Department, Marketing Department, Product Department, Customer Success | Infrastructure Manager: Dave Smith

• Account Management | Strategy

Telemetry group

Product Manager: [Tim Hey (Interim)] | Product Marketing Manager: John Jeremiah | Support: Amanda Rueda | Backend Engineering Manager: James Lopez (Interim) | UX Manager: Jacki Bauer | Content Marketing: Suri Patel | Technical Writer: Russell Dickenson | Internal Customers: Sales Department, Marketing Department, Product Department, Customer Success, Data Team | Infrastructure Manager: Dave Smith

• Collection | Strategy
• Analysis Minimal

Enablement section

Product Director: Joshua Lambert | Engineering Director: Chun Du | Support Manager: Jason Colyer | Product Marketing Manager: Ashish Kuthiala | Quality: Tanya Pazitny | Content Marketing: Erica Lindberg | Technical Writing: Mike Lewis | Infrastructure Manager: Dave Smith

Enablement stage

Distribution group

Product Manager: Larissa Lane | Product Marketing Manager: William Chia | Support: Diana Stanley | Backend Engineering Manager: Steven Wilson | UX Manager: Jacki Bauer | Technical Writer: Axil | Internal Customers: Quality Department, Infrastructure Department, Customer Success | Infrastructure Manager: Dave Smith

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

Geo group

Product Manager: Fabian Zimmer | Product Marketing Manager: John Jeremiah | Support: Aric Buerer | Backend Engineering Manager: Rachel Nienaber | Frontend Engineering Manager: André Luís (Interim) | Test Automation Engineer: Jennie Louie | UX Manager: Jacki Bauer | Technical Writer: Evan Read | Internal Customer: Infrastructure Department | Infrastructure Manager: Dave Smith

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

Memory group

Product Manager: Joshua Lambert (Interim) | Product Marketing Manager: Ashish Kuthiala (Interim) | Support: Cindy Pallares | Backend Engineering Manager: Craig Gomes | Test Automation Engineers: Grant Young, Nailia Iskhakova | UX Manager: Jacki Bauer | Content Marketing: Erica Lindberg | Technical Writer: Mike Lewis | Internal Customers: Quality Department, Infrastructure Department | Infrastructure Manager: Dave Smith

Ecosystem group

Product Manager: Patrick Deuley | Product Marketing Manager: Ashish Kuthiala (Interim) | Backend Engineering Manager: Nick Nguyen | Frontend Engineering Manager: Nick Nguyen (Interim) | UX Manager: Jacki Bauer | Content Marketing: Erica Lindberg | Technical Writer: Mike Lewis | Internal Customers: Alliances Department, Customer Success | Infrastructure Manager: Dave Smith

• SDKs & Integration APIs Viable | Documentation
• Integrations Viable | Documentation

Search group

Product Manager: Kai Armstrong (Interim) | Product Marketing Manager: John Jeremiah | Support: Blair Lunceford | Backend Engineering Manager: Craig Gomes (Interim) | Frontend Engineering Manager: Craig Gomes (Interim) | UX Manager: Jacki Bauer | Product Designer: Marcel van Remmerden (Interim) | Technical Writer: Russell Dickenson | Internal Customers: Engineering Department, Customer Success, Infrastructure Department | Infrastructure Manager: Dave Smith

• Search Viable | Documentation • Strategy

Database group

Product Manager: Joshua Lambert (Interim) | Product Marketing Manager: TBD | Backend Engineering Manager: Craig Gomes | UX Manager: Jacki Bauer | Content Marketing: TBD | Technical Writer: TBD | Internal Customers: Quality Department, Infrastructure Department | Infrastructure Manager: Dave Smith

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:

1. Data, maybe leveraging Meltano product
2. ML/AI, maybe leveraging Kubeflow
3. Networking, maybe leveraging some of the open source standards for networking and/or Terraform networking providers
4. Design, we already have design management today
5. Govern, combined dashboards for secure, defend, 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.

1. Software Composition Analysis (SCA) = Dependency Scanning + License Compliance + Container Scanning
2. Application Performance Monitoring (APM) = Metrics + Tracing + Real User Monitoring (RUM)
3. Project Management = 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

• gitlab-shell
• gitlab-workhorse

Source Code group

• Repository Mirroring

Other functionality in Verify

• Runner

Other functionality in Secure stage

Static & Dynamic Analysis group

• Project and Group Security Dashboards
• Interacting with Vulnerabiilities

Composition Analysis group

• Pipeline and Merge Request Security reports
• Dependency List

Other functionality in Monitor stage

APM group

• GitLab Self-monitoring
• Instrumentation Workflow
• Triaging Workflow

Health group

• Operations Dashboard
• Resolve Workflow
• Improve Workflows

Shared functionality

Some areas of the product are shared 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.

Issues related to these areas should be owned on a case-by-case basis, depending on the problem to solve. If you encounter an issue falling into a shared area, you can:

• Apply the group::not_owned label to indicate a lack of ownership that requires resolution.
• @ mention a product manager in the most closely related stage for assistance with ownership and prioritization.

Once a responsible individual for the issue has been established, remove the group::not_owned label and replace it with an appropriate label for the group who is taking ownership for the issue.