Remote estimation etiquette that keeps rooms moving

Why open voice votes stall rooms

On a call, the first person who says “this is a five” sets the room’s weather. Quieter people match the loud number, seniors get echoed without challenge, and you spend twenty minutes arguing a single story while the backlog sits untouched.

Planning poker only works when estimates stay hidden until reveal. The ceremony is not a status chat or a design review—it is a short, structured pass: same story for everyone, cards down, one reveal, brief talk about the spread, lock a number, next item.

Product-accurate note. Scrumbets keeps votes private until the room is revealed, with Fibonacci-style cards (0–21) plus ? and ☕. Use that privacy as a social contract, not just a UI feature.

Silent-vote norms

Agree these rules once at the start of the ceremony (or paste them in the meeting chat). Norms beat tools when someone is tempted to narrate their card.

No spoken numbers before reveal. That includes “I’m between 5 and 8,” “definitely bigger than last time,” and screenshare of a private card.
No chat dumps of the number. Side-channel DMs and emoji polls collapse the same privacy the room provides.
Wait for the board, not for the loudest person. Host watches for who has voted; prompts are neutral (“two left”)—never “Sarah, what’s your number?”
Pick a card even when unsure. Use ? when you need context, not silence. Silence is invisible; a card is a signal.
Host does not pre-vote in voice. The facilitator models the rule: no “this feels like a 13” while others are still choosing.

Anti-pattern. Reading votes aloud one by one as people click turns poker into a sequential poll. Reveal once so every card appears together.

When discussion is OK

Discussion is not banned—it is scheduled. Talk after reveal, and only about what the board shows. Before cards, clarify the story; after lock, move on.

Moment	Allowed talk	Not allowed
Before vote	Story title, acceptance criteria, unit of estimate, “what’s in / out of scope”	Any effort number, “easy,” “huge,” comparisons that smuggle a size
During vote	“Still voting,” “waiting on two,” connection issues	Narrating your card, “I’m going high,” peer pressure to hurry a specific person
After reveal	High/low reasoning, scope mismatch, split or spike proposals, short re-vote if new facts	Re-litigating consensus, status updates, design debates with no estimate outcome
Large spread	“Are we estimating different work?” extremes explain once, then re-vote or split	Averaging without understanding; forcing a midpoint nobody owns

Rules of thumb after reveal

Tight cluster / consensus — confirm once, log the number, next story. Do not invent risk.
One outlier — that person speaks first (or last—pick a fixed rule). Others listen; then re-vote or adopt the cluster.
Wide spread — check for different scopes before “who’s right.” Often the story needs a split, not a louder argument.
Many ? or ☕ — stop estimating; capture “needs spike / not ready,” park it, protect the rest of the agenda.

Time-box talk: about two minutes for a normal spread, a bit more for a true split decision. If the room is still circling, host proposes the cluster median or parks the item—do not burn the ceremony on one ticket.

Anchoring pitfalls

Anchoring is any early signal that freezes the room around a size before independent judgment. Multiplayer poker exists to reduce it; etiquette is what actually stops it.

Senior first voice. If a tech lead says “probably an 8” on the call, juniors rarely put down a 3. Silence until reveal fixes most of this.
Reference stories spoken as sizes. “This is like the checkout work—that was a 13” is a soft anchor. Point at the ticket, not the old number, until after reveal.
Host “helpful” framing. “Should be quick” and “this might be big” are size words. Stick to scope and acceptance criteria.
Partial reveals. Peeking, counting hands on camera, or “three of us picked the same” before formal reveal all leak anchors.
Re-vote to paper over conflict. A second vote is for new information (scope change, missing AC)—not to pressure outliers into the middle.

Healthy alternative. After reveal, ask extremes for reasoning, not for permission to keep their card. The goal is shared understanding of the work, then a locked number in your tracker—not unanimous feelings.

Facilitator “keep moving” checklist

Room link in agenda / chat before the call; everyone joins the same Scrumbets room.
State the silent-vote rule once; point at hidden votes and a single reveal.
Story text matches the ticket; agree the unit (relative points, not hours) once.
Silent vote → wait for “has voted” signals → reveal once.
Discuss only the spread; time-box; lock the number outside the room (Jira, Linear, sheet).
Reset / next story; park unresolved items as spike or “not ready.”
Cap the ceremony (e.g. 30–45 minutes); end on time even if the backlog is not empty.

Scrumbets is the ceremony surface—hidden cards, reveal, Fibonacci-style deck—not your backlog of record. Log the estimate where the team already tracks work.

Try it

Open a free Scrumbets room, share the link, and run the next estimation with silent votes and one reveal. Part of the Waryway suite of install-free team tools.

Open Scrumbets Waryway hub All guides

Related guides

Host a Scrumbets room: first-run checklist — open the room and share the link before the ceremony starts.
Planning poker facilitation for remote teams — host steps, reveal timing, and the full facilitation flow.