As a new developer who is the only software guy on staff I have faced a few challenges but possibly the most difficult has been time estimates. I strugle every time I have to give a project estimate.
My question then is; If I do not have any experience and I don't have a fellow dev in my environment, how do I provide a solid estimate? I have read Joel Spolsky's article on Evidence Based Scheduling but how can that apply if I do not have any evidence?
I appreciate any advice on this subject.
By estimating the time required for one task, you can multiply that length by the number of similar tasks that the project involves. For example, if you can estimate that a meeting lasts half an hour and you have five meetings scheduled this week, you can estimate a total of 2.5 hours' worth of meetings this week.
Estimate at completion (EAC) is calculated as budget at completion divided by cost performance index. Formula 1 for EAC is as follows: Estimate at completion (EAC) = Budget at completion (BAC) / Cost performance index (CPI)
You don't provide a solid estimate. You give as good an answer as you can, and explain that it is just a very rough estimate, and why it's so rough.
If you make it very clear that:
I think you should be okay. You need to make those things very clear though, in writing, so that you don't get held to your rough estimates later.
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