Functional Group Updates

Format

Functional Group Updates are regular updates from a group at GitLab.

  1. We'll use Zoom for now, will switch to YouTube Live later.
  2. Use this slide deck as template to your presentation. Presentations should allow editing (preferred) or commenting from everyone at GitLab.
  3. Make sure to add the link of the presentation to the GitLab Availability Calendar invite at least 24 hours before the call takes place. This allows team members to see the presentation, to click links, have random access during the presentation, and to quickly scan the presentation if they missed it. Please also add who the speaker will be to the presentation and the invite. To do this, go to the GitLab availability calendar, find the event, click on more details and edit the description. People Ops will ping the appropriate team member at the 24-hour mark if the event hasn't been updated yet.
  4. Reduce distractions for yourself and the attendees by:
    • having the presentation open in its own new browser window, and only sharing that window in Zoom.
    • switching off notifications (from Slack, email, etc.). On Mac, in the notification center in the upper right hand corner, click on Notifications, select Do Not Disturb (sometimes you need to scroll up to see the option).
  5. All calls are published on YouTube, with the exception of Finance, Sales, Security, Channel, and Partnerships. Every call is reviewed prior to publishing to make sure no internal information is shared externally.
  6. Right now everyone at GitLab the company is invited to each call, we'll invite the wider community later.
  7. Attendance is optional.
  8. The update is also announced on and the recording linked from our team call agenda.
  9. Tone should be informal, like explain to a friend what happened in the group last month, it shouldn't require a lot of presentation.
  10. You can invite someone in the team to give the update, it doesn't need to be the team lead, but the team lead is responsible that it is given.
  11. Calls are 5 times a week 30 minutes before the team call, 8:00 to 8:25am Pacific.
  12. Calls should be a maximum of 15 minutes (aim for 10 minutes) for the presentation so
    • Please focus on the discussion during the call, not the slide content. Everyone is able to read the slide content so the value is in the conversation and questions. Leave time for questions, the presentation is there as warmup to get questions, questions will have the things people care about that you overlooked, they are the most important part of the FGU.
    • People will watch less FGU's if is a bigger time commitment, it is great it they end with time to spare.
    • Save time by writing information on the slides, people can read faster than write, many people will not be able to watch the FGU either live or recorded but can read trough the slides.
    • It is fine if a call ends after 5 or 10 minutes.
    • Do not read the contents on your slides, we already read what is on them before you mention it.
    • People need to be on time for the team call, end no later than :29 and preferably at :25.
    • If there are more questions invite them via a chat channel you mention.
  13. Calls are scheduled by an EA.
  14. If you need to reschedule, please switch your presenting day with another FGU presenter. If you've agreed to switch do the following:
    • Go to the GitLab Availabiltiy calendar invite
    • Update the date of your and the other invite to be switched
    • Choose to send an update to the invitees
    • If prompted with the questions to update 1 or all events, choose to only update this event
  15. Every group with 5 people or more presents.
  16. The call is recorded automatically, and all calls are transferred every hour to a Google Drive folder called "GitLab Videos", which is accessible to all users with a GitLab.com e-mail account.
  17. Video recordings will be published on our blog so contributors, users, and customers can see it. We're aiming to publish a blog post once a week of that weeks' recordings with the matching slides in one go.

Template for the blog post

For instructions on how to create a blog post, please see our Blog Handbook.

Please copy the code block below and paste it into a blog post with the file name yyyy-mm-dd-functional-group-updates.html.md.

---
title: "GitLab's Functional Group Updates - MMM DD-DD" # replace "MMM" with the current month, and "DD-DD" with the date range
author: Name Surname
author_gitlab: gitlab.com-username
author_twitter: twitter-username
categories: Functional Group Updates
image_title: '/images/blogimages/functional-group-update-blog-cover.jpg'
description: "The Functional Groups at GitLab give an update on what they've been working on"
---

<!-- beginning of the intro - leave it as is -->

Every day from Monday to Thursday, right before our [GitLab Team call](https://about.gitlab.com/handbook/#team-call), a different Functional Group gives an [update](https://about.gitlab.com/handbook/people-operations/functional-group-updates/) to our team.

The format of these calls is simple and short where attendees have access to the presentation content and presenters can either give a quick presentation or jump straight into the agenda and answering questions.

<!-- more -->

## Recordings

All of the updates are recorded using [Zoom](https://zoom.us) at the time of the call. All the recordings will be uploaded to our YouTube account and made public, with the exception of the Sales and Finance updates.

<!-- end of the intro -->

<!-- beginning of the FG block - repeat as many times as necessary (copy and paste the entire block) -->

----

### XXX Team

[Presentation slides](link-to-slides-deck)

<figure class="video_container">
  <iframe src="https://www.youtube.com/embed/8vJBc8MJihE" frameborder="0" allowfullscreen="true"> </iframe>
</figure>

<!-- end of the FG block -->

<!-- beginning of the FG block - repeat as many times as necessary (copy and paste the entire block) -->

----

### XXX Team

[Presentation slides](link-to-slides-deck)

<figure class="video_container">
  <iframe src="https://www.youtube.com/embed/8vJBc8MJihE" frameborder="0" allowfullscreen="true"> </iframe>
</figure>

<!-- end of the FG block -->

----

Questions? Leave a comment below or tweet [@GitLab](https://twitter.com/gitlab)! Would you like to join us? Check out our [job openings](https://about.gitlab.com/jobs/)!

Uploading and Editing the Videos

Functional Group Update XXX-Team Date

Presentation - https://example.com [Input your presentation's URL and check if its set to view only for anyone with the link if using Google Slides]

Try GitLab EE FREE for 30 days, no credit card required - https://goo.gl/JdznoY

Want to know more about our free GitLab.com? https://goo.gl/Uol8bl

GitLab License FAQ - https://goo.gl/hZAsYF

Questions?? - https://goo.gl/i7KzQ8

Schedule

There is a rotating schedule:

Week 1:

Week 2:

Week 3:

Week 4:

Week 5:

Agenda

A possible agenda for the call is:

  1. Accomplishments
  2. Concerns
  3. Stalled/need help
  4. Plans
  5. Questions in chat