Keeping distributed agile teams ‘face to face’
summary
Shows how small, practical changes measurably cut friction: moving developers and testers to sit together halves defect churn and speeds delivery; splitting one person into remote work multiplies external relationships from 1 to 13 to 33 to 49; using Skype and instant messaging for quick audio/video handoffs plus recorded sprint reviews and a deputy product owner restores timely feedback across time zones; mob then pair programming across sites builds shared skills; quarterly face‑to‑face meetups consolidate trust and make distributed teams work.
AI-written summary · about
chapters (17)
- 0:00Distributed agile teams
- 1:12Face to face communication
- 4:01Distribution and external relationships
- 6:52Time zone challenges
- 8:38Cultural differences in teams
- 11:07Cross-functional team shift
- 15:45Remote product owner setup
- 20:11Remote tester in time zone
- 23:23Split team with skill differences
- 27:32Instant messaging tools
- 29:18Remote meetings best practices
- 33:32Role of video in communication
- 35:17When to move people together
- 35:59Quarterly face to face meetings
- 37:21Team building activities
- 38:04Pair programming remotely
- 39:29Summary
related talks
41mHow to be a highperforming distributed agile team
37mBuilding & Scaling Distributed Teams
36mHow YOUR scrum team can excel in a remote setting
43mScaling Yourself for Managing Distributed Teams...
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
06mDistributed Teams
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
35mPair Programming from 2,000 km Away: Strategies for Distributed Agile Teams