Do's & Donts for Distributed Scrum
summary
Nine pragmatic patterns from a decade of fieldwork spell out what actually changes distributed Scrum: a Global Gardener role that fixes system-level impediments across sites, value-stream teams instead of mapped roles, and an aligned rhythm with integration points. Examples: setups with 40 and 50 people per site suffer without a gardener; one-week developer visits routinely expose infrastructure gaps; prefer sneak previews during sprints, shared infrastructure with a Plan B, and regular face‑to‑face when forming new teams.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:39OUTSOURCING TRENDS
- 4:44SCRUM & DISTRIBUTED WORK
- 11:52VALVE-STREAM STRUCTURE
- 13:58ALIGNED RHYTHM
- 20:55SHARED
- 23:00PRACTICE
- 25:54ITERATE REQUIREMENTS
- 37:56DISTRIBUTED SCRUM PATTERNS
related talks
43mScaling Yourself for Managing Distributed Teams...
43mEver Since We Started Doing SCRUM Everything's Great. Not!
41mKeeping distributed agile teams ‘face to face’
43mCommunication Strategies for scaled and distributed teams
42mDistributed Agile Development
49mGlobally Distributed Software Engineering - The Good, the Bad and the Ugly
15mAdvanced Scrum techniques for optimal delivery
36mHow YOUR scrum team can excel in a remote setting