Just an idea - make your normal estimate and add 50%. If you still
under-estimate, keep on adding (say to 75%). If you feel you have
over-estimated, reduce it.
Alternatively, work out what you should have got for your recent
projects and compare them with what you estimated. This should give
you
Try to find your correction factor. Review some projects you did in
the past. Would you have been able to complete them in time if you
had had twice the time you estimated? Or 1.5x, or 3x? Or even higher?
Next time, estimate your resources in the usual way (breaking down
into chunks, etc), then
Joel Spolsky gave a great description of how to use this idea
systematically, calling it Evidence Based Scheduling:
http://www.joelonsoftware.com/items/2007/10/26.html
No reason it wouldn't work as well for design as for development, though you
might need to adjust the method to account for
Hi,
Not a direct answer, but this reminded me of A. Cooper's *An Insurgency of
Quality*http://www.brightcove.tv/title.jsp?title=1416866797channel=1274129191
.
He answers a similar question around the time 37:37 of the presentation.
Sebi
On Fri, Aug 1, 2008 at 7:37 PM, Lakshmanan L L [EMAIL
Hi,
I work on interaction design for an engineering/design application. I would
like to get some feedback from the forum on how do you do your resource
estimates for your design tasks.
Most of the times we end up under estimating the resource required to do a
design and have trouble
