The top 5 problems with distributed agile
summary
Distills five specific failure modes: teams-in-the-dark from poor domain access, the vendor-as-black box, persistent us versus them thinking, collapsed day-to-day communication, and cultural/hierarchy gaps that block self‑organization. Claims 80% of fixed‑price projects barely work, 10% end in legal pain. Recommends dedicated long‑term teams, scrum with empathic scrum masters, a proxy product owner and a process manager, plus the Distributed Team Canvas, Culture Canvas and a 1–10 collaboration metric.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30What is distributed?
- 2:232004: TRIP TO INDIA
- 3:592005-2010: CRIED MANY TIMES
- 5:57The black bog
- 8:34#3: Cultural differe
- 10:18Us versus Them
- 12:38SCRUM
- 14:25Serum Master - glue
- 18:25DISTRIBUTED TEAM CANVAS
- 19:35THE CULTURE CANVAS
- 21:28WRAP UP
related talks
41mAre You Failing at Being Agile?
33mReduce Small-Team Culture Shock with Agile
38mConway's law in practice: Agile teams & Microservises
45mYou can't be agile when you're fighting your code
48mAgile is STILL a Dirty Word!
47mAgility at Scale - Platform versus Product Concerns
48mThe 10 vicious circles at work: detecting and breaking them up
47mLong-lived teams are damaging to your organisation