Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do you do very quick (and dirty) estimations for coding tasks? [closed]

So you've just been put on the spot by The Boss. You've got 15 minutes to come up with a back of the envelope estimate for the addition of some new feature. Your boss (fortunately) recognizes that you can't provide an accurate estimate in that time so expecting something that is in the right order of magnitude.

The question is how do you go about giving a estimate in the time frame that is accurate to an order of magnitude?


Note that this is meant to be a quick and dirty estimate, not something that might be expected from questions like this

like image 438
Andrew Edgecombe Avatar asked Sep 20 '08 22:09

Andrew Edgecombe


People also ask

How to estimate programming hours?

A project's duration = overall task time estimation (E) + E*risk buffer + E*time eaters. So, if a project's overall task time estimation is 7,200 hours, the total project duration will be: 7,200 + 7,200*0.25 + 7,200*0.20 = 10,440 hours.

How do you estimate a code?

My opinion is that best practice for an estimate code is a sequential code starting with the year. For example, the code structure would look like this: 20-001, 20-002, 20-003. This would allow 999 estimates for the year. If you do more then make it 4 digits after the year.

Where can I adjust an estimate for a particular task?

Answer: Estimates tab is used to adjust the estimate for a particular task/activity. Explanation: We can adjust estimates for a specific task in the Estimates tab.


2 Answers

Place finger in mouth, lick, wave in air and make up a number based on past experience. Then double it.

Really, its just experience that counts. You imagine what the task entails you doing, and you know how long it'll take you to do that. Double it for unanticipated items. This is also why you never ask junior programmers for such estimates.

like image 168
gbjbaanb Avatar answered Sep 28 '22 08:09

gbjbaanb


The best way is to try a quick breakdown of all of the major sub-components, e.g.

  1. Update data model script (3 items in 2 tables)
  2. Change input screen (3 new inputs)
  3. Check Input (3 new inputs)
  4. Update Data.
  5. Display results etc...
  6. Build unit test

Assign a rough guess on each of these and if you can't think of one put down at least 2 hours, because even the simplest item will probably take at least an hour, but the 2x will allow for uncertainty.

At least you will have thought of all the items you will have to do so it will be in the right order of magnitude as was requested.

like image 22
Turnkey Avatar answered Sep 28 '22 08:09

Turnkey