Extreme Remoting
summary
A team developed a nine-month remote workflow with a 6–7 hour time difference (two-hour daily overlap) between Taiwan and Warsaw. They solved coordination issues by enforcing coding standards, visible daily task boards and retrospectives, using Slack and Hangouts (WebEx for clients), plus VPN and QoS for video; they rely on pair programming, frequent short video check-ins and explicit status updates to replace corridor communication and improve handoffs and discipline.
AI-written summary · about
chapters (8)
- 0:00Extreme remote intro
- 3:14Taiwan work setup
- 8:00Global team communication
- 15:37Performance challenges
- 22:28Time zone gains and pitfalls
- 28:08Team and process changes
- 36:30Remote standards and feedback
- 42:00Summary and tips
related talks
35mPair Programming from 2,000 km Away: Strategies for Distributed Agile Teams
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
40mBeing a remote developer
27mRemote Team Management
42mSustaining Remote – First Teams.
52mRemote Working Approaches That Worked (And Some That Didn’t)
57mRemote Doesn’t Mean Distant - Managing Teams Effectively from Different Geographies
59mRemote, but Unstoppable: Unlocking the Power of a Fully Distributed Studio