What does pointing poker mean?
Pointing poker means assigning a relative point value to a story after the people doing the work have considered its size, complexity, and uncertainty. Each participant chooses privately, then all cards are revealed together. The simultaneous reveal matters because it prevents the first estimate from becoming an anchor for everyone else. The value is useful only inside the team’s own scale: a 5-point story in one product is not automatically the same amount of work as a 5-point story in another.
How a round works
The facilitator presents one story and its acceptance criteria. Participants ask questions until they can describe the work clearly enough to estimate. Everyone selects a card, and the room waits until the votes are in. The facilitator reveals the cards at once and invites the highest and lowest estimators to explain what they saw. The group discusses scope, dependencies, unknowns, and possible implementation approaches. If the disagreement came from missing information, clarify the story or add a discovery task. Vote again when the conversation has changed the shared understanding, then record the estimate the team can support.
Why use Fibonacci values?
Many teams use 1, 2, 3, 5, 8, 13, and 21 because the gaps grow with uncertainty. Small stories can be compared closely; larger stories need a broader conversation. A large card is often a signal to split the story rather than a precise measurement. Teams may add 0 for no effort, a question mark for insufficient information, or a coffee card when the meeting needs a pause. The specific deck matters less than using it consistently and explaining what the values mean.
Common mistakes to avoid
Do not convert points directly into hours, use an average to hide disagreement, or treat a card as an individual performance score. Do not keep estimating a story that has unclear acceptance criteria. A Scrum Master can improve the session by protecting independent thinking, asking for evidence behind outliers, and stopping the round when a missing decision is the real blocker. Over time, compare completed work with the team’s own previous estimates to improve forecasting, while remembering that points describe relative effort rather than a universal unit.