Why convert relative sizes to hours?

Agile teams prefer relative sizing (T-Shirts, Story Points) because it compares complexity without committing to exact deadlines. However, stakeholders and clients often need concrete budgets and timelines. This converter bridges that gap using baseline averages.

How do I determine the 'Baseline Map' hours?

Look at past data. What is an example of an average 'Medium' task your team has completed? How many days did it take? If it took 2 developers 1 week (80 combined hours), then M = 80. By standard scaling, S would be 40 and L would be 160.

Why is there a Variance Range (-20% to +30%)?

Relative estimating is inherently uncertain. The 'Cone of Uncertainty' principle states that estimating sizes before work starts usually carries a high degree of variance. Providing stakeholders with a range (e.g., $10k - $14k) instead of a single number ($12k) manages expectations significantly better.

T-Shirt Size Converter

Bridge the gap between agile relative estimates and traditional cap-ex budgeting by mapping T-Shirt sizes into hourly projections.

Core Metric

Blended Hourly Rate ($)

The average hourly billing or cost rate for the team executing this work.

Backlog Size Quantities

How many backlog items currently exist for each t-shirt size?

X-Small (XS) Items

Small (S) Items

Medium (M) Items

Large (L) Items

X-Large (XL) Items

Guide

Relative Sizing to Budgets

Teams use T-Shirt sizes (XS through XL) exactly because they are not granular hours. A developer says "this is an XL, it's very complex", without committing to exactly 86.5 hours of work.

However, business stakeholders need to allocate corporate cap-ex budgets. This calculator allows you to apply an arbitrary average hour mapping to your team's abstract sizes to produce a working financial projection and resource baseline.

Managing Expectations

Never give a stakeholder just the solid number (e.g., $43,000).

Always provide the Budget Variance Range instead. Using the classic agile cone of uncertainty, early-stage backlog sizing is rarely accurate to the dollar. Over-estimate variance by at least +30% when requesting funding.

Frequently Asked Questions

How to Use

About the T-Shirt Size to Hours Converter

What it calculates

This t-shirt size to hours converter supports agile planning, prioritization, capacity forecasting, and team health tracking. Translate agile relative estimates into actual hourly budget projections and variances.

When to use it

Use when planning sprints, estimating delivery dates, or improving team workflows.

Example

Adjust the inputs above to model your specific scenario with the T-Shirt Size to Hours Converter.

Explore More

T-Shirt Size Converter

Core Metric

Backlog Size Quantities

Relative Sizing to Budgets

About the T-Shirt Size to Hours Converter

Related Calculators

Sprint Capacity Planner

Agile Team Health Radar

Estimation Poker

Lead Time & Cycle Time Analyzer

Monte Carlo Delivery Predictor

Project Scope Generator