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:
Our deck, the slides that we use to describe the company
Product marketing specializations
The functionality of GitLab is ordered in 4 level hierarchy:
Stages: One of the 7 DevOps lifecycle stages (see below), one of the two areas that span the entire lifecycle, or a non-lifecycle stage like Auth or BizOps.
Categories: High-level capabilities that may be a standalone product at another company. e.g. Portfolio Management.
Capabilities: An optional group of functionality that is made up of smaller discrete features. e.g. Epics. Capabilities are listed as the second tier of bullets below. We have feature categories but it is incomplete and not used everywhere.
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.
DevOps lifecycle stages
At GitLab the Dev and Ops split is different because our CI/CD functionality is one codebase that falls under Ops.