Async Planning Poker: does it work?

Traditional Planning Poker is synchronous — everyone gathers, the PO presents, everyone votes. But what about when the team is in different timezones or schedules simply don’t allow a meeting? Is async Planning Poker viable?

How async Planning Poker works

The mechanics are the same as synchronous, but unfolded over hours or days:

1. The PO publishes stories with descriptions and acceptance criteria
2. Each member votes within a deadline (e.g., 24 hours)
3. Votes are revealed when everyone has voted or the deadline expires
4. If there’s consensus, the estimate is set
5. If there’s divergence, a focused discussion is scheduled

When it makes sense

• Multi-timezone teams — when members are in 3+ timezones
• Very large teams — async pre-voting before synchronous discussion
• Continuous refinement — estimate backlog items at any time, not just in meetings
• Partial availability — when not everyone can attend due to vacation or conflicts

When it does NOT make sense

• Small, co-located teams — live meetings are faster and more effective
• Complex items — requiring deep technical debate
• New teams — still needing to calibrate estimates together and share context

Advantages

• Flexibility — everyone votes at their most productive time
• Fewer meetings — reducing calls is always good for productivity
• More thoughtful votes — without time pressure, members can analyze calmly
• Inclusive — introverted members feel more comfortable voting

Disadvantages

• No immediate discussion — loses the spontaneous debate that reveals risks
• Can be slower — 24h async vs. 30 min synchronous
• Discipline dependent — if half the team doesn’t vote, the process stalls
• Lack of context — no chance to ask the PO in real time

Best practices for async

1. Detailed descriptions — without live Q&A, documentation must be impeccable
2. Clear deadlines — set a 24-48h voting window
3. Synchronous second round — if high divergence, schedule 10 min of discussion
4. Scalability — use tools that support notifications and automatic reminders

The ideal hybrid model

Many teams adopt a hybrid model:

• Async for clear, well-documented backlog items
• Synchronous for complex items or with divergence in async votes

This combination reduces meeting time by up to 50% without losing estimate quality.

Conclusion

Async Planning Poker works, but with caveats. It’s an excellent complementary tool — especially for continuous refinement — but it doesn’t fully replace synchronous sessions for items needing deeper discussion.