How can a Developer Estimate Times?
SubliminalVortex wonders: "Many times in the past, I have been asked on 'how long' it would take to implement a certain features/fixes in a product. What's interesting is that many times, certain 'fixes' is adjusting the wording/placement of the items in question; in other cases, users want the product to do everything they ever imagined, since it already started by following their line of thought. From there, the problem continues. From the user interface, people 'imagine' and think that 'oh, it would be easy if...' and scenarios occur, not only internally from the company using the product, but the clients themselves. Usually, several good ideas are there, but estimating times is a pain in the arse if you have a platform you're writing code for which has no documentation. How do coders estimate times to their bosses? If I know the answer outright, I'll give it, but in some cases, I don't how much time I'll take from other developers *because of the lack of documentation*. I'm going to have to bring in my D&D dice next week just to start."
...use a random number generator? :)
More seriously, I've found from past exeperience you should always take whatever time you think the project will take and multiply that number by 2 or 3. If you are lucky (and the customer requirements don't change to much) you should make it.
To take a leaf from Star Trek just do what he always did. Say it will take 3 times as long as you think it will, and you will always get half that time to complete it. And if you get it done early you will be rewarded.
Win-win.
Count how many dumbshit managers with no technical knowledge you have over you.
Double your realistic estimate for each DM.
Skivvy Niner? Email me!
HEY! Look left just ONE MORE TIME!
first one, of course, is: "How can i make a woman tick?"
i just don't devote any more time to these 2 questions anymore...
I don't feel like it...
Hahahaha! Good one!
Management also often has information you may not haveHoo-haa! You're on a roll!
he/she isn't likely to be around much longerStop, please, you're killing me!
Proud neuron in the Slashdot hivemind since 2002.