Working groups rollup updates

There are a lot of working groups in Engineering and others as well that the CTO needs to be aware of.

The ultimate goal is to provide a good way to do rollup updates to the CTO. Think high-level e-group appropriate updates. This is also helpful for anyone outside the group who is interested in knowing what’s happening with the WG and where they’re at.

Need to find a way to get regular (weekly) rollup updates. Each group should have at minimum:

1. link to handbook page
2. Overall status
3. Brief update from latest meeting (and date)

Note: possibly other things I haven’t thought of, for ideas, we can look at the Free SaaS User Efficiency epic

Proposal

Short term

1. Looking at a doc similar to top initiatives quarterly update, but more frequent.
2. Alternative: (Recommended) Status quo: Have VPs bubble up anything that requires CTO attention via weekly Should Know doc & Slack pings, until we get a long(er) term solution.
3. Separately: Have WGs update handbook page, make sure up to date, and have required info, including:
   • Goal
   • Exit criteria
   • Anticipated date to retire
   • Where to see overview/health/status
   • Location of updates
   • Location of milestones/significant updates (if applicable)
   • Comms/updates channels aside from Slack, sync meetings, GitLab epic (if applicable)

Decision: 2 & 3 status quo, update handbook pages.

Long term

Key: align with company-level decisions, being lead by CoST.

1. Similar to top-initiatives.
2. In a subgroup, possibly in gitlab-com/working-groups. Note: Recommend having a shared top-level group with wherever OKRs are located in Q1.
3. Should follow the guidance on the Leading cross-functionally page (MR that introduced it) and Working groups page.
4. Waiting on: @mushakov will create documentation on the current “recommended” way to do these.
5. Issue to solve in product: gitlab-org/gitlab#384192 (closed)

To do

1. Gather info on how WGs are communicating, especially to e-group. | #66 (comment 1188593641)
2. Gather info on how using GitLab has gone for top-initiatives. | #66 (comment 1191792895)
3. Update WG handbook page with making Communications explicit. | www-gitlab-com!113458 (comment 1191764713)
4. Confirm which working groups are still active
5. Discuss with CTO on whether to move ahead with short term proposals
6. Update HB pages: update-to-date and include comms for active WGs not completing this quarter
7. Create issue for long term solution

List: Working group - sponsor

1. API Vision - Senior Director of Dev section, Tim Zallmann | www-gitlab-com!116851
2. ClickHouse Datastore - Development, Christopher Lefelhocz | www-gitlab-com!116855
3. Cross-Functional Prioritization - CTO | Async | www-gitlab-com!116849
4. Demo & Test data - Quality, Mek Stittri | www-gitlab-com!116654
5. Disaster Recovery - Infrastructure, Steve Loyd | www-gitlab-com!117121
6. Engineering Internship - Development, Christopher Lefelhocz | Looks up to date, ending 2023-01-31
7. [-] FedRAMP Execution - Product, David DeSanto (Development involvement) | Top initiatives updates, quarterly to e-group
8. Frontend Observability - Senior Director of Dev section, Tim Zallmann | www-gitlab-com!117122
9. Kubernetes Migration - Infrastructure, Steve Loyd | www-gitlab-com!117120
10. [-] Maintainership - Development, Christopher Lefelhocz | Note: wrapping up
11. Next Architecture - Development, Christopher Lefelhocz | Looks up to date, ending 2023-01-31
12. Rate Limit Architecture - Development, Christopher Lefelhocz
13. webpack - Development, Christopher Lefelhocz