When T-Shirt sizing Epics, should the size be based on 1 person's capacity or the teams capacity?
irl last edited by
My company wants the team to estimate (via t-shirt sizes) Features/Epics. When we attempt to do this, I often get asked "is this estimate based on 1 person or the entire team working on the feature/epic"? I'm not sure how to answer this question because I know our business leaders want to be able to convert relative sizes (like S/M/L) to weeks of work.
It doesn't matter as long as a) you are consistent and estimate every story the same way, and b) you can tell your business leaders what the conversion factor is.
There are additional layers of complexity that might influence your answer: are all tickets and developers interchangeable? Are all tickets worked by a single developer, or are some worked in pairs, or swarmed by the team? etc etc. But as long as you know what those things are, then you can do whichever is simplest.
(There's a whole other possible scrum/agile topic about whether business leaders ought to be that deeply in your business, and whether you should be using estimates to predict completion dates or velocity, but since you didn't tag this as scrum or agile, I won't go there. )