The Expansion Team at GitLab focuses on running experiments to increase the expansion of our platform and expanding usage by teams within an organization or by individual users additionally we strive to increase the value of GitLab to existing customers getting them to adopt new features in higher paid tiers.
~"group::expansion" team, create a new issue label it with ~"devops::growth" ~"group::expansion"As part of the wider Growth stage we track and work on issues with the label combination of ~"devops::growth" ~"group::expansion".
Our team follows the Product Development Flow utilizing all labels from ~workflow::start to ~workflow::complete.
We adhere to the Completion Criteria and Who Transitions Out outlined in the Product Development Flow to progress issues from one stage to the next.
We use workflow boards to track issue progress throughout a milestone. Workflow boards should be viewed at the highest group level for visibility into all nested projects in a group.
| gitlab-org | gitlab-com | gitlab-services | all groups |
|---|---|---|---|
| Expansion Workflow | - | Expansion Workflow | - |
This approach helps us stay organized and keeps the work we do in once easy to access place. This also helps others find our work easily and contribute.
As we work on building product and experiments we create multiple issues which then become artifacts. We leverage these artifacts throughout the life of a pice of work. These also help other teams orient themselves around the work we have done.
Typical artifacts you'd see in our epics and issues are: