Growth:Acquisition Group

1. You are here:
2. Engineering
3. Development Department
4. Growth Stage
5. Growth:Acquisition Group

On this page

• Vision
• Mission
• Team Members
  • Stable Counterparts
• How We Work
  • Prioritization
    • Cross-functional Backlog
    • Merged Merge Request Types
    • Flaky Test Issues
  • Workflow
• Common Links

Vision

The Acquisition Group is part of the Growth Stage. We work on connecting our users with our product value.

• I have a question. Who do I ask?

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

Mission

The Growth:Acquisition Group works on product priorities and growth deliverables with our Growth product managers and contributes to Growth initiatives including the Registration Flow and Continuous onboarding.

Team Members

The following people are permanent members of the Growth:Acquisition team:

Person	Role
Kamil Niechajewicz	Fullstack Engineering Manager, Growth:Acquisition and Activation
Doug Stull	Staff Fullstack Engineer, Growth:Acquisition
Roy Liu	Fullstack Engineer Intern, Growth:Acquisition
Ross Byrne	Fullstack Engineer, Growth:Acquisition
Serhii Yarynovskyi	Fullstack Engineer, Growth:Acquisition

Stable Counterparts

We work directly with the following team members in the Growth:Acquisition group:

Person	Role
Gayle Doud	Senior Product Manager, Growth:Acquisition
Sam Awezec	Principal Product Manager, Growth:Acquisition and Activation
Costel Maxim	Senior Security Engineer, Application Security, Plan (Project Management, Product Planning, Certify), Create:Source Code, Growth, Fulfillment:Purchase, Fulfillment:Provision, Fulfillment:Utilization, Systems:Gitaly
Nikhil George	Senior Security Engineer, Application Security, Secure (Static Analysis, Dynamic Analysis, Composition Analysis, Vulnerability Research), Growth (Acquisition, Activation).
Vincy Wilson	Senior Manager, Quality Engineering, Enablement, Fulfillment, Growth, Sec and Data Science
Mariana da Costa Melo	Customer Success Manager, Growth (Commercial EMEA)
Philipp Zapf	Customer Success Manager, Growth (Enterprise EMEA)

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, Engineering, and Quality.

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

Cross-functional Backlog

(Sisense↗) We also track our backlog of issues, including past due security and infradev issues, and total open System Usability Scale (SUS) impacting issues and bugs.

Merged Merge Request Types

(Sisense↗) MR Type labels help us report what we're working on to industry analysts in a way that's consistent across the engineering department. The dashboard below shows the trend of MR Types over time and a list of merged MRs.

Flaky Test Issues

(Sisense↗) Flaky test are problematic for many reasons.

Workflow

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

• We use a shared Kanban workflow board for both groups - Acquisition and Activation for work in the build phase of the product development flow.

• We use refinement threads on issues to discuss our approach and estimate weight of upcoming work.

Common Links

• Growth Stage
• Acquisition issues
• #g_acquisition in Slack (GitLab internal)