Distributed Teams
summary
Describes concrete fixes for India–West distributed teams: use a proxy product owner co‑located with the dev team who travels monthly and gains decision authority; hire a strong scrum master as empathic glue; run explicit culture canvases to surface hierarchical vs. flat expectations; avoid 24/7 night-shift handoffs and instead find small daily overlap windows or a local interface role; prefers co‑location when possible and reports that proxy POs reduce four‑hour response delays into same‑day feedback.
AI-written summary · about
related talks
38mDistributed Sys Teams
41mKeeping distributed agile teams ‘face to face’
54mEffective SCRUM in Distributed Teams
43mScaling Yourself for Managing Distributed Teams...
47mDistributed Teams — Can They Work?
46mLeading Distributed Teams
37mBuilding & Scaling Distributed Teams
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams