Growth:Expansion Group

1. You are here:
2. Handbook
3. Engineering
4. Development Department
5. Growth Sub-department
6. Growth:Expansion Group

Maintained by:

E

On this page

• Vision
• How we work
  • Prioritization
  • Workflow
    • Overview
    • Working boards
  • UX
• Team Members
• Stable Counterparts
• Expansion Links
• Common Links

Vision

The Expansion Group is part of the Growth section and works directly with our product counterparts on the Product Direction for Expansion. As well as feature deliverables for GitLab products the Expansion Group works to deliver product based Growth-Deliverables.

See What's keeping us busy

• I have a question. Who do I ask?

Questions should start by @ mentioning the Product Manager for the Expansion group or creating a new issue in the Growth Product Expansion issues list.

How we work

• We're data savvy
• In accordance with our GitLab values
• Transparently: nearly everything is public
• We get a chance to work on the things we want to work on
• Everyone can contribute; no silos

Prioritization

Prioritization is a collaboration between Product, UX, Data, and Engineering.

• We use the ICE framework for experiments.
• We use Priority and Severity labels for bugs.

Workflow

We use the Product Development workflow when working on issues and merge requests across multiple projects.

While not all of the work we do relates to the GitLab project directly, we use milestones to track Deliverables and other enhancements.

Overview

Working boards

• The validation track is where the Product Manager - usually in collaboration with UX - defines what the team should aim to deliver. Once complete, the Product Manager will move to workflow::planning breakdown (larger issues) or straight to workflow::scheduling for Engineering to pick up. If there is no Engineering input required the issue can be closed.
• The Retention Engineering group (group::retention) schedules issues for development in the build phase, based on the Product Managers priorities. For bugs and security issues, Priority and Severity labels will have been added by the Product Manager.
• Combined workflow board shows the combined workflow including validation and build tracks.

The above boards can be filtered by milestone to provide additional context around priority. For example a P3 security issue (due within 90 days) will be added to one of the next 3 milestones by the Engineering team during the workflow::scheduling stage to ensure that SLA is met.

UX

The Growth UX team has a handbook page which includes Growth specific workflows.

Team Members

The following people are permanent members of the Expansion Group:

Stable Counterparts

We work closely with our colleagues in the Retention, Fulfillment and Telemetry groups.

The following members of other functional teams are our stable counterparts:

Expansion Links

• #g_expansion in Slack (GitLab internal)
• Expansion issues

Common Links

• Growth section
• Growth issues board
• #s_growth in Slack (GitLab internal)
• Growth Performance Indicators
• Growth opportunities
• Growth meetings and agendas
• GitLab values