Asynchronous Work and Remote Teams

This desk is part of the attendee preparation for our workshop Leading Engineering Teams For New Managers.

It's the context for Day 2: Asynchronous Work and Remote Teams. For the video and transcript to go with these slides, check out the resources page on our site.

Transcript

1. Asynchronous work and remote teams
2. If anyone is remote...
3. You are a distributed team
4. Everyone could be remote
5. You are always a distributed team
6. How
7. Focus on communication
8. Asynchronous communication channels • Stop expecting immediate responses • Public, by default • Permanent, by default
9. Policy by Pull Request • Discussions are public • Decisions are transparent • Everyone is encouraged to contribute
10. Regular retrospectives • Concentrate on problems and solutions rather than people • Address issues early • Keep conversations transparent
11. Remote pairing • tmux • Tuple
12. I write down all the things I did wrong so someone else doesn't have to
13. Documentation • One central source of truth • Everybody writes their own documentation • Leave every project better than you found it
14. Internal blogging • Today I Learned • Case studies • Weekly project reports • One weird trick...
15. The personal stuff
16. Keep track of your people • Are they okay? • Are they productive? • Are they communicative?
17. Create opportunities for interaction • Demo sessions • Social sessions • Buy them lunch • Catchup roulette
18. Key points • You're already a distributed team, make sure you act like one • Asynchronous work is about communication • Rituals help