Scrum Poker Guide

Scrum poker is planning poker used inside the Scrum framework. The technique is identical — private votes, simultaneous reveal, discussion, re-vote — but the roles, ceremonies, and outcomes align with Scrum events: sprint planning, backlog refinement, and occasionally release planning. The Product Owner presents backlog items, the Developers estimate effort, and the Scrum Master facilitates timeboxing and participation.

Scrum roles in a poker session

• Product Owner — Clarifies story intent, acceptance criteria, and business value. Does not dictate story points but answers scope questions.
• Developers — Everyone who will contribute to delivery estimates. In Scrum, "Developers" includes engineers, QA, design, and other builders — not only coders.
• Scrum Master — Keeps the session on schedule, ensures quiet participants speak, and stops debates from running without resolution.

Typical scrum poker flow

1. Review the user story and acceptance criteria as a team.
2. Ask questions until everyone understands the scope.
3. Each participant selects an estimate card privately.
4. Reveal all cards at the same time.
5. Discuss outliers — ask why the high and low voters chose their numbers.
6. Re-vote if needed until the team aligns or agrees to split the story.
7. Record the agreed story point value in your backlog tool.

Scrum poker in sprint planning

During sprint planning, the team estimates items until they fill capacity based on historical velocity. Scrum poker helps the team commit realistically: if every story lands at 8 or 13 points, that is a signal to refine or split before overloading the sprint. Combine estimation with a clear Definition of Ready so poker sessions do not stall on under-specified stories.

Scrum poker in backlog refinement

Refinement poker often moves faster than sprint planning because the team is sizing future work, not committing yet. T-shirt sizing can work here for very rough buckets; switch to Fibonacci when stories approach the top of the backlog. A healthy refinement cadence means sprint planning poker is mostly confirmation, not discovery.

Tips for effective scrum poker

• Timebox discussion per story — five minutes is a common starting point.
• Use a consistent scale across sprints so velocity stays meaningful.
• Treat large spreads as a refinement signal, not a failure.
• Include the whole delivery team so estimates reflect real work.
• Record assumptions in the ticket when the team picks a middle value after debate.

Remote scrum poker

Distributed Scrum teams should vote inside a dedicated tool rather than typing numbers in chat, which breaks simultaneous reveal. PlanITPoker provides real-time rooms, QR sharing, and vote charts for remote ceremonies. See our remote planning poker guide for a full checklist.