GUIDE 2026

How to manage a remote team with distributed scrum: What I’d do

Josh Fechter
By
Josh Fechter
Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You…
More About Josh →
×

Distributed Scrum fails when you copy office ceremonies onto Zoom and call it culture. I'd redesign for async-first clarity and scarce overlap hours.

Practices I'd insist on

  • Written sprint goals and acceptance criteria before the planning call
  • Overlap hours protected for decisions—not status karaoke
  • Recorded demos and decision logs for zones that sleep through live
  • Explicit working agreements on response times and what counts as urgent
  • A single source of truth for backlog state (tool discipline beats heroics)

Ceremony tweaks that help

Ceremony Remote adjustment
Standup Async updates + short unblock huddle
Planning Pre-read backlog notes
Review Recorded demo + structured feedback
Retro Anonymous prompts + one experiment

Trust comes from predictable delivery and visible priorities—not more meetings. I'd measure whether distributed teammates feel equally informed.

Technical collaboration skills stack well with a Technical PM Certification. Keep learning in the newsletter.

Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You can connect with him on LinkedIn here.