We have to estimate the size of projects for forecasts, for portfolio-related decisions, and to prepare quotations for customers. But how can we reliably estimate a project’s size without identifying and analyzing every single user story? And does it make sense to analyze in so much detail when a substantial portion of the effort is likely to be wasted? Software sizing is an essential part of estimating our resource needs for a project. In order to forecast time and budget, we need to be able to quantify “what” we are building. This is because the resources required are related . . .