Estimation Scales
Planning poker versus T-shirt sizing: choosing the right scale
Compare numeric planning poker cards and T-shirt sizing so your team can choose the right estimation scale.
Published by SprintDeck · Updated 2026-05-20 · 8 min read
Choosing between cards and T-shirt sizes
Planning poker cards and T-shirt sizing solve similar problems with different levels of precision. Fibonacci cards are useful when teams already plan with story points and want numeric trends. T-shirt sizes are useful when the team wants a rough early read or when stakeholders should not treat numbers as delivery promises.
The best scale is the one your team can explain consistently. If sizes lead to vague discussion, use cards. If cards create false precision, use T-shirts. SprintDeck supports both approaches through standard and custom decks, so the facilitation pattern can stay consistent while the scale changes.
A reliable facilitation pattern
The safest planning poker sessions follow a small repeatable loop: clarify the story, confirm acceptance criteria, give everyone a quiet moment to think, vote privately, reveal at the same time, and discuss only the spread that matters. That loop keeps the meeting from becoming a loud negotiation and gives quieter team members the same chance to influence the estimate as the first person who speaks.
SprintDeck is designed around that loop. A facilitator can create a room, share a code, choose a deck, watch voting progress, reveal once enough people have voted, and capture the final estimate while the conversation is still fresh. The tool does not replace product thinking or technical judgment; it protects those judgments from anchoring, scattered notes, and manual coordination overhead.
- Keep the story small enough that the team can reason about risk without inventing hidden scope.
- Ask for questions before voting, but avoid discussing numbers before the reveal.
- Treat a wide spread as useful information, not as failure.
- Capture the final estimate and the reason for any large disagreement before moving to the next item.
Common mistakes to avoid
The most common failure is turning estimation into a debate before independent votes exist. When a tech lead or product owner suggests a number early, the rest of the room often adjusts around that anchor. Another failure is forcing the average after reveal. An average can summarize numbers, but it cannot explain uncertainty, missing acceptance criteria, or a disagreement about architecture.
A healthier session makes disagreements visible and then narrows them deliberately. If estimates are close, the facilitator can confirm whether the group accepts the mode or median. If estimates are far apart, ask the highest and lowest voters what assumption drove their number. The goal is not to make every card identical; the goal is to uncover risk while the team can still respond.
- Do not reveal votes one by one.
- Do not use planning poker to pressure teams into lower commitments.
- Do not estimate vague stories just to keep the meeting moving.
- Do not treat story points as hours with a different label.
When numeric cards are better
Numeric planning poker cards are useful when a team has a stable velocity signal and needs estimates that can support sprint planning. Numbers make it easier to compare work over time, notice when large stories should be split, and forecast capacity without pretending that points are exact hours.
Use numeric cards when the team understands the scale and can explain the reason behind a final estimate. If numbers create pressure or false precision, the facilitator should reset expectations before continuing.
- Choose cards for sprint planning and backlog refinement.
- Choose cards when the team already works with story points.
- Choose cards when historical calibration matters.
When T-shirt sizing is better
T-shirt sizing is useful earlier in discovery, when the team needs a rough comparison but not a sprint-ready estimate. Small, medium, and large can help prioritize conversations without implying a delivery commitment.
The two scales can coexist. A team might use T-shirt sizes during discovery and planning poker cards when stories become sprint candidates. SprintDeck supports custom decks so the tool can match the team's decision stage.
Practical checklist
- Use cards when sprint planning needs numeric point estimates.
- Use T-shirt sizes when discovery needs rough comparison.
- Avoid mixing scales inside one forecast.
- Explain why the selected scale fits the decision stage.
- Switch from T-shirt sizing to cards when stories become sprint candidates.
- Use custom decks only when the team has a clear working agreement.
- Review whether the scale improves discussion or creates false precision.
- Confirm the page guidance maps to a real team decision, not only a keyword.
- Use the SprintDeck room to protect independent votes before discussion.
- Capture a final estimate only when the team can explain the main assumption.
- Link the resource back to a related guide when the team needs deeper context.
- Treat the checklist as facilitation support, not as a replacement for judgment.
- Revisit the recommendation after the team completes similar work in production.
- Document where the guidance changed the estimate, the story split, or the follow-up owner.
- Use disagreement as a signal for backlog quality instead of treating it as meeting failure.
- Keep examples concrete so readers can apply the advice in the next refinement session.
- Review whether the team needs a smaller story, a spike, or clearer acceptance criteria.
FAQ
Can a team use both scales?
Yes. T-shirt sizes can support early discovery while planning poker cards support sprint-ready estimation.
Which scale is better for stakeholders?
T-shirt sizes may be safer for early stakeholder conversations because they avoid false numeric precision.
Which scale is better for velocity?
Numeric planning poker cards are better when the team uses velocity as one planning input.