The Ops Sub-department is composed of development teams working on Verify, Package, Release, Configure, and Monitor features of GitLab DevOps Platform.
The following teams comprise the sub-department:
Product direction can be found on the Ops Section Product Direction handbook page.
(Sisense↗) We also track our backlog of issues, including past due security and infradev issues, and total open SUS-impacting issues and bugs.
(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.
Ops Sub-department regular meetings
|Meeting||Invitees (open to anyone)||DRI||Purpose||Cadence (duration)||Notes|
|Staff||EMs, Staff+ Engineers, People Business Partner||Sam Goldstein||discuss group initiatives and announcements||weekly (async)||We are experimenting with conducting this meeting async.|
|Skip-Level||Skip level EMs and ICs + People Business Partner||Sam Goldstein||roundtable discussion / opportunity to build connections across the group||monthly|
|Continuous Integration staff||Sr. Manager Verify + Managers||Cheryl Li||discuss group initiatives and announcements||bi-weekly (25 mins)|
|Continuous Delivery staff||Sr. Manager Continuous Delivery + Managers||Dan Croft||discuss group initiatives and announcements||bi-weekly (25 min / 50 mins)||25 mins one week, 50 the next. People looking to learn about management can attend the 25 minute meeting.|
|Ops Engineering Showcase (formerly demos)||All engineering team members||Mark Nuzzo||Engineering-focused showcase of code and achievements||monthly (50 mins)||Mark Nuzzo coordinates the region showcases for each month|
|Ops promotion reviews||Director, Sr. Managers, Managers||Sam Goldstein||Discussion and calibration on promotion documents for the quarter||Quarterly||We'll discuss an decide if we want to do this monthly and whether we want a post calibration meeting as well.|
|Observability Weekly Sync||Product, Development, and Community leads for Observability integration and launch||Sam Goldstein||Efficiently communicate weekly activities across functions (e.g. Product, Development, Community Relations). Create clear understanding of what we intend to accomplish this week.||Weekly (25 min)||Agenda|
|Ops Hiring Manager Sync||Hiring managers||Sam Goldstein||Support hiring manager efforts. Updates and tracking of hiring activity. Tricks and tips for effective hiring.||Weekly (25 min)||Agenda|
The weekly Ops Staff meeting follows this async format:
Each month there are two showcase sessions organized for both APAC and AMER/EMEA timezones. These sessions are organized as opportunities for engineers to show off the things they've been working on. These sessions are each organized via a planning issue linked in the epic below. Sessions are recorded and uploaded to YouTube as well.
|2022||January||Video||No showcases||Jobs UI Refactor|
Planning processes followed by teams in the Sub-department:
Ops Managers, Sr. Managers, and Directors meet in the last month of each quarter to:
We have limited capacity in the recruiting team so hiring managers are experimenting with the Ops Hiring process. We also hold a weekly hiring manager sync meeting (see Meetings section).
|5 weeks before||OKR kickoff. Quick sync to review schedule and expectations. Director Ops and direct reports.|
|4 weeks before||Next Quarter OKR Planning - Initial Review Session - Director, SEMs, EMs - Review CEO, CTO, CProjO and VP Development OKR drafts|
|3 weeks before||Next Quarter OKR Planning - 50 minute Director/SEM OKR review meeting. Ops Directors+, Sr. EMs, Group PMs propose OKRs for their groups in Working Drafts (existing document (internal))|
|2 weeks before||Next Quarter OKR Planning - 50 minute SEM/EM meeting for Verify and CD compartment. EMs propose OKRs for their groups via issues linked from review meeting doc.|
|1 week before||OKRs are moved into Ally. Directors, SEMs, EMs document how to achieve following guidance in https://about.gitlab.com/company/okrs/#documenting-how-to-achieve|
|1 week before||OKRs and how to achieve docs are shared by DRIs in #doe-ops and other appropriate slack channels.|
|1st week of quarter||Ops Sub-Dept OKR AMA. 25 minute kickoff meeting to discuss OKRs and answer questions.|
from x to y).
**Good** - Things that went well... **Bad** - Things that didn't go so well... **Try** - What might you do differently next time?
We have a policy in Ops to keep status updates out of meetings. Instead of reporting on status in meetings, Directors, Senior Engineering Managers, Engineering Managers and Principal Engineers provide weekly async updates. The content of these updates may vary by individual and role but generally cover:
~OpsSection::Weekly-Update labelare summarized in weekly issues in the Ops Status Updates project.
We are piloting a process to make coordinating with the Support team on customer escalations more efficient.
See How to Use GitLab.com to Formally Request Help from the GitLab Ops Development Team for process details.