Pair Programming from 2,000 km Away: Strategies for Distributed Agile Teams
summary
Diego runs nine developers across three companies with up to a three‑hour time difference and enforces eight hours a day of paired work, rotating pairs daily and assigning roles like driver/navigator, interrupts and build monitor. Development uses strict TDD, continuous integration into a always‑releaseable master and weekly retros and pointing. Remote pairing uses Screenhero, tmux and Chrome Remote Desktop plus Google Sheets/Docs for pairing boards and retros; remote pairing works well but some soloing for ~3 hours per day and occasional in‑person inceptions remain necessary.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:10Welcome
- 0:34What are distributed agile teams
- 1:13Who is Diego
- 2:05What is Agile
- 2:42Extreme Programming
- 3:13Pair Programming
- 4:45Pair Programming Station
- 5:32Morning Meeting
- 6:49Whiteboard
- 7:32Testdriven development
- 9:32Shared code ownership
- 11:30Pipeline
- 12:00Retros
- 12:59Collaborative Story Estimation
- 14:27Changes with Remote Development
- 14:59Pair Programming Tools
- 16:21Google Spreadsheet
- 17:16Google Docs
- 17:47Story pointing
- 18:34Time zone differences
- 20:33Team buyin
- 21:56Work in progress
- 23:20Inperson challenges
related talks
48m(Remote) Pair programming
44mWhat We Learned in 8829 Hours of Pair Programming
28mProblem Solving Through Pair Programming
32mMaximizing the Fun Pair Programming Benefits
47mExtreme Remoting
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
23mWarm-Up Talk: Perceptions of Pair Programming
36mDistributed & Local: Getting the Best of Both Worlds