I think the question is , how do we , as developers come up with reasonable estimates , without ending up getting burnt out due to working till the early hours of the morning so that one can still finish within the "qouted" estimate?
On 2/17/06, Carl Olivier <[EMAIL PROTECTED]> wrote:
Heh.The cry of coders down the ages.Estimate to yourself (say 16 hours) - then double it (thus 32 hours) then double it again (64 hours) and quote that. Haha - seems ott I know - but with scope changes, bad specs, etc - you will find it usually goes there anyways...And if not - you look good! Although if you always come in at half the estimate time this will also suck. :)Don't use that all the time - but have in teh past -specifically for difficult clients ;)
Rgds,Carl
From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Mutonho
Sent: 17 February 2006 10:35
To: [email protected]
Subject: [CTJUG Forum] EstimatesProject managers will always ask for estimates on the time a developer thinks he/she is gonna spend coding something.I know experience plays a major role in this , but generally speaking ,what techniques do you guys use?Any rules of thumb?Lies ,etc :) ?
--
Jeff Mutonho
Java/J2EE Developer
ph : + 27 21 408 6230
mob : + 27 82 907 6420
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
--
Jeff Mutonho
Java/J2EE Developer
ph : + 27 21 408 6230
mob : + 27 82 907 6420
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CTJUG Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/CTJUG-Forum
-~----------~----~----~----~------~----~------~--~---
