Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Effective Remote Teams
Search
Danny Preussler
April 13, 2018
Technology
120
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Effective Remote Teams
Spontaneous presentation at SoCraCan Las Palmas 2018
Danny Preussler
April 13, 2018
More Decks by Danny Preussler
See All by Danny Preussler
Clean Code Revisited in Age of AI (Droidcon USA)
dpreussler
2
52
Testing, how hard can it be? (Droidcon Lisbon 2022)
dpreussler
3
540
Take your Kotlin to the next step, abandon what you’ve learned (in Java)
dpreussler
0
720
The Power of Types, KotlinConf 2019
dpreussler
7
1.5k
Java vs Kotlin
dpreussler
0
610
Property Delegation with Kotlin for Android
dpreussler
1
150
Java vs Kotlin
dpreussler
2
620
To inject or not to inject: Dependency Injection with Kotlin (Droidcon Nairobi)
dpreussler
4
330
TDD on Android
dpreussler
4
420
Other Decks in Technology
See All in Technology
AIに任せた品質は、誰が見立てるのか - AI時代のテストマネジメント
nakanao
3
2.9k
え、こんなに早く改修できるの?──新人エンジニアとスクラムマスターの2人が語る、AI×アジャイル開発の現場
ysasago
2
700
特殊変数大全
dak2
0
120
Railsのように考える: See through the Master
snoozer05
PRO
5
1.3k
エージェントはローカル、検証はMicroVM — Lambda MicroVMsでつくるServerless CI
fujioka6789
3
750
LLMに渡さなかった仕事
nanaism
0
1.4k
俺の仕事は AIに奪われないし、たぶんその BIも要らない
hikaruri
0
540
あけおめLINE 傾向とその対策
nasa9084
0
310
AI de Idea
kawaguti
PRO
2
130
作って終わりじゃないサーバーレス 〜9年運用する大規模EC物流API基盤の設計・運用のリアル〜
zozotech
PRO
0
490
AIエージェントの一手は 誰も見ていない - Falco拡張OSS「Prempti」とeBPFで サーバーレス実行基盤を二層防御する
keitah
0
530
開発投資の期待値を上げるプロダクトロードマップづくり ~プロダクトエンジニアが越境して事業を伸ばす~
kekekenta
1
250
Featured
See All Featured
How to optimise 3,500 product descriptions for ecommerce in one day using ChatGPT
katarinadahlin
PRO
3
3.8k
Self-Hosted WebAssembly Runtime for Runtime-Neutral Checkpoint/Restore in Edge–Cloud Continuum
chikuwait
0
820
Speed Design
sergeychernyshev
33
2.1k
Context Engineering - Making Every Token Count
addyosmani
9
1.2k
The Curious Case for Waylosing
cassininazir
1
540
Mind Mapping
helmedeiros
1
370
Breaking role norms: Why Content Design is so much more than writing copy - Taylor Woolridge
uxyall
1
410
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
12k
Game over? The fight for quality and originality in the time of robots
wayneb77
1
290
Ruling the World: When Life Gets Gamed
codingconduct
0
360
How Fast Is Fast Enough? [PerfNow 2025]
tammyeverts
3
900
Primal Persuasion: How to Engage the Brain for Learning That Lasts
tmiket
0
480
Transcript
Effective Remote Teams @PreusslerBerlin SoCraCan 2018
Our situation, Android team: • 2 in Berlin • 1
in Sczcecin, 2 Lublin, 1 Wroclaw • 1 dev in New York • 1 QA in Minsk • Scrum Master, PO, QA in New York • Later: more devs from Canada, LA, New York
Get to know each other!
Tools • Slack • Customize! • Jira + CI integration
• Screenhero
Asychronous communication • Don’t expect answer • Labels in Github
PR tiny, big, urgent approved, needs_rebase, dont_merge, question, recheck
Have a backup plan • If Slack video chat does
not work, be ready to move to Hangout or Skype. • Be pragmatic and don’t spend too much time in trying to fix the tool.
Feel the pain • If larger team in one spot:
every one needs to work from home once a week!
Tech standups • Daily between 10 and 45min
Face to Face meetings • Try to meet every x
weeks • Give isolated team members a presence in the room! • Remote teams need this investment!
Remember the manifesto • Individuals and interactions over processes and
tools: • Dont rely on specific tool • Be pragmatic • Working software over comprehensive documentation • Don't write specifications that you would not write for a local team.
Timezones • Split morning standups • Document decisions • Don’t
delay what you would not delay without i.e. PRs • Might be hard to follow up on Slack • Split teams • Trust
Have fun http://blog.viacom.tech/2017/04/07/effective-remote-teams/