How to run a remote estimation ceremony with clear host steps, silent voting, reveal etiquette,
and a free browser room on Scrumbets—no install, no spreadsheet tab wars.
On a video call, open voice votes bias the room. Spreadsheets lag, screenshare fights for focus,
and people with quieter opinions never put a number down. Planning poker works when votes stay
hidden until reveal, then the group talks only about the spread—not the first person who spoke.
Facilitation is the job: set the story, wait for everyone to vote, reveal once, drive a short discussion,
lock a number, reset for the next item. The tool should stay out of the way.
What Scrumbets gives you
Scrumbets
is Waryway’s lightweight planning poker app: open a room, share the link, cast hidden votes,
reveal together, and align. Standard Fibonacci-style cards plus specials:
Cards
Use
0 · 1 · 2 · 3 · 5 · 8 · 13 · 21
Relative effort / complexity
?
“I need more context” — vote without inventing a number
☕
Need a break (or this item is not ready to estimate)
Product-accurate note. Votes stay private until the room is revealed.
After reveal, Scrumbets can surface a score suggestion and discussion prompts
(missing votes, outliers, wide spread, or consensus)—use them as facilitator cues, not as the final decision.
Host steps (start to close)
Open a room. Go to
scrumbets.waryway.com
and create or join a session. Copy the room link for the call chat.
Name the story. Put the backlog item (title + one-line acceptance criteria)
in the session story field so everyone estimates the same thing.
Wait for joiners. Confirm each person appears as connected before you start the clock.
Late joiners can still vote once they land.
Frame the question. Agree the unit once (“story points relative to our last 5”)
and ban side-channel voice estimates until reveal.
Silent vote. Everyone picks a card. Watch for “has voted” indicators; don’t call out
numbers early. Prompt quiet people privately or with a neutral “waiting on two votes.”
Reveal once. When the room is ready, reveal. Do not re-hide and re-vote until
the discussion has a clear reason (new scope, missing AC).
Discuss the spread, then lock. High/low explain briefly; middle cluster often settles the number.
Record the estimate in your tracker, then clear/reset for the next story.
Reveal etiquette
No anchoring. Host and senior engineers do not say “this feels like an 8” before cards are down.
One reveal per story cycle. Re-voting is fine after new information, not to paper over disagreement.
Outliers speak first or last on purpose. Either ask extremes first (fresh reasoning) or last (avoid dominance)—pick a rule and stick to it.
Time-box talk. Two minutes of discussion, then re-vote or host proposes the cluster median.
Respect ? and ☕. Those are valid signals that the item is not ready—not “wrong” votes.
Anti-pattern. Reading votes aloud one by one as people click turns poker into a sequential poll.
Reveal together so the board appears at once.
After reveal: discussion prompts
Scrumbets can attach facilitator-style prompts after reveal—for example when someone has not voted,
when one person is far from the cluster, when the spread is wide, or when the room is in consensus.
Treat them as conversation starters:
No vote yet — “What’s blocking you, or do you need more context?”
Outlier — “Walk us through the approach that got you that card.”
Wide spread — “Are we estimating different scopes? Split the story?”
Consensus — Confirm once, log the number, move on. Don’t re-litigate green boards.
Facilitator checklist
Room link in the agenda / meeting chat before the call starts
Story text matches the ticket under estimation
Silent vote → single reveal → short discussion → lock → next
Cap the ceremony (e.g. 30–45 minutes); park unresolved items with explicit “needs spike”
Capture numbers outside Scrumbets (Jira, Linear, sheet)—the room is the ceremony, not the backlog
Try it
Spin up a free room and run your next estimation on Scrumbets.
Part of the Waryway suite of install-free team tools.
