The Scrum Guide doesn't mention time zones. It was written for teams that could stand in a circle every morning, hash out sprint scope over a whiteboard, and grab coffee together between meetings.
That's not most teams anymore. If your engineers sit in New York, Berlin, and Bangalore, you're dealing with a 10.5-hour spread. Sprint planning at 9am Eastern is 7:30pm in India. Your "quick retro" at 4pm Berlin time hits Bangalore at 8:30pm.
The usual fix is rotating who gets the bad meeting time. That's fair, but it still treats every ceremony as a synchronous event. And that's the actual problem.
Not every ceremony needs a meeting
This is the question most teams skip: which ceremonies actually require everyone talking at the same time?
| Ceremony | Needs sync? | Why |
|---|---|---|
| Daily standup | No | Written updates are faster to consume and don't require timezone coordination |
| Sprint planning | Partially | Scope negotiation needs real-time discussion, but context-sharing doesn't |
| Sprint review | Yes | Live stakeholder feedback is the whole point |
| Retrospective | Yes | Honest team conversations about dynamics need tone of voice and real-time energy |
| Backlog refinement | Hybrid | Async pre-read, sync for questions and estimation |
The daily standup is the easiest ceremony to move async, and it frees up your overlap window for the ceremonies that actually benefit from live discussion.
The overlap window
Map out when your team members are all within working hours. For most globally distributed teams, this is 2-4 hours. Some get less.
For that NYC/Berlin/Bangalore spread, the overlap is roughly 14:00-16:00 UTC. Two hours. That's it.
Those two hours are sacred. One meeting per day, max. Everything else happens async. If you're burning your overlap window on status updates, you won't have time left for sprint planning or retros, which are the ceremonies that actually suffer without real-time discussion.
A small trick that helps: ask people to flex 30-60 minutes in either direction. A Berlin dev starting at 10am and a Bangalore dev staying until 7:30pm buys you an extra hour. Rotate who flexes so nobody's always the one adjusting.
Sprint planning without the 2-hour meeting
The async-prep-sync-decision pattern cuts planning meetings in half:
- 48 hours before: PO shares candidate backlog items with acceptance criteria and context. Team reads and posts questions async.
- 24 hours before: Team runs async estimation (planning poker works well here — everyone votes independently and you can spot disagreements before the call).
- During overlap: Live session focuses only on resolving disagreements and committing to the sprint goal. 45-60 minutes instead of 2 hours.
The information transfer happens async. The negotiation happens sync. You stop wasting synchronous time on things people could have read on their own.
Why retros need to stay synchronous
I'd argue retros are the ceremony you should fight hardest to keep live. The candid, sometimes uncomfortable conversations about how the team works don't land the same way in a shared doc. Text strips out tone. Written responses feel less safe than spoken ones.
That said, you can make the sync portion shorter:
- Have people add retro items to the board before the meeting. This gives everyone, especially those in less convenient time zones, equal chance to contribute.
- Keep it to 60 minutes. Distributed retros lose energy faster than in-person ones.
- Use anonymous voting. Power dynamics get amplified on screen.
Distributed teams need retros more than co-located ones. Miscommunication and unclear handoffs pile up silently when there are no hallway conversations to catch them. The retro is where that stuff surfaces. Skip it and the problems just compound.
The sample week
Here's what it looks like in practice with a 2-hour overlap (14:00-16:00 UTC):
| Day | Overlap window | Async |
|---|---|---|
| Monday | Sprint planning (60 min) | Standup updates, planning pre-read |
| Tuesday | Open for ad-hoc sync | Standup updates, refinement pre-read |
| Wednesday | Refinement (45 min) | Standup updates, estimation |
| Thursday | Open for ad-hoc sync | Standup updates |
| Friday | Retro or review (60 min) | Standup updates, retro board input |
One meeting per day in the overlap window. The rest of the time, people build things.
What usually goes wrong
Defaulting to HQ time. If leadership is in New York and every meeting happens during East Coast hours, your other offices are permanently accommodating. People notice and stop engaging.
Skipping documentation. Co-located teams have hallway conversations. Distributed teams don't. If you didn't write it down, it didn't happen for anyone who wasn't on the call.
Adding more meetings to compensate. The instinct when async communication feels lacking is to schedule more syncs. This makes it worse. Fix the async communication instead.
I wrote a longer version of this with concrete team agreements, sprint review strategies for multiple timezone clusters, and a deeper breakdown of the async-first approach. You can read the full post on the Kollabe blog.
If your team is already doing async standups or hybrid planning, I'd love to hear what's working. Drop a comment.
Top comments (0)