I'll join the chorus and say that this is great stuff, jacquesm.
Estimation is one thing that makes me very nervous to the point of not wanting to start my own thing. I have always underestimated things (and once it got very bad when I was doing contract work). If you could expand on tips here (such as what to avoid - i.e. don't switch to a new programming language before starting work), it would be much appreciated.
Here's my rule for estimating time: figure out how long it should take and multiply that by 3.
This has worked out to be in the right area about 80% of the time. I have one particular client where I bumped the multiplier up to 4 because of how often they ask for major changes halfway through the work.
Comments
I'll join the chorus and say that this is great stuff, jacquesm.
Estimation is one thing that makes me very nervous to the point of not wanting to start my own thing. I have always underestimated things (and once it got very bad when I was doing contract work). If you could expand on tips here (such as what to avoid - i.e. don't switch to a new programming language before starting work), it would be much appreciated.
Here's my rule for estimating time: figure out how long it should take and multiply that by 3.
This has worked out to be in the right area about 80% of the time. I have one particular client where I bumped the multiplier up to 4 because of how often they ask for major changes halfway through the work.
Ok, I'll do that, give me a couple of days to get it done.
The irony is rich.
Yep.
But it will be done in a couple of days (2 days == couple), I guarantee it.
Ok, to make good on my promise, I've amended the estimating page, it is about 3 times the original length now.
Probably the way I'm going to continue this project is to flesh it out slowly and to continue to subjects that deserve a page by themselves.
I hope the additions are useful to you, you can find them here:
http://jacquesmattheij.com/be-consultant/estimating