Analytics Section

Maintained by:

What we cover

Who we are

Product Groups

Here are the individuals who work as part of one of the Analytics Section groups.

Analytics Instrumentation

Analytics Instrumentation	PM	UX	EM	FEM	FE	BE	Total
Names	Tanuja Jayarama Raju		Sebastian Rehm			Ankit Panchal, Sebastian Rehm, Jonas Larsen, Michał Wielich, Niko Belokolodov, Piotr Skorupa, Sarah Yasonik	N/A
Count	1	0	1	0	0	7	9

Product Analytics

Product Analytics	PM	UX	EM	FEM	FE	BE	Total
Names	James Heimbuck	TBD	Dennis Tang				N/A
Count	1	1	1	0	0	0	3

Observability

Observability	PM	UX	EM	FEM	FE	BE	Total
Names	Sacha Guyon		Nicholas Klick	Nicholas Klick			N/A
Count	1	0	1	1	0	0	3

Section structure

The section is covered by groups from teams across two primary departments, Engineering and Product. Teams and team members from those departments have their own handbook pages linked below.

Engineering
- Development
  - Analytics Instrumentation
  - Product Analytics
- UX
- Quality
Product
- TBD

Investment Allocation

The product groups within the Analytics Section are outlined in the product categories page.

The product department determines our investment within the section by allocating headcount for development team members to product groups. While doing so we adhere to the following principles:

All product groups will maintain at least a 1:1:1 ratio between three primary DRIs - Product Managers, Product Designers and Engineering Managers.
We don't currently maintain 1:1:1:1 ratio for the additional Software Engineer in Test (SET) DRI but desire to have singular stable-counterparts between SETs and product groups.
We will strive to maintain at least 6 developers (FE + BE) in each product group

SaaS Performance Indicators

TBD

Analytics Stack ownership

The Analytics Stack drives the functionality required to operate Product Analytics features within GitLab.

The Analytics Stack is currently composed of the following functionality:

Event ingestion: Jitsu, to be replaced by Snowplow
Data storage: Clickhouse
Data querying: Cube

An ownership model is explicitly called out as different groups within the Analytics Section are responsible for different pieces of functionality in the Analytics Stack:

Functionality	Owner	Key Stakeholder
Event ingestion	Analytics Instrumentation	Product Analytics
Data storage	Product Analytics	Analytics Instrumentation
Data querying	Product Analytics	Analytics Instrumentation

With this model, Owners are required to notify Key Stakeholders of significant changes to any Functionality, given that there may be impact to other pieces of Functionality working upstream/downstream.

Meetings

TBD

Analytics Section Manager Meetings

TBD

Async Meeting

TBD

Function Based Performance Indicators (PI) Review

TBD

5x5s

In order to satisfy intent #1 - we'll start the meeting series by doing a weekly rotation of 5x5s - five minute presentations on five slides introducing yourself to the rest of the team.

Analytics Section Retrospective

TBD

Intent

The intent of the Section Retrospective Summary meetings is to:

Share reflections, lessons learned and best practices across stages and groups
Serve as a communal forum to solve broad in scope problems or persistent blockers
Share and celebrate accomplishments to give visibility into what other stages and groups are working on

Expectations

It's expected that engineering managers, engineers, and product managers contribute to the document sharing their stage reflections, lessons learned, and best practices in how their teams operate and how they perform retrospectives. Sharing these reflections, lessons learned, and best practices in the form of group handbook page content is preferred.

Moderators

Each Section Retrospective is led by a team member from the group. Any Analytics team members can volunteer as moderator by adding their name to the table below:

Milestone	Moderator	Issue link
15.2
15.3
15.4
15.5
15.6
15.7
15.8
15.9
15.10