Distributed Agile Development
summary
Mobile web engineering team embraces distribution since 2012, adopts Scrum rituals, drops a Wiki for project tools, and moves from Mingle to Trello and Google Hangouts; standups run Monday/Wednesday/Friday, team size roughly doubles, and biannual in‑person meetups happen. Norms include rule of three and if it didn't happen on the mailing list then it never happened, which cuts miscommunication, reduces conflicts, improves resilience, widens the global hiring pool, and yields measurably higher throughput.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:04OPEN SOURCE BRIDGE
- 3:19Distribution exacerbates communication problems
- 3:57workflow problems become obvious
- 4:48multiple people setting priorities
- 8:21rituals
- 11:02if it didn't happen on the mailing list...
- 14:16face to face, from time to time
- 27:27should the principle change?
- 28:33distribution problems
- 29:22discovering practices and tools
related talks
48mAgile from the Open Source Trenches
54mEffective SCRUM in Distributed Teams
41mKeeping distributed agile teams ‘face to face’
35mBuilding and Growing an Agile Team
43mFrom an Agile Team to an Agile Organization
20mAgile development application for live ops
49mDo's & Donts for Distributed Scrum
21mScaled Agile DevOps