Guide · Agile estimation techniques

Planning Poker vs T-Shirt Sizing

Planning Poker and T-Shirt sizing are two popular Agile estimation techniques. Both aim to estimate user stories efficiently, but they are used in different contexts and serve different purposes.

Side-by-side comparison

Planning Poker

  • Uses numerical values (Fibonacci sequence)
  • Whole team votes simultaneously
  • Encourages structured discussion
  • More precise and granular estimates
  • Best for sprint planning and backlog refinement
  • Works well for remote and hybrid teams

T-Shirt Sizing

  • Uses qualitative labels (XS, S, M, L, XL)
  • Faster and more intuitive
  • Less discussion required
  • Lower precision, higher speed
  • Best for early backlog grooming and roadmap planning
  • Useful for large batches of stories

When to use Planning Poker

Planning Poker is the right choice when your team needs accurate estimates and shared understanding before committing to a sprint. It works best when:

  • Stories are already written and partially refined.
  • The team needs to align on complexity and risk.
  • You want to surface hidden dependencies before development starts.
  • Remote or hybrid team members need a structured way to participate.

Learn more about Agile estimation best practices or how Scrum teams use Planning Poker in their ceremonies.

When to use T-Shirt sizing

T-Shirt sizing is more appropriate at the start of a project or release cycle, when you need a rough picture of the backlog without investing hours in detailed estimation. Use it when:

  • You are estimating a large number of stories quickly.
  • Stories are not yet fully defined or refined.
  • You need a high-level roadmap for stakeholders.
  • Speed matters more than precision at this stage.

A T-Shirt sizing session in practice

Here is how a typical T-Shirt sizing session works when a team has a large, unrefined backlog:

  1. The Product Owner reads each story in 30 seconds — just the title and one-line goal, no deep discussion yet.
  2. Team members hold up a card or type a label: XS, S, M, L, or XL.
  3. If estimates align, the size is recorded and the team moves on immediately.
  4. If estimates differ widely (e.g. S vs L), the team takes 60 seconds to surface the main concern before re-voting.
  5. At the end of the session, stories labelled XS and S are ready for sprint planning. Stories labelled M are good candidates for a Planning Poker session. Stories labelled L or XL need to be split first.

Result of a T-Shirt sizing session

A team of 5 can size 30 to 50 stories in under an hour. This gives the Product Owner a realistic view of the backlog before committing to any detailed estimation.

Which one is better?

Neither is strictly better. Many Agile teams use both techniques at different stages of the same project:

  • T-Shirt sizing for rough estimation during discovery and roadmap planning.
  • Planning Poker for detailed estimation during sprint planning and backlog refinement.

A common combined approach

Use T-Shirt sizing to identify which stories are small (S), medium (M) or large (L). Then run a Planning Poker session only on the medium and large stories to get a precise story point estimate before they enter a sprint. This avoids spending Planning Poker time on stories that are already obviously small.

FAQ

Planning Poker vs T-Shirt sizing — common questions

Can I convert T-shirt sizes to story points?

Yes. Many teams map sizes to a Fibonacci range: XS = 1–2, S = 3, M = 5–8, L = 13, XL = 21 or more. This gives a rough story point estimate from T-shirt sizing, but it should be refined with Planning Poker before the story enters a sprint.

Which technique is better for remote teams?

Planning Poker works better for remote teams because it gives everyone an equal, anonymous vote at the same time. Online tools like Poker-Planning.org replicate this in a browser. T-Shirt sizing can work remotely using polls but offers less structure for discussion.

Should T-shirt sizing be done as a team?

Yes. Even though T-shirt sizing is faster and less formal, it still benefits from multiple perspectives. A story that looks Small to a developer might look Large to a QA engineer. Doing it as a group surfaces these differences before planning.

Does T-shirt sizing replace Planning Poker?

No. T-shirt sizing is a quick filter for large backlogs, not a replacement for Planning Poker. Once stories are refined and ready for a sprint, teams need the structured discussion and numerical precision that Planning Poker provides.