Why estimation matters
Estimation is the foundation of sprint planning. Without it, teams cannot determine how much work fits into a sprint, and stakeholders have no basis for setting delivery expectations. Good estimates turn a vague backlog into a realistic plan.
Over time, consistent estimation builds velocity data that helps teams forecast future sprints with increasing accuracy. This is not about predicting exact hours — it is about understanding relative effort so the team can make informed trade-offs.
Estimation also improves communication. When a team agrees that a story is a "5" while another is a "13," they share a common language for describing complexity. That shared understanding reduces surprises mid-sprint and keeps stakeholders informed.
Planning poker
The most widely used agile estimation technique.
In a planning poker session, each team member privately selects a card with a numerical value — typically from the Fibonacci sequence. All cards are revealed simultaneously, preventing anchoring bias. When estimates diverge, the team discusses briefly and re-votes until consensus is reached.
The structured reveal-and-discuss cycle surfaces hidden assumptions and risks that other techniques often miss. Most teams estimate 8 to 15 stories per session.
Pros
- Precise numerical estimates
- Reduces anchoring bias
- Encourages thorough discussion
- Builds team consensus
Cons
- Slower per item than other methods
- Requires all team members present
- Can feel heavy for large backlogs
Best for: Sprint refinement and backlog grooming where precision matters. Read the full planning poker guide
T-shirt sizing
Fast, intuitive estimation for high-level planning.
Stories are sorted into buckets labeled XS, S, M, L, and XL based on relative effort. The team reviews each item and quickly agrees on a size. There is no formal reveal step — most teams simply discuss and place.
T-shirt sizing trades precision for speed. It is ideal when you need a rough sense of effort across a large number of items without spending time on detailed discussion.
Pros
- Very fast per item
- Easy to learn for any team member
- Great for roadmap-level estimates
- Low overhead and minimal ceremony
Cons
- Less precise than numbered scales
- Harder to track velocity over time
- Ambiguous boundaries between sizes
Best for: Roadmap planning and quick initial sizing. Compare planning poker and T-shirt sizing
Affinity mapping
Silent grouping for large backlogs.
The team silently groups user stories by relative size on a board or wall. Without discussion, each person places stories into clusters from smallest to largest. Once everyone has placed their items, the team reviews the groupings together and resolves disagreements.
Affinity mapping is extremely fast for large backlogs because it avoids item-by-item discussion. It works best as a first pass before applying a more precise technique to individual stories.
Pros
- Extremely fast for large backlogs
- Silent process reduces groupthink
- Visual layout reveals patterns
- Works well as an initial triage step
Cons
- Low precision without follow-up
- Requires physical or digital board space
- Limited discussion during grouping
Best for: Initial triage of 50+ backlog items before detailed estimation.
Dot voting
Lightweight prioritization with rough sizing.
Each team member receives a fixed number of dots and places them on backlog items to indicate relative effort or priority. Items with more dots rise to the top. The technique doubles as both a sizing and a prioritization exercise.
Dot voting is the most lightweight technique on this list. It works well when you need a quick read on team sentiment without a formal estimation session.
Pros
- Very fast and low ceremony
- Combines sizing with prioritization
- Easy for large groups
- No special tools required
Cons
- Very low precision
- No structured discussion
- Results can be ambiguous
Best for: Quick prioritization meetings and rough effort signaling.
Choosing the right technique
Match the method to your context for the best results.
Planning poker
Sprint refinement sessions where precision and discussion matter most.
T-shirt sizing
Roadmap planning and high-level estimation where speed is the priority.
Affinity mapping
Large backlogs that need fast initial triage before detailed estimation.
Dot voting
Quick prioritization and rough sizing when time is limited.
Frequently asked questions
Planning poker tends to produce the most accurate estimates because it combines independent voting with structured discussion. However, accuracy depends more on team calibration than the specific technique.
Yes. Many teams use T-shirt sizing or affinity mapping for high-level roadmap estimation, then switch to planning poker with Fibonacci values for sprint-level refinement. Matching the technique to the context improves efficiency.
Consider your team size, experience level, and the level of precision needed. New teams often start with T-shirt sizing. Experienced teams benefit from planning poker. Large backlogs suit affinity mapping for initial triage.
Yes. Any team estimating relative effort can adapt these techniques. Marketing, design, and operations teams have successfully used planning poker and T-shirt sizing for project planning.
Re-estimate when scope changes significantly or when the team learns new information that changes the effort required. Avoid re-estimating completed work — use it to update remaining items only.
Continue reading
More guides on agile estimation and team practices.
What is planning poker?
Learn what planning poker is, how the estimation technique works, and why agile teams use it for sprint planning.
Read guidePlanning poker vs T-shirt sizing
Compare planning poker and T-shirt sizing estimation methods. Learn the pros, cons, and when to use each technique.
Read guideEstimating user stories
A practical guide to estimating user stories using story points. Learn the process, common scales, and mistakes to avoid.
Read guide