Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
E
Experimentation
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • Growth
  • Experimentation
  • Issues
  • #2

Closed
Open
Opened Oct 02, 2020 by Phil Calder@pcalderOwner

Experiment framework - options and analysis - improve, build, buy

High level comparison of three options for improving the experimentation capability at GitLab:

  1. Improve: improve the current framework #3 (moved) &/or #4 (closed)
  2. Dogfood: dogfood GitLab Feature Flag feature #5 (moved)
  3. Buy: purcahse an off the shelf solution for testing

Growth product requirements for experimentation: #1 (closed) define required capabilities for Bucketing, Measuring, Analysis, Data and privacy. Table provides a high level view of whether the solution does - or is expected to - meet the key requirements in the short term. Note that analysis of specific buy options has not been provided.

Time to value is a high level estimate of when the key requirements could be met by each of the three options.

  1. Now - requirements are already met
  2. Short term - likely within 3 months
  3. Medium term 3-6 months
  4. Unknown - definitely longer than 3 months based on what we currently know, more information required
Improve Dogfood Buy
Bucketing ✅ ✅ ✅
Measuring ✅ ✅ ✅
Analysis ❓ ❓ ❓
Data/privacy ✅ ❓ ❓
Time to value Short to Medium term Unknown Unknown
Cost Opex Opex Capex - Unknown
Risk Changing requirements Relies on other product teams priorities Integration, data privacy, time to analyze requirements
Edited Nov 01, 2020 by Phil Calder
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/growth/experimentation#2