A Tale of Two Cities - Early Adoption Stories
summary
Two large, distributed adopters rewrite legacy sales/support systems: one for 2500–3000 offices with 4‑week iterations and staged monthly releases to match hardware rollouts, the other with 3‑week sprints and teams split across US, India, Denmark and Singapore. Common failures: two‑day ScrumMaster class without values, offshore incentives that delay commits, builds controlled remotely, early waterfall behavior for 4–5 sprints, and normal 50+ hour weeks. Fixes that work: corporate video raised offshore participation, builds move to 1–2/day, formal retrospectives with manager action items, and a Solutions team one sprint ahead to shield dependencies.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:25What was it
- 6:28Who was involved
- 7:58Fully Distributed Teams
- 9:31Physical Environment
- 11:52Release Schedule
- 15:11Technical Environment
- 16:17Communication
- 18:28Planning
- 20:45Scrum Masters
- 23:43City N
- 28:17Problem Management
- 29:33Live Look
- 30:09This is Us
- 30:28Culture Differences
- 31:05Conclusion
related talks
16mLightning Talks
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
40mAgile Software Development: Practice and Analytics
39mScrum at Scale
51mWhy Scaling Agile Doesn't Work
21m600 Days of LeSS: A Practice Chronicle
18mAgile leadership and technical mastery, a harmonious alliance