Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Building and scaling effective distributed teams
Lindsay Holmwood
November 27, 2017
Education
4
150
Building and scaling effective distributed teams
Lindsay Holmwood
November 27, 2017
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Footguns and factorisation: how to make users of your cryptographic library successful
auxesis
0
1.1k
Levelling up database security by thinking in APIs
auxesis
0
63
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
45
Microservices are an antipattern
auxesis
0
140
Mirrors, networks, and boundaries
auxesis
0
62
Managing remotely, while remotely managing
auxesis
13
3.5k
Testing Conway’s Law in open source communities
auxesis
6
370
Mirror, mirror, on the wall
auxesis
2
240
Mixing oil and water: devops in an ITSM world
auxesis
1
380
Other Decks in Education
See All in Education
Gordon Parks - Segregation Series - complete
oripsolob
0
1.1k
World War I and the Red Scare
oripsolob
0
220
フォトディレクトリってなに?〜みんなで写真をアップしてみよう!〜|WordPress Mega Meetup Japan 2022 Spring
shuseitoda
0
130
20220412_情報社会論 #01
furuhashilab
0
160
Should international development work with big tech – a means-ends discussion: Contra arguments
dominic_orr
1
130
鯛焼きの是非 その限界について
superkinoko
0
1.2k
ポストSDGsのサステナビリティとウェルビーイング ― ESG投資および非財務情報法の開示/Sustainability_well-being
tkimura12
0
170
英語授業研究学会・関東支部 第28回春季研究大会(山﨑資料)
hirokiyamazaki
0
250
新卒が半年で AWS 認定資格11冠取得した勉強記
dohara
0
130
Padlet opetuksessa
matleenalaakso
3
5.2k
Visualisation Techniques - Lecture 8 - Information Visualisation (4019538FNR)
signer
PRO
0
800
WindowsコンテナDojo 全体スケジュールのご案内
utsukibm
0
330
Featured
See All Featured
How STYLIGHT went responsive
nonsquared
85
3.9k
Fontdeck: Realign not Redesign
paulrobertlloyd
73
4.1k
Why You Should Never Use an ORM
jnunemaker
PRO
47
5.5k
Typedesign – Prime Four
hannesfritz
33
1.3k
Navigating Team Friction
lara
175
11k
Designing the Hi-DPI Web
ddemaree
272
32k
Code Reviewing Like a Champion
maltzj
506
37k
GraphQLとの向き合い方2022年版
quramy
16
8k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
655
120k
Producing Creativity
orderedlist
PRO
333
37k
Designing Experiences People Love
moore
130
22k
The World Runs on Bad Software
bkeepers
PRO
56
5.2k
Transcript
Building and scaling effective distributed teams Lindsay Holmwood
About me Worked in and lead distributed software engineering teams
for 7 years
About me Lead teams with follow-the-sun coverage
About me Currently at Envato leading distributed team of 15
The journey 0. Fundamentals 1. Starting out 2. Growing the
team 3. Scaling to the whole org
Inclusion Practices Technology Sponsorship
No management buy in? Don’t even bother.
Starting out
Inclusion Practices Technology Sponsorship
Regular face to face catchups. Ideal: once a quarter
Regular face to face catchups. Likely: once a year
Establish rituals
Multiple internet connections Dongle with lots of data
Multiple internet connections Don’t skimp on quality (fast upload a
must)
Multiple internet connections Move to areas with NBN
Multiple internet connections Have backup equipment
Instant messaging Non-negotiable, primary comms method
Instant messaging Your lifeline to your team.
Instant messaging Scheduled do not disturb time
Instant messaging Announce start/stop
Ceremonies: Daily standup Rotate the facilitation responsibility
Ceremonies: Retrospectives Discuss and refactor practices
Leadership participation Show endorsement. Build empathy.
Growing the team
Inclusion Practices Technology Sponsorship
The basics Even more important!
The basics Bring in coaches to observe and facilitate.
Hack: Greet everyone to check
Hack: Ask questions in the negative “Does anyone disagree?” not
“Do we all agree?”
Team design: Time zone coverage How many time zones? How
much time zone overlap?
Team design: Time zone coverage Add people in new time
zones in pairs.
Team design: Time zone coverage Beginning & end of day
standups.
Team design: Time zone coverage Record crucial meetings.
Team design: Antipattern: Forcing everyone to work at exactly the
same time
Team design: Antipattern: Communication in physical spaces that excludes remoters
Team design: Antipattern: Activities that exclude remoters (use of whiteboards)
(in-person icebreakers)
Google Quick Draw
Team design: Defining question How would this decision make me
feel if I was working from home?
Leadership participation Show endorsement. Build empathy.
Scaling to the whole org
Inclusion Practices Technology Sponsorship
What does it take to make distributed teams a first
class citizen in the organisation?
The executive and management working remotely at least 2 days
a week.
Guilds Share lessons learnt with other teams
Feedback loops Keep refactoring your ways of working.
Feedback loops “What got us here won’t get us there."
Thank you! (and questions?)