There are XX team members in the Ops Section.
The following people work as part of the Ops Section but outside a specific product group.
|Tristan Read||Senior Frontend Engineer, Monitor:Monitor|
|Olena HK.||Senior Frontend Engineer, Monitor:Monitor|
|Joanna Shih||Quality Engineering Manager, Ops|
|Sam Goldstein||Director of Engineering, Ops|
|Kenny Johnston||Sr. Director of Product Management, Ops|
|Crystal Poole||Backend Engineering Manager, Monitor:Monitor|
|Peter Leitzen||Senior Backend Engineer, Monitor:Monitor|
|Serena Fang||Backend Engineer, Manage:Access|
|Orit Golowinski||Senior Product Manager, Release|
|Sarah Yasonik||Backend Engineer, Monitor:Monitor|
|Chrissie Buchanan||Content Marketing Manager, Ops|
|Sarah Waldner||Senior Product Manager, Monitor:Monitor|
|Jackie Porter||Group Manager, Product, Verify|
|Vitali Tatarintev||Senior Backend Engineer, Monitor:Monitor|
|Sean Arnold||Backend Engineer, Monitor:Monitor|
|Lorie Whitaker||Staff UX Researcher, Verify, Package, and Release|
|Andrej Kiripolský||UX Researcher, Configure, Monitor, Enablement|
|Saumya Upadhyaya||Sr Product Marketing Manager|
|David O'Regan||Senior Frontend Engineer, Monitor:Monitor|
|Kevin Chu||Group Manager of Product Management, Configure, Monitor, Release|
Here are the individuals who work as part of one of the Ops Section groups.
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.
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:
Every other Tuesday at 9am Pacific a product group from the Ops Section hosts a 30 minute, public, synchronous and live-streamed AMA.
The intent of these AMAs is to:
No content prep is required. We will host an AMA with an agenda that has a single link to the groups handbook page followed by questions from attendees.
The schedule for upcoming Ops Section Product Group AMAs is:
We'll measure the succes of this expiremental meeting based on the number of attendees and number of questions asked from outside the group during the AMAs.
Every Monday at 9:00am Pacific, the Managers in Ops Section Wide roles for the Development, UX, Quality and Product Management Departments are invited to attend the Ops Section Manager Meeting. The invite is in the Ops Section calendar - GitLab internal.
The intent of this meeting is to:
The agenda for the meeting is here - GitLab internal.
On a monthly basis we discuss each department's (Product, Development, Quality, UX) performance indicators with an eye towards enabling department performance improvements by improving how we interact across departments. The content and scheduling for these monthly reviews are:
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.
Every Tuesday alternating weekly between European Availability (5:30 AM Pacific) and Pacific Availability (11:30 AM Pacific) we hold an Ops Section PM Meeting. Any Gitlab team member is invited to attend, just ask for the invite in the #ops-section.
The intent of this meeting is to:
In order to satisfy the above intent, we:
This section documents experimental PM process used in the Ops Section that isn't incorporated into the Product Process handbook which covers all sections.
The intent is to share more competitive understanding amongst Ops Section Product managers.
Ops Section PMs maintain a personal Epic for their future competitive analysis issues and record walk-through style videos of their top priority assessment once per quarter at any time. Because of the competitive nature of this assessment the issues are left public but the videos are posted privately to YouTube. They will post the videos and issues to the
#ops-section slack channel and ping
@gl-ops-section-pms on the issues when completed.
We'll consider this experiment a success if it encourages collaboration and understanding amongst PMs. After one quarter, we'll measure success by amount of engagement by Ops Section PMs in the issues and slack posts in the form of comments.
A list of important milestones achieved as part of our Ops Section Product Performance indicators.