The COVID-19 pandemic means many engineering teams have made the shift from working under one roof to working remotely. For some companies that change could be permanent. At GitLab, this is how we've always worked. This round-up consolidates some of the top insights from leaders in the all-remote space, and also includes a number of best practices engineering teams of all sizes can replicate.
1. Embrace a remote-first culture
Two HubSpot team members joined GitLab Virtual Commit, our user conference, to talk about how discarding a remote-friendly culture in favor of a remote-first culture helped build a more inclusive workplace. Watch the video below to learn more about HubSpot's move to remote.
2. Be a thoughtful manager
Let’s be honest, managing an all-remote, globally distributed team is different from managing when you’re all in the office. Engineering managers at GitLab share their tips for being a thoughtful and effective team leader – from a distance.
3. Cut down on Zoom fatigue
Every engineering manager we talked to suggested cutting down on the number of meetings and make the pivot to asynchronous work. In this session from GitLab Virtual Commit, Luke Thomas with Friday.app explains how to make the transition.
Need to cut down on Zoom fatigue but still require weekly discussions? The GitLab Support team got creative and turned their weekly department meeting into a podcast. Now, team members can catch up on the latest developments on their own time and off-camera.
4. Some advice on engineering together while apart
Collaboration on an all-remote team takes practice. GitLab team members we interviewed suggest embracing asynchronous communication, share suggestions for onboarding new engineers, and more.
Watch this video from GitLab Virtual Commit to dive deeper into best practices for remote onboarding engineers.
Pair programming is great for problem solving tricky code, but when you work on an all-remote team, you can’t just pull up a chair and get it done. Our remote pairing enthusiasts share four tips on how to make it happen.
When it comes to pairs, nothing goes together better than Agile software development and all-remote work practices. GitLab (the product) is built on Agile principles and facilitates remote collaboration while GitLab (the company) is made up of a globally distributed workforce.
5. Always know your results
GitLab is a results-driven company, meaning we care about what you achieve than how you achieve it. To measure your engineering productivity, we suggest calculating your merge request (MR) rate. Read on to learn why this metric matters.
Bonus: Learn more about remote work
We have a number of resources to help engineering teams up-level their all-remote work. Here are a few places to start:
- How to manage a remote team: Join nearly 17,000 people in taking the Coursera class we created to help newly remote teams. Learn how to manage a remote team (for free).
- Get the GitLab guide to all-remote work: We round-up lots of remote work tips in our all-remote section of the GitLab Handbook.
- Check out more resources on our all-remote hub, including our 2021 Remote Playbook, the Remote Manifesto, and more.
“Top @GitLab stories on engineering while remote” – Sara Kassabian
Click to tweet
Free eBook: The GitLab Remote Playbook
Learn to stabilize your work-from-home team and dive deep on topics including asynchronous workflows, meetings, informal communication, and management.Download now