Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re: Estimating Task Complexity VS Loudmouth

by terra incognita (Pilgrim)
on Nov 23, 2004 at 15:58 UTC ( [id://409923]=note: print w/replies, xml ) Need Help??


in reply to Estimating Task Complexity VS Loudmouth

There is no silver bullet that will tell you how much time a task will take. Especially if you are new to the technology you are coding with. To do estimating well you need to have a constant feedback loop and accurate records of how long a task actually took. Each estimate you make needs to be feed in to the next estimate you make. Even if you use an algorithm for this you will still need to go through iterations before you will have an accurate estimate.

Here is how I provide estimates on my work.

• If I have not worked with the technology before I try to strip out everything I am familiar with and provide an estimate on that first.
• Then I do a quick assessment of how difficult the new stuff will be for me to learn. Part of that assessment is what resources I can call on if I get stuck, can I create something simple right away, and does something already exist I can use. I also try to create something using the new technology. I classify this as learning time.
• I then provide an estimate (guess) how long it will take to code the task in the new technology if had experience in it.
• Add some padding time, usually 15 – 20%.

You will be off, the chances of getting it right the first time is remote. However if you estimate a larger time than you need, it will be easier to manage the project and/or customer expectations. Studies make it clear that most projects will be under estimated so go longer than you feel you will need. As well if you are enhancing or maintaining code your productivity will be lower than if you are making new code. Typically programmers doing enhancement work are 70% as effective and maintenance programming is 25% as effective as new coding, so you will need to add padding for that.

No matter what the number is that you come up with keep your boss or client in the loop with the current estimate. They will be much more open to changes if you are open and honest with them. As well keep really accurate estimates of the time the task actually took. That way next time you will be that much closer ion your estimate.

  • Comment on Re: Estimating Task Complexity VS Loudmouth

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://409923]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others exploiting the Monastery: (3)
As of 2024-04-19 19:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found