T-shirt estimation

by Jan 20, 2023

Don’t estimate unless you do it on a high level.

Use it for a roadmap. Use it as for relative size, not as time.

I don’t use the Fibonacci sequence anymore (1, 2, 3, 5, 8, 13, 20). It has too many values to choose from. Subconscious I still connect it with time, how hard I tried not to. It is also difficult to grasp for new people to a team. They are often confused how to score work using this.

My preferred way now is to use T-shirt sizes. People just ‘get’ this, they have experience using this measurement within their daily life. And for me, it doesn’t have any connection with time: it is just size. Relative size.

I try to only use S, M and L. So very high level and rough estimates. Occasionally a XS or XL slips in but try to stay away from it.

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more