How YOUR scrum team can excel in a remote setting
summary
Remote Scrum shifts long co‑located rituals into a mix of async and short live work: teams compress cross‑timezone collaboration into a single golden hour and report heavy meeting fatigue, so experiment with rotating a single team representative for large program calls, combine short async standups plus a chat overflow channel, and use Miro/Mural and Jira to keep a 3–6 month backlog visible. Practical moves that work: rank calendars, replace some meetings with 15‑minute calls, ask for thumbs down on the working agreement, and add a bit of sparkle to standups.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:35What is an agile practitioner
- 4:34Rugby scrum
- 5:48Scrum in a work environment
- 8:35Online tools
- 10:14Challenges
- 14:25Scrum can be your friend
- 15:24How to address lag
- 18:00Too many meetings
- 26:13Remote participation
- 28:53Scrum ceremonies
- 29:28Backlog refinement
- 32:48Common issues
- 33:33Daily standups
- 34:30Sprint review
related talks
44mHow To Lead a Remote Team
39mHow to apply agile methodologies with teams on remote
48mTeam Leadership In The Time Of Remote Silence
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
52mRemote Working Approaches That Worked (And Some That Didn’t)
49mRemotely Operated - Managing Scattered Teams
41mHow to be a highperforming distributed agile team
26mRemote-first teams work better