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
50
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
作り直せるコードは迅速に 作り直せないDBは慎重に - AI時代のプロダクトエンジニアが「判断の不可逆性」で開発速度を変える話
kinosuke01
0
300
AI活用の現在地、 ちゃんと見えてますか?/XPfest-2026
visional_engineering_and_design
0
180
From Vanilla Kubernetes to a Batteries-Included Platform: Developer Experience at 1,300+ Clusters
yosshi_
0
680
Snowflakeで実現する全社横断の顧客の声(VOC)分析・活用基盤@Snowflake World Tour Tokyo 2026
yuto16
0
160
Gitは怖い?共有ワークスペースから始めるSnowflakeチーム開発
coco_se
0
110
株式会社シーエーシー エンジニア向け会社紹介資料
cac
0
57k
2026/09/10 Spring Bootから Jakarta EE/MicroProfileへの移行
megascus
0
310
研究開発部の紹介 / Sansan R&D Profile
sansan33
PRO
4
25k
Snowflakeのコスト最適化を支えるアーキテクチャ設計
ktatsuya
1
1.4k
synctest時代のhttptest Go 1.27で変わるHTTPサーバテストの裏側 / go conference2026 synctest and httptest
budougumi0617
1
2.6k
AI時代に顧客へ最速で価値を 届けるための試行錯誤 〜「AI × マネジメント」領域におけるmentoのケース〜
posterkeisuke
0
110
Webとヘルスデータ
yukukotani
1
370
Featured
See All Featured
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
133
19k
The Pragmatic Product Professional
lauravandoore
37
7.4k
Java REST API Framework Comparison - PWX 2021
mraible
34
9.7k
Writing Fast Ruby
sferik
630
63k
Applied NLP in the Age of Generative AI
inesmontani
PRO
4
2.4k
Fashionably flexible responsive web design (full day workshop)
malarkey
408
67k
Groundhog Day: Seeking Process in Gaming for Health
codingconduct
0
340
The Invisible Side of Design
smashingmag
301
52k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
500
The Curious Case for Waylosing
cassininazir
1
500
Paper Plane
katiecoart
PRO
3
53k
Dominate Local Search Results - an insider guide to GBP, reviews, and Local SEO
greggifford
PRO
0
330
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/