How to be a highperforming distributed agile team
summary
Argues distributed agile teams can match co‑located performance and shows concrete wins: a Hyperloop volunteer team of ~400 goes from subreddit post to competition finalists, virtual co‑working produces long‑term partnerships, and simple upgrades cut meeting friction. Recommends low‑cost tools and behaviors: Crisp for noise removal, Meeting Owl and virtual whiteboards for presence, telepresence robots (~$500–$2,000) for lone remote members, and explicit team agreements plus trust built from reliability, consistency and responsiveness.
AI-written summary · about
chapters (5)
- 0:00Start
- 13:27create a team agreement with my remote team
- 22:59experimenting with virtual reality
- 35:19managing teams with different time zones
- 36:04try to mix up the type of communication
related talks
57mLessons from {distributed,remote,virtual} communities and companies
41mKeeping distributed agile teams ‘face to face’
08mHow to run distributed teams
37mBuilding & Scaling Distributed Teams
36mHow YOUR scrum team can excel in a remote setting
33mDistributed Teams
29mManaging distributed teams from your pyjamas
31mHow the “Aggregation of Marginal Gains” can help Distributed Teams become high-performing