4 ms·
I have a policy in which I don't estimate jobs where my gut says will take more than 40 hours worth of work. Beyond that it's Agile style iteration work. I thi
by rpwilcox 15y ago
I have a policy in which I don't estimate jobs where my gut says will take more than 40 hours worth of work. Beyond that it's Agile style iteration work.
I think this has two advantages: I don't put that much time into "no real business here" leads, or (if there is business there), there's no way I know the whole scope of a large project in one conversation.
- superkinz 15y agoThat's interesting. So when you say that it's more than 40 hours (at least $X cost), do you still give a high end range or just say "we'll see how it goes?"
- rpwilcox 15y agoI'm not sure a high end range makes sense without sitting down with the client and spending time on creating an Agile product backlog. (With a product backlog then we can start getting a vague scope). I've actually revised my standard "potential lead" email based on some of the conversations in this thread. I now make it explicit that (a) I can help put together an Agile product backlog, for those larger project, and (b) make my hourly rate for this project manager/product owner work very explicit (to filter out those that don't actually have money)