Run Tighter, Fairer Estimation Sessions
Quick answer
A good planning poker facilitator keeps the session neutral, reads stories clearly, enforces time limits, and draws out quieter voices. They load the backlog before the session starts, run a maximum of two estimation rounds per story, and step in only when the team is stuck.
Planning poker only works when someone is steering the ship. That person is the facilitator — usually the scrum master, tech lead, or whoever owns the sprint. But facilitation is not about having the right answers. It is about creating the conditions where the team arrives at honest estimates together.
The Facilitator's Role: Neutral by Default
The single most important thing a facilitator can do is stay out of the vote. When the person running the session also casts a number, it introduces anchor bias — especially if they are senior. PointPoker reflects this in its design: the facilitator role does not vote by default. Your job is to read the story clearly, field clarifying questions without steering the answer, and manage the flow of the session.
Pre-Session Prep: The Work That Makes Everything Else Faster
A session without a groomed backlog runs long and ends in frustration. Before anyone joins the room, confirm that every story in the queue has a clear title, acceptance criteria summary, and relevant links. In PointPoker, you can load your full story queue before the session starts. Rule of thumb: if you cannot read the story aloud in under sixty seconds and have the team understand what done looks like, the story is not ready to be estimated.
Pacing the Session: Timers and the Two-Round Rule
Use a per-round timer — sixty to ninety seconds is the right range. The timer creates productive pressure that prevents overthinking without rushing genuine deliberation. When votes diverge, ask the high estimator and the low estimator to share their reasoning, then run one more round. If the team still does not converge after two rounds, the facilitator makes a judgment call and moves on.
Managing Dominant Voices
Every team has someone who talks first and loudest. The simultaneous reveal is your first line of defense. Make sure everyone has submitted before you reveal. After the reveal, redirect the discussion toward outliers. Ask the quieter members first. Something as simple as "Sam, you went with a three — what are you seeing?" surfaces insights that would otherwise get lost.
When to Use the Facilitator-Participates Setting
If the team is small — two or three people — sitting out leaves the group too thin to surface meaningful divergence. If the facilitator has hands-on context that no one else has, their estimate carries real signal. PointPoker includes a facilitator-participates toggle for these cases. Use this setting deliberately, not as a default.
Remote Facilitation Challenges
Remote sessions introduce a different kind of latency: the latency of human attention. Read the story aloud before starting the timer. Call out participants by name if they have not submitted. Keep your session link pinned in the team's Slack or Teams channel so late joiners can find their way in without interrupting the flow.
Transferring the Facilitator Role Mid-Session
Sometimes the facilitator needs to hand off. PointPoker supports facilitator transfer without ending the session. The incoming facilitator inherits full control: they can advance stories, adjust settings, and reveal votes. Before you transfer, brief the incoming facilitator on where you are in the queue. The session state stays intact — votes cast, stories completed, and the remaining queue all carry over.
Facilitate your next session with full control
No account required. Load your backlog, set a timer, and start estimating in under a minute.
Start a Free Session