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
69
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
730
The Power of Types, KotlinConf 2019
dpreussler
7
1.5k
Java vs Kotlin
dpreussler
0
620
Property Delegation with Kotlin for Android
dpreussler
1
160
Java vs Kotlin
dpreussler
2
630
To inject or not to inject: Dependency Injection with Kotlin (Droidcon Nairobi)
dpreussler
4
350
TDD on Android
dpreussler
4
430
Other Decks in Technology
See All in Technology
Codex を使った障害対応机上演習の実際
orgachem
PRO
0
170
M5Stackで作る BLEマウス GPSログの世界
tomokusaba
PRO
0
450
フィンテック養成勉強会#68
finengine
0
180
NDIでApple Vision Proにリアルタイム映像送信
jyouryuusui
0
140
Kiro Crewで「みのるん式」仕事術やってみた
minorun365
PRO
3
960
~最速でビジネスインパクトを創出する~ Sansanのデータ基盤と活用事例
sansantech
PRO
0
110
Metadata - Section 1: HTML Basics
mohab1
0
140
Turning Repos into the Product Second Brain with an LLM Wiki
linedevth
0
120
Post AI時代のリファクタリング実践記 / Refactoring in the post AI era
kaminashi
1
310
What Is JetBrains Air
x5gtrn
PRO
0
130
AIカンパニーへの転換を支えた、エンジニアの仕事の再定義
kworkdev
PRO
2
1.4k
その Valkey 使いこなしていますか?
onk
PRO
5
1.7k
Featured
See All Featured
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.6k
The AI Revolution Will Not Be Monopolized: How open-source beats economies of scale, even for LLMs
inesmontani
PRO
3
3.8k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
7k
Why You Should Never Use an ORM
jnunemaker
PRO
61
10k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
The Invisible Side of Design
smashingmag
301
52k
Agile Leadership in an Agile Organization
kimpetersen
PRO
0
290
brightonSEO & MeasureFest 2025 - Winning Strategies for Black Friday CRO & PPC - Christian Goodrich
cargoodrich
3
870
Speed Design
sergeychernyshev
33
2.2k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
360
31k
GraphQLとの向き合い方2022年版
quramy
50
15k
Raft: Consensus for Rubyists
vanstee
142
7.8k
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/