Planning Poker Facilitator Tips

Running a session well is mostly about protecting a few simple rules from getting quietly skipped under time pressure. If you're new to the technique itself, start with What Is Planning Poker?. Facilitating in Scrum specifically? See Scrum Poker.

Protect independent voting

The entire point of simultaneous reveal is that nobody's estimate influences anyone else's. It's tempting to let someone "just quickly say their number" to speed things up - resist it. One early loud opinion is often enough to quietly drag the rest of the team's votes toward it.

Ask the outliers to explain, don't just average

When votes spread out, the instinct is to split the difference and move on. Don't - ask whoever voted highest and lowest why. The highest estimator often knows about a dependency or edge case nobody else considered; the lowest often knows a shortcut. Averaging throws that information away.

Set a time limit per story, out loud

Announce it before voting starts, not after the discussion is already dragging: "let's timebox this to three minutes." A visible timer removes the awkwardness of someone having to be the one to say "we should move on."

Know when to stop re-voting

Two rounds of voting is normal. If a third round still doesn't converge, that's a signal the story itself is underspecified, not that the team needs to vote harder. Park it, write down the open question, and move to the next story rather than burning the whole session on one item.

Share the facilitation role

The person running the session (starting stories, revealing votes, calling time) doesn't have to be the same person every week. Rotating it - or, in Fibopoker's case, letting a Premium host delegate a moderator for a session without handing over full account ownership - keeps one person from becoming a scheduling bottleneck for the whole team's refinement sessions.