Understanding Planning PokerA collaborative estimation technique for Agile teams
What is Planning Poker?
Planning Poker (also called Scrum Poker) is a collaborative estimation technique used by Agile teams to estimate the effort required for user stories or backlog items. Team members privately select a card representing their estimate, then simultaneously reveal their choices. Discrepancies lead to discussion, helping align understanding and improve estimation accuracy.
Why Use It?
Planning Poker improves estimation accuracy through: 1) Collective intelligence - combining team perspectives, 2) Anchoring bias reduction - prevents influence from first estimator, 3) Knowledge sharing - discussion reveals hidden complexities, 4) Relative sizing - focuses on comparison rather than absolute numbers, 5) Team alignment - builds shared understanding of 'large' vs 'small'.
Items to Estimate
Estimation: User Story 1
? = Need more info, ☕ = Need a break
Team Votes
You
Waiting
Team Member 1
Waiting
Team Member 2
Waiting
Total Items
1
Estimated
0
Average Estimate
-
Rounds
1
Story Point Reference Guide
Very Small
Simple fix, one task
Small
Simple feature, minimal testing
Medium-Small
Straightforward feature
Medium
Normal feature with some complexity
Large
Complex feature, multiple components
Very Large
Major feature, significant complexity
Huge
Epic or very uncertain work
Massive
Consider breaking into smaller items
Planning Poker Glossary
Planning Poker
A consensus-based estimation technique where team members privately select estimates and reveal them simultaneously.
Story Points
A unit of measure for estimating effort. Represents relative complexity, not absolute time.
Fibonacci Sequence
The number series (1, 2, 3, 5, 8, 13, 21...) used because uncertainty grows with larger items.
Consensus
When team members agree on an estimate. Indicates shared understanding of the work.
Outlier
An estimate significantly different from the group. Usually indicates missing information or different perspectives.
Reference Story
A previously estimated item used as a benchmark for comparing new items.
Velocity
Average story points completed per sprint. Used to predict how much work can be done in future sprints.
Backlog
A prioritized list of features, bugs, and technical debt that need to be addressed.
User Story
A short description of a feature from the user's perspective: As a... I want... So that...
Sprint
A fixed time period (usually 1-4 weeks) where a specific amount of work must be completed.
Product Owner
The person responsible for maximizing product value and managing the product backlog.
Scrum Master
Facilitates Scrum processes, removes impediments, and helps the team work effectively.
Estimation
The process of determining how much effort a piece of work requires, measured in story points.
Refinement
The ongoing process of discussing backlog items to prepare them for upcoming sprints.
T-Shirt Sizing
An alternative to story points using sizes (XS, S, M, L, XL) instead of numbers.
Planning Poker Card (? )
Used when the estimator needs more information before providing an estimate.
Coffee Break (☕)
Used when the team needs a break before continuing with estimation.