What is Planning Poker?
Planning Poker is a consensus-based agile estimation technique used by development teams to estimate the effort or relative size of user stories, features, or tasks. It combines expert opinion, analogy, and disaggregation into an enjoyable approach to estimating.
Why Use Planning Poker?
- • Reduces anchoring bias: Everyone votes simultaneously before seeing others' estimates
- • Encourages discussion: Different estimates lead to valuable conversations
- • Leverages team wisdom: Combines diverse perspectives and expertise
- • Creates shared understanding: Team aligns on story complexity and requirements
- • Improves accuracy: Group estimates are typically more accurate than individual ones
Modified Fibonacci Numbers
We use a modified Fibonacci sequence that includes commonly used estimation values:
The gaps between numbers encourage relative sizing rather than precise time estimates.
For Facilitators
How to lead effective planning poker sessions
1Session Setup
Create and Share Room
Create a room and share the join link with your team members
Prepare User Stories
Have well-defined user stories ready with clear acceptance criteria
2Running the Session
Set the story name and description. Explain requirements, acceptance criteria, and answer any clarifying questions before voting begins.
Watch as team members cast their votes. Green indicators show who has voted. Wait for everyone to vote before revealing.
Click "Reveal Votes" to show all estimates. If there's disagreement (wide spread), facilitate discussion between highest and lowest voters.
Click "Vote Again" for another round if estimates are too spread out. Continue until you reach consensus.
Enter the final agreed estimate and click "End Voting" to complete the story and move to the next one.
💡 Facilitator Best Practices
- • Keep discussions focused on the story being estimated
- • Encourage participation from all team members
- • Ask follow-up questions when estimates vary significantly
- • Don't rush - let discussions happen naturally
- • Use the statistical analysis to guide final estimates
- • Record the reasoning behind estimates for future reference
For Team Members
How to participate in planning poker sessions
1Joining the Session
Use the Join Link
Click the room link shared by your facilitator and enter your name
2Making Estimates
Pay attention to the facilitator's explanation of the user story, requirements, and acceptance criteria. Ask questions if anything is unclear.
Think about technical complexity, unknowns, dependencies, and effort required. Compare to previously estimated stories of known sizes.
Select your estimate card without discussing with others first. This prevents anchoring bias and ensures independent thinking.
When votes are revealed, be ready to explain your estimate, especially if it differs significantly from others. Share your perspective and concerns.
Understanding the Cards
💡 Estimation Best Practices
- • Focus on relative sizing, not absolute time estimates
- • Consider all aspects: coding, testing, documentation, deployment
- • Factor in your team's velocity and experience
- • Don't overthink - go with your gut feeling initially
- • Be willing to change your estimate after discussion
- • Ask questions if story requirements are unclear
- • Remember that estimates are for planning, not commitments