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
130
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
56
Testing, how hard can it be? (Droidcon Lisbon 2022)
dpreussler
3
550
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
630
To inject or not to inject: Dependency Injection with Kotlin (Droidcon Nairobi)
dpreussler
4
340
TDD on Android
dpreussler
4
420
Other Decks in Technology
See All in Technology
[2026 Oracle Technical Deep Dive] OCI AI Resilience -OCIのセキュリティ対策機能をきちんと使いこなす- (2026年9月17日開催)
oracle4engineer
PRO
0
140
IoTデバイスを繋げるプロトコルMatterをAndroidで使用する方法
harutiro
0
120
Claude Code本は、どのように執筆チームで書かれたか
oikon48
0
110
ビジネスを止めない技術的負債の返済のための戦略とその手法 - 技術的負債と向き合う / Complexity and Simplicity
soudai
PRO
3
640
20260930_Gemma4_Hands-on
tsho
0
230
事業活動を AI Ready にする攻めと守りのデータエンジニアリング / data-engineering-for-ai-ready-business
pei0804
3
690
ミイダス株式会社 テックチームのご紹介 / MIIDAS Tech Team
miidas
0
160
Snapshot Testing in Practice: Predictable and Reliable SwiftUI Views
fespinoza
0
130
AI Made Us Faster at Solving the Wrong Problems
marceloancelmo
0
170
カンファレンスに参加した後の浮遊感とセルフケア
pauli
0
310
3つのアプローチで目指す チームを強くするAI駆動開発
thkt
0
120
並行性の問題を防げ!実践トランザクション入門
occhi
0
280
Featured
See All Featured
Odyssey Design
rkendrick25
PRO
2
860
Google's AI Overviews - The New Search
badams
0
1.6k
The Cost Of JavaScript in 2023
addyosmani
55
10k
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
2
320
The Cult of Friendly URLs
andyhume
79
7k
Balancing Empowerment & Direction
lara
6
1.3k
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
6
1.2k
Digital Ethics as a Driver of Design Innovation
axbom
PRO
1
450
Measuring Dark Social's Impact On Conversion and Attribution
stephenakadiri
2
300
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
1
420
We Analyzed 250 Million AI Search Results: Here's What I Found
joshbly
2
2k
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/