Planning Poker for large teams (10+ people)
Planning Poker works great with 5-9 people. But when the team grows to 10, 15, or even 20 members, the dynamic changes completely. Discussions get longer, voices get lost, and the session drags on.
The large team problem
With many people in the session:
- Discussions multiply — each opinion adds time
- Voices dominate — more extroverted members monopolize the conversation
- Fatigue arrives faster — more people means more total time
- Coordination gets complex — managing 15 simultaneous votes is different from managing 5
Strategies to adapt
1. Split into subteams
Divide the large team into groups of 5-7 by domain. Backend estimates backend tasks, frontend estimates frontend. Each subteam runs their own Planning Poker and facilitators consolidate afterwards.
2. Elect representatives
Each subgroup elects a representative who joins the main session. Representatives discuss internally with their subgroup before voting.
3. Async pre-voting
Before the synchronous session, everyone votes asynchronously. In the meeting, only items with high divergence are discussed (e.g., votes ranging from 2 to 13).
4. Limit the number of items
With large teams, aim for max 8-10 items per session. Schedule additional sessions if needed.
5. Use a dedicated facilitator
One person facilitates only — doesn’t vote, doesn’t opine, just manages time and ensures all voices are heard. Can be a Scrum Master or someone rotating.
Digital tooling is mandatory
With large teams, physical cards or spreadsheets don’t scale. Use a digital tool that:
- Reveals all votes simultaneously
- Automatically highlights divergences
- Maintains history per team and per item
- Supports 15+ simultaneous votes without lag
When to rethink the structure
If even with these adaptations Planning Poker remains unproductive, it may be a sign that the large team should be split into smaller squads. Teams of 5-9 people are more agile in every sense — estimation included.
Conclusion
Large teams need more structure in Planning Poker, not less. Dividing, pre-voting, limiting items, and dedicated facilitation are the pillars for maintaining estimation quality as the team grows.