How to Be a High Performing Distributed Agile Team
summary
Shows three concrete rules — make communicating easy, define normal behavior, create presence — and names real tools and experiments: Crisp AI for noise removal, Meeting Owl and Logitech gear, Sakoku virtual office, Kubi and Suitable Technologies robots, Rumi VR and holograms (Tupac at Coachella). Gives surprising numbers and cases: a 400‑person volunteer Hyperloop finalist, an agile coach who works a month from Argentina without team noticing. Emphasizes what was built, what worked, and practical tradeoffs (Skype for business remains a pain).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:48Remote work in agile manifesto
- 4:05Proof remote agile teams succeed
- 7:15Easy remote communication
- 14:02Normal behavior on distributed teams
- 17:53Presence and work visibility
- 27:02Simple ways to build presence
- 28:25Overcoming time zone challenges
- 30:13Key takeaways
related talks
53mTips & Tricks to Become a High-Performance Team
41mA Clear-Eyed Look at Distributed Teams
38mPolyglot Agile
26mVirtual Scrum
36mDistributed & Local: Getting the Best of Both Worlds
20mRevealing Mechanisms to Create Resilient Teams and the Organizational Culture That Supports Them
49mDelivering with Self-Organized Teams — Real, Fast + Good
34mBecoming a team, one pixel at a time