estimio

Planning Poker vs. T-Shirt Sizing: Which Estimation Method Works Best?

Last updated: January 2025

Quick Answer

Planning Poker and T-Shirt Sizing are both popular agile estimation methods, but they serve different purposes. Planning Poker (using Fibonacci story points) is better for detailed sprint planning and teams that need precise estimates. T-Shirt Sizing (XS, S, M, L, XL) is faster and better for high-level backlog prioritization. Most agile teams use both: T-Shirt Sizing for initial prioritization, then Planning Poker for sprint planning.

What is Planning Poker?

Planning Poker is a consensus-based estimation technique where team members vote on story points using cards (typically Fibonacci sequence: 1, 2, 3, 5, 8, 13, 20, 40, 100). Team members discuss differences after voting, then re-vote until consensus is reached.

How Planning Poker Works

  1. Moderator presents a story - The team reviews the user story or task
  2. Team members vote independently - Each person selects a story point card
  3. Votes are revealed - Everyone sees all votes simultaneously
  4. Discussion - If votes differ significantly, team discusses why
  5. Re-vote - Team votes again after discussion
  6. Consensus - Process repeats until team agrees on estimate

Planning Poker Benefits

  • Precise estimates - Fibonacci sequence provides granular sizing
  • Team consensus - Forces discussion and alignment
  • Relative sizing - Compares stories to each other, not absolute time
  • Sprint planning ready - Estimates directly usable for velocity calculations
  • Reduces anchoring - Independent voting prevents bias

Planning Poker Drawbacks

  • ⚠️ Time-consuming - Can take 5-10 minutes per story
  • ⚠️ Requires full team - All team members must participate
  • ⚠️ Can be stressful - Some team members may feel pressured
  • ⚠️ Over-precision risk - May create false sense of accuracy

What is T-Shirt Sizing?

T-Shirt Sizing uses familiar clothing sizes (XS, S, M, L, XL, XXL) to quickly categorize work items by relative size. It's a simplified estimation method that focuses on speed over precision.

How T-Shirt Sizing Works

  1. Team reviews backlog items - Stories are presented one by one
  2. Quick categorization - Team assigns a size (XS, S, M, L, XL)
  3. Minimal discussion - Only discuss if there's significant disagreement
  4. Move to next item - Process is fast, typically 1-2 minutes per item

T-Shirt Sizing Benefits

  • Very fast - Can estimate 20+ items in 30 minutes
  • Low pressure - Less intimidating than precise numbers
  • Good for prioritization - Quickly identifies large vs. small items
  • Works with large backlogs - Efficient for initial sizing
  • Easy to understand - Non-technical stakeholders get it immediately

T-Shirt Sizing Drawbacks

  • ⚠️ Less precise - Only 5-6 size categories
  • ⚠️ Not sprint-ready - Usually needs refinement before sprint planning
  • ⚠️ Less discussion - May miss important details or risks
  • ⚠️ Harder to track velocity - Sizes don't map directly to story points

When to Use Planning Poker

Use Planning Poker when you need:

  • Sprint planning - Estimating stories for the next sprint
  • Precise estimates - Need story points for velocity tracking
  • Team alignment - Want to ensure everyone understands the work
  • Complex stories - Stories with dependencies or unknowns
  • Small to medium backlogs - 10-30 items per session

Best for: Scrum teams, sprint planning meetings, teams estimating 1-2 sprints ahead.

When to Use T-Shirt Sizing

Use T-Shirt Sizing when you need:

  • Backlog prioritization - Initial sizing of large backlogs
  • Quick estimates - Need to size 50+ items quickly
  • High-level planning - Roadmap or release planning
  • New teams - Teams new to estimation (less intimidating)
  • Stakeholder communication - Non-technical audiences

Best for: Product managers, backlog grooming, initial prioritization, large backlogs.

Hybrid Approach: Best of Both Worlds

Many successful agile teams use both methods:

  1. T-Shirt Sizing first - Quickly size entire backlog (XS, S, M, L, XL)
  2. Planning Poker for sprints - Refine M, L, XL items with Planning Poker before sprint planning
  3. Skip small items - XS and S items often don't need detailed estimation

Example Workflow

  • Quarter 1: T-Shirt Size entire backlog (200 items) → 2 hours
  • Sprint Planning: Planning Poker for 10-15 sprint candidates → 1-2 hours
  • Result: Fast prioritization + precise sprint estimates

Comparison Table

| Factor | Planning Poker | T-Shirt Sizing | |--------|---------------|---------------| | Speed | 5-10 min per story | 1-2 min per story | | Precision | High (Fibonacci points) | Low (5-6 categories) | | Best for | Sprint planning | Backlog prioritization | | Team size | 3-10 people | Any size | | Discussion | Extensive | Minimal | | Sprint-ready | Yes | Usually needs refinement | | Velocity tracking | Direct (story points) | Indirect (size mapping) | | Stakeholder clarity | Requires explanation | Immediately clear |

How to Choose the Right Method

Ask yourself:

  1. What's the goal?

    • Sprint planning → Planning Poker
    • Backlog prioritization → T-Shirt Sizing
  2. How many items?

    • 10-30 items → Planning Poker
    • 50+ items → T-Shirt Sizing
  3. How much time?

    • 2+ hours available → Planning Poker
    • 30-60 minutes → T-Shirt Sizing
  4. Team experience?

    • Experienced with estimation → Planning Poker
    • New to estimation → T-Shirt Sizing
  5. Need precision?

    • Yes, for velocity → Planning Poker
    • No, just prioritization → T-Shirt Sizing

Tools for Each Method

Planning Poker Tools

  • estimio: Free online Planning Poker with AI assistance, Jira integration, and real-time collaboration
  • Jira Planning Poker plugins
  • Physical Planning Poker cards
  • Miro/Mural templates

T-Shirt Sizing Tools

  • Jira backlog with custom fields
  • Trello with labels
  • Spreadsheets with size columns
  • Physical sticky notes with size labels

Common Mistakes to Avoid

Planning Poker Mistakes

  • Skipping discussion - If votes differ, discuss why
  • Rushing - Take time to understand the story
  • Anchoring - Don't let one person's vote influence others
  • Over-precision - Story points are estimates, not commitments

T-Shirt Sizing Mistakes

  • Too many sizes - Stick to 5-6 sizes (XS, S, M, L, XL)
  • No refinement - Remember to refine before sprint planning
  • Ignoring small items - XS items still need to be estimated
  • Inconsistent sizing - Use reference stories for consistency

Conclusion

Both Planning Poker and T-Shirt Sizing are valuable estimation methods, but they serve different purposes. Use T-Shirt Sizing for fast backlog prioritization and Planning Poker for precise sprint planning. Many teams successfully combine both: T-Shirt Size the backlog, then Planning Poker the sprint candidates.

The best approach is to start with T-Shirt Sizing to quickly prioritize your backlog, then use Planning Poker to get precise estimates for stories entering your sprint. This hybrid approach gives you speed and precision.

Next Steps


Related Articles:

Cookie Preferences

We use cookies to enhance your experience. Essential cookies are required for the service to function. Analytics cookies help us improve the service by understanding how you use it. IP addresses are anonymized and we respect Do Not Track settings. Learn more