What is Scrum Poker?
Scrum Poker is a team estimation technique for Scrum and agile planning. Each participant chooses an estimate privately, then the team reveals all votes together and discusses differences before agreeing on a final estimate.
Run a focused Planning Poker session with private votes, live reveals, flexible decks, and clear facilitator controls.
Loading tool...
Scrum Poker, also called Planning Poker, is a lightweight way for a team to estimate work without letting the first loud opinion set the number. Everyone selects an estimate privately, the facilitator reveals all votes at the same time, and the team uses the spread to find hidden assumptions.
The goal is not to make story points mathematically perfect. The useful part is the conversation: a small estimate can reveal a simpler implementation path, while a large estimate can reveal risk, missing requirements, or work that should be split before sprint planning.
Scrum Poker is a team estimation technique for Scrum and agile planning. Each participant chooses an estimate privately, then the team reveals all votes together and discusses differences before agreeing on a final estimate.
Hidden votes reduce anchoring. A senior voice, early number, or confident guess can pull the whole team toward one answer before quieter participants have shared their own view.
Use Fibonacci when you want classic story point estimation with bigger gaps as uncertainty grows. Use Linear for small, concrete work. Use T-shirt sizes when the team only needs rough relative sizing.
The room creator and promoted facilitators can reveal or hide votes, start the next backlog item, edit the active item title, and change room settings. Regular members can join, update their name or avatar, and vote.
Changing the deck clears the current votes and hides results, because some selected values may not exist in the new deck. Change decks before the team starts voting whenever possible.
? is useful when the item is too unclear to estimate. Coffee is a pause signal. Treat both as conversation signals rather than numeric estimates.
Rooms are kept in memory and inactive rooms are closed after one day. Use the room for the live session, then save the agreed estimates in your normal backlog or issue tracker.