Category maturity

GitLab features are grouped into a hierarchy, representing increasingly higher level capabilities. Features make up a broader Category, which then belong to a DevOps Stage. Stages are assigned a yearly lifecycle, and categories a maturity.

Planned category maturity

The maturity framework makes it easy to visualize where GitLab is making investments, and resulting category maturity improvements. As part of the planning process for each category, the set of features required and expected date to reach the next maturity is maintained. It can also be used to compare historical to planned velocity. A reduction in velocity is one of our biggest risks.

Below is a chart which illustrates the aggregate current and future progression of all categories.

DevOps stage maturity

Non-DevOps stage maturity

Learn how to make changes to categories and their maturity on our website handbook page.