I believe that one cannot make an accurate time estimate without a technical specification.

Once the technical specification has been drafted(that takes time) you can extract all the functions and allocate time to each one.

Each function should be tested(xtreme programming) as u unit.

 

I know this sounds like the ideal world but I have burnt my fingers so many times with this.

The less experienced you are the more necessary this becomes.

 

In the real world though, the PM comes along and casually asks how long it will take and expects you to thumb suck some estimation in 5 mins about a 2 month project!

Most of the time the client doesn’t know what they want yet ect ect.

 

Just make very sure about what you say because TIME = MONEY in our world.

 

 

 

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Mutonho
Sent: Friday, February 17, 2006 1:12 PM
To: [email protected]
Subject: [CTJUG Forum] Re: Estimates

 

But then there could be a situation where a PM "feels" that one is asking for too much time..or perhaps another developer in the team could claim that another developer is asking for too much time for what they "perceive" to be an easy job.
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] Estimates

Project 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to