liveBook · Manning

T-shirt sizing

As explained in Think Like a Software Engineering Manager

T-shirt sizing is a relative estimation technique that classifies work items into size categories such as Large, Medium, Small, and Extra Small.

Once a project plan identifies high-level tasks, the engineering team can T-shirt-size them: assign each task a relative effort category—Large, Medium, Small, or Extra Small. This gives the team a first view of the workload before estimating smaller tasks. section 10.1.3

Set a scale that fits your team

One possible scale is Large = 12 weeks, Medium = 8 weeks, Small = 4 weeks, and Extra Small = 2 weeks. Adjust those values to your team’s needs; they are not universal rules. section 10.1.3

After sizing, estimate granular tasks—using story points if the team follows an agile method. Compare the resulting effort with developer capacity or budget. If they do not align, discuss reducing scope, changing the timeline, or adding resources. section 10.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Gives a customizable four-category scale and next steps, but no detailed sizing procedure.
Examples
Illustrates Large, Medium, Small, and Extra Small with sample efforts of 12, 8, 4, and 2 weeks.
What it assumes
Assumes a project plan with identified tasks and supplies a simple scale if the company has none.
What you can do after
Practice/perform high-level sizing and use estimates to discuss capacity, scope, timelines, or resources.
How it connects
Links work breakdown structures and project plans to story points, developer capacity, and scope negotiation.

Also explained in

Compare how 2 books explain T-shirt sizing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.