We all know that software estimation is difficult to get exact, but I am not looking for exact. I'm looking to be able to derive an approximate number of person-hours for a project to know how many people to hire in a startup.
So, assuming you have:
Do people have any rules of thumb they use to quickly guesstimate the number of hours involved?
UPDATE: I am asking for ballpark estimations rules based on measurable but coarse requirements. Answers of "4 to 6 weeks" are fun, glib answers, but I'd like to hear from people who've actually established some simple barometers of work.
I always write up a detailed list of tasks that I need to accomplish. From there, I can better judge the amount of time for those individual tasks and I add those numbers up. After that, I tack on 25-50% extra as a buffer in case of complications, which always seem to come up.
When I say a list of tasks, I mean something like this: (this is an example, be as verbose as humanly possible, especially on a site-map)
I always estimate times in terms of hours. (not 15-30 minute blocks)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With