Free Planning Poker by TeamRetro

Planning Poker is an agile estimation technique where team members assign story points to user stories based on their complexity, effort, and uncertainty, helping teams plan sprints more accurately. It promotes team consensus and surfaces differing perspectives early.

Planning Poker is a simple, team-based way to estimate work by combining shared understanding and quick consensus. 1) Pick a backlog item (user story/task) to estimate. 2) Review the details (goal, scope, and acceptance criteria) and ask clarifying questions. 3) Choose your estimate privately using the agreed scale (commonly Fibonacci: 1, 2, 3, 5, 8, 13…). 4) Reveal estimates at the same time so no one influences others. 5) Discuss differences if estimates vary, especially the highest and lowest, to uncover risks, assumptions, or missing details. 6) Refine the item if needed (clarify requirements, note assumptions, or split the work). 7) Re-estimate and repeat until the team reaches a reasonable agreement. 8) Move to the next item and keep going until you've estimated what you need.

Wide variance signals misunderstanding or hidden complexity. Have the highest and lowest voters explain their reasoning; often they've spotted risks or assumptions others missed. Discuss, clarify, and re-vote until the team aligns.

If estimates vary, the team discusses the reasoning behind their points. This often uncovers misunderstandings or missing details in the user story, leading to better alignment.

To run a successful session: 1) Prepare the work first: make sure each item has a clear goal, brief description, and acceptance criteria. 2) Keep stories small: split large items so they're easier to understand and estimate. 3) Align on what "done" means: confirm scope, assumptions, and any dependencies before voting. 4) Use a consistent scale (e.g. Fibonacci) for the whole session. 5) Vote simultaneously so everyone reveals at the same time. 6) Discuss gaps, then re-estimate: if estimates vary widely, let the highest and lowest explain why, clarify, then vote again. 7) Timebox discussions: park deep technical debates as follow-ups so the session keeps moving. 8) Capture notes: record key assumptions, risks, and action items directly in TeamRetro so everyone stays aligned.

No account is required for instant use, and you can reuse the same room number for future planning and estimation sessions.