The goal is to support the members of these groups in connecting at a personal level,
not to check in on people's progress or replace any existing processes to communicate
status or ask for help, and the questions are written with that in mind:
What did you do outside of work since we last spoke?
What are you planning to do today?
Is anything blocking your progress or productivity?
Each week, the Engineering Manager (EM) creates a short video communicating both GitLab and Team information. The Weekly Update is accompanied by a presentation and a Google Document to capture asynchronous questions.
To maintain our service level for GitLab.com customers, GitLab team members serve as On-call Engineers. In general, Engineers select shifts that are convenient for them. Each shift spans four hours.
Each week, the Product Manager, the Create:Editor Frontend and Create:Editor Backend Teams conduct a synchronous meeting to share progress and discuss issues. These meetings are recorded and can be viewed asynchronously. A Google Doc is also available to ask questions or comment synchronous or asynchronously. Conducting meetings using this format allows all team members to participate in knowledge sharing.
Calendars are used to communicate important events:
Communicate your daily work schedule. Setting your daily work hours in Google Calendar helps communicate your availability to team members across timezones. This is important when scheduling synchronous meetings across timezones. (Making your calendar public is recommended but it is not required.)
Communicate activities / events you plan on attending
Communicate feature related events (Deep Dives, Demonstrations etc.)
Communicate weekly group meetings (all stable counterparts are invited)
Sprint Planning Calendar
communicate deadlines for Sprint Planning activities