3 ms·
If there is anything you can easily count or estimate, do it. It may be wildly inaccurate, but it's better than nothing, and those paying for the job also have
by Someone 10y ago
If there is anything you can easily count or estimate, do it. It may be wildly inaccurate, but it's better than nothing, and those paying for the job also have a hard time arguing about counts.
Examples:
If there is UI involved, count or estimate the screens and their complexity (# of controls, plus a factor for what your gut says the complexity of each control is)
If you have to process xml, json or something like it, count the number of different tags in the file. Again, add or multiply by what your gut/experience tells you the complexity of the structure or what you have to do with it is.
Similarly, for a database, guess/count tables, fields and foreign keys.
If there are N stakeholders, multiply your estimate by f(N) for some strictly increasing f (they won't accept f(x) = x, but square root works fine). if they complain, saying they will not disagree, ask them to appoint a single stakeholder so that the others don't need to waste time saying what that single stakeholder would say, anyways.