3 T-Shirt Sizing Agile Methods (Guide + Free Sizing Board)

T-shirt sizing in Agile is a relative estimation technique. Instead of guessing hours, the team gives each epic, feature or task a size from XS to XXL based on how big it is compared with the other work in the backlog. It is the fastest way for a project manager or product owner to see the shape of a large backlog, prepare for portfolio planning, or answer the classic stakeholder question, “Roughly how big is this project?”, without pretending to know more than the team does.

This guide walks project managers through the three T-shirt sizing methods that work best in practice: T-shirt planning poker, affinity sizing and sprint bucket mapping. You will see when to use each one, how to run it step by step, a worked project example, and a free T-Shirt Sizing Board that turns your sizes into a sprint forecast you can share.

What Is T-Shirt Sizing in Agile?

T-shirt sizing replaces numbers with labels everyone already understands: XS, S, M, L, XL and sometimes XXL. A team looks at a backlog item and asks one question: is this bigger or smaller than the items we already sized? Because nobody has to commit to a number of hours, the conversation stays on scope, complexity and risk, which is exactly what a project manager needs to understand early in a project.

The technique is relative, just like story points. Story points are often described as an absolute or numeric method, but they are also relative sizes that each team calibrates for itself; the numbers simply make them easier to add up. T-shirt sizes trade that arithmetic for speed, which is why teams use them for epics and roadmaps and switch to points when the work gets close to a sprint.

To make the sizes useful, give each one a meaning your project team agrees on. Software development teams use T-shirt sizing most, but it works for any project team, from marketing campaigns to office moves. Here is a starting scale for epics in two-week sprints:

When Should Project Managers Use T-Shirt Sizing?

T-shirt sizing shines whenever you need a quick, shared view of how much work is ahead and you do not yet have the detail for story points. The most common moments are:

• Project kick-off. Size the epics to see how much work is involved and whether the Agile team has the right people, especially when you are collaborating with a software development partner.
• Agile portfolio and roadmap planning. Compare upcoming features across teams without breaking every one of them down into stories.
• Backlog triage. Spot the few huge items hiding in a long product backlog so the product owner can split, reorder or drop them.
• Teams new to estimation. Sizes are easy to learn and give a team a gentle first step before story points.

Be honest with stakeholders about what the sizes mean. Some Agile practitioners argue that estimates add little value and that a team should simply work on the most valuable item next, an idea known as #NoEstimates. Project managers rarely have that luxury, because budgets, contracts and release dates still need a forecast. T-shirt sizing is a good compromise: it gives management a rough picture for capacity planning without turning a guess into a project schedule, which is the most common mistake organizations make with early estimates.

The main premise of the no estimates movement is that estimates do not directly add value to your process or work, so you should find ways to reduce the estimation process or even stop it if possible

Stop Estimating: The #NoEstimates Movement in Agile – DZone Agile

The same idea of relative, size-based thinking applies outside software too. For teams that want to create branded apparel for events or team-building activities, exploring options to start private label production can help them develop custom designs that reflect their brand identity, and the project behind it can be sized just like any other backlog.

Method 1: T-Shirt Planning Poker

Planning poker is the best-known Agile estimation game, and it works just as well with T-shirt sizes as with numbers. James Grenning first described the method in 2002 and Mike Cohn later made it popular. Each estimator holds a set of size cards and everyone reveals their choice at the same time, so the first person to speak cannot anchor the rest of the team. Use it when you have a small number of important items that deserve a real conversation.

To facilitate a planning poker T-shirt sizing session, follow these steps:

1. Agree on the sizes. The facilitator or project manager hands out the cards (XS, S, M, L, XL and a ? card) and shows one reference item for each size.
2. Present the item. The product owner explains the epic or feature, using an Agile charter, a business case or simply the epic description. The team asks questions.
3. Vote in secret. Each team member picks the card that matches their estimate and keeps it face down.
4. Reveal and discuss. Everyone turns their card over at once. If the sizes differ, the people with the smallest and largest cards explain their thinking.
5. Re-vote until you agree. Repeat the vote until the team settles on a size everyone can accept. If the team cannot agree after two or three rounds, the item probably needs to be split or researched first.

Planning poker needs the whole team, which makes it slower than the other methods, but the discussion is the point. When two developers pick XS and XL for the same item, they almost always have different assumptions about the scope, and surfacing that early saves the project from a nasty surprise later.

Method 2: Affinity Sizing (The Silent Wall Sort)

Affinity sizing is the method to use when a project manager or product owner brings a long backlog and needs rough sizes fast. Instead of discussing each item, the team groups items of similar size on a wall or an online whiteboard, mostly in silence. It is especially useful at the start of a project, after a story-writing workshop, or when a backlog has grown out of control.

Here is how to run it:

1. Set up the columns. Write XS, S, M, L and XL across the top of a wall or a digital board, and add a column called Discuss.
2. Put each backlog item on a card. A short title is enough. The product owner stays nearby to answer quick questions.
3. Place once. One team member reads an item and places it under the size they think fits, without talking.
4. Move once. Anyone who disagrees can move the card to another column, again without talking.
5. Moved again? Discuss it. If someone wants to move a card a second time, it goes to the Discuss column instead. At the end, size those items with planning poker.

The no-talking rule is what makes the method fast, and it also stops one confident person from shaping every estimate. The team must move quickly and not overthink. The cards that end up in the Discuss column are not a failure; they are exactly the items where the project team has different assumptions or hidden risk.

Method 3: Sprint Bucket Mapping for Epics

The third method turns sizes into something a sponsor can plan around. Epics are large pieces of value that will later be broken down into user stories, and analyzing an epic should always start with its Minimum Viable Product (MVP), the smallest version that delivers value. Early on there is little data, so the team sizes each epic and maps every size to a range of sprints. The estimate is refined as the MVP is built.

Use a sprint chart like this one, adjusted to your own team and sprint length:

Working in XL sizes is not ideal. If an epic is larger than six sprints, break it down. Once every epic has a size, add up the low and high ends of each range and divide by the number of teams to get a forecast: “between 6 and 13 sprints, and we plan to 10.” That range is far more honest than a single date, and it narrows as each epic is refined.

Which T-Shirt Sizing Method Should You Use?

Most project teams end up using all three methods at different stages. This comparison helps you choose:

T-Shirt Sizing Board: Turn Sizes Into a Forecast

Use this free T-Shirt Sizing Board to put sprint bucket mapping into practice. List your epics or features, pick a size and a confidence level for each one, and the board adds up the sprint ranges, shows where the effort sits, flags items that need splitting and gives you a forecast with dates. It opens with the supervisor portal example below already loaded, and you can edit the size scale to match your team.

T-Shirt Sizing Agile Example

Imagine your project team is building a website where an organization’s supervisors can sign in and manage their documentation. Center the sizing on the project goals: the first release must let supervisors register, sign in and find documents. Each epic below will later be broken down into user stories; for now, the team sizes them with an affinity sort and maps them to sprints.

With two teams, the backlog comes to roughly 6 to 13 sprints, and the project manager plans to about 10. More than half of that effort sits in the document library, so the first action is obvious: split the XL epic and run a short technical spike on search before anyone promises a date.

Benefits and Pitfalls of T-Shirt Sizing

T-shirt sizing is popular because it simplifies estimation. Team members spend less time debating hours and more time talking about scope and risk, and when the sizes live in a shared tool, everyone can see who is working on what and how much is on each person’s plate. The main benefits for project managers are:

• Speed. A team can size dozens of items in a single session.
• Easy to learn. Anyone, including stakeholders outside the project team, understands the difference between S and XL.
• Better conversations. Disagreement on a size exposes hidden assumptions early in the project.
• Capacity planning. Mapped to sprints, sizes give a first forecast for budgets and roadmaps.

The pitfalls are just as real, and each has a simple fix:

• Subjectivity. One person’s M is another person’s L. Agree on a reference item for each size.
• Unclear differences between sizes. Use fewer sizes. Start with S, M, L and XL and add XS or XXL only if you need them.
• Sizes you cannot add up. T-shirt sizes are labels, not numbers. Map them to sprint ranges or story points before you forecast.
• Estimates treated as commitments. Always share a range and refine it as the work is broken down.

To see T-shirt sizing in action, watch the video below. It walks through a T-shirt sizing estimation session, shows how planning poker fits into the process, and explains how teams use relative sizing to estimate work more efficiently.

Tools for T-Shirt Sizing Online

Sizes are most useful when the whole project team can see them in one place. Most work management tools can store a T-shirt size as a custom field, and many online whiteboards are ideal for affinity sorting. For teams looking to visually represent their T-shirt sizing estimates or create custom T-shirts for team-building events, consider T-shirt printing online services to easily design and order custom apparel. Two popular tools for T-shirt sizing are Asana and Trello.

Asana

Asana uses T-shirt sizing for its own content projects and recommends deciding on a small set of sizes, agreeing on what each one means and tracking them in a shared field so project managers can gauge each person’s workload. Its guide also compares T-shirt sizing with story points.

How to use T-Shirt Sizing to Estimate Projects • Asana

Trello

Trello lets you add a custom field for T-shirt sizes to every card, then sort and filter cards by size. Automation rules can keep cards organized in the order you want, and because boards are shared, the whole project team sees the same picture.

How T-Shirts Can Style Up The Strategy For Your Next Big Project Kickoff (trello.com)

T-Shirt Sizing vs Story Points and Other Alternatives

T-shirt sizing is not the only way to estimate in Agile. The two alternatives project managers meet most often are story points and plain time estimates. Many teams combine them: T-shirt sizes for epics and roadmaps, story points for the stories in the next few sprints.

Fibonacci Series and Story Points

Story points represent the size, difficulty and effort of a user story compared with other stories. Many teams use a Fibonacci-style scale (1, 2, 3, 5, 8, 13, 21), where each number is the sum of the two before it. The scale is deliberately non-linear: the gaps grow as items get bigger, because the bigger an item is, the less precisely anyone can estimate it. Story points can be added up, which lets a team track its velocity from sprint to sprint.

Story points are not as precise as they look. Ron Jeffries, one of the creators of Extreme Programming, explains that stories were first estimated in “ideal days” and only later renamed to points, and he now questions how teams use them.

I like to say that I may have invented story points, and if I did, I’m sorry now.

Ron Jeffries, Story Points Revisited

Converting T-Shirt Sizes to Story Points

When work gets close to a sprint, many teams translate sizes into points. A common starting mapping is XS = 1, S = 2, M = 3 or 5, L = 8 and XL = 13, but there is no standard: each team should calibrate the mapping against items it has already delivered. Anything that maps above 13 points is usually an epic that needs to be broken down, not a story to estimate.

If you need a single early number for a whole project rather than relative sizes, a SWAG estimate or a top-down analogous estimate may suit you better. For tasks where you can give an optimistic, a most likely and a pessimistic time, use the PERT formula and calculator.

T-Shirt Sizing Facts Worth Checking

T-Shirt Sizing FAQ

Conclusion

T-shirt sizing remains one of the simplest and most effective ways for Agile teams and project managers to estimate work without getting bogged down in false precision. Use planning poker when a few items need a real conversation, an affinity sort when you face a long backlog, and sprint bucket mapping when stakeholders need a forecast. Whichever method you choose, agree on what each size means, split anything bigger than L, and share a range rather than a single date.

As the project moves forward, refine the sizes into story points and track how long the work really takes, so your next round of T-shirt sizing is even better calibrated. Try the T-Shirt Sizing Board above with your own backlog, and explore more free calculators and templates in our Free Project Management Toolkit. Ultimately, the goal is progress, not perfection.

Suggested articles:

• SWAG Estimates in Project Management
• Why You Need to Use Top-Down Analogous Estimating
• Agile Scrum for Beginners Made Easy: Roles, Practices and Ceremonies