Several years ago I worked for a Consulting firm that gave weekly classes
on job estimation. What you are calling the client factor, they called
the confidence factor. It is real and very useful.
>>And then, you have the "client factor", as in
>>* Work out a rough estimate
>>*
PROTECTED] On Behalf Of Tony G
Sent: Sunday, March 09, 2008 4:35 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Estimating Timelines
I've been meaning to blog on this for a while, thanks for the
opportunity:
removepleaseNebula-RnD.com/blog/general/2008/03/estimates1.html
> From: John
I've been meaning to blog on this for a while, thanks for the opportunity:
removepleaseNebula-RnD.com/blog/general/2008/03/estimates1.html
> From: John Rodgers
> Speaking for myself, ... today's
> applications are so complex that all the dependencies are
> impossible to forecast. It is not a que
ot;
* And we all have those 'Oh, maybe I forgot to mention ...' clients
that definitely rate a "10"
Yeah, I'm getting cynical in my old age
Regards
Mike
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin King
I have to weigh in on this in support of everything stated so far. John is
right, the first estimate is the one that "sticks" so that estimate has to
factor in what is known about the problem, solution, and path at the time
the estimate is requested, which is often before any real discovery has
ta
Analysis, design, and testing always take longer than programming. Even
with a code change of one line you may take a lot of time analyzing the
problem and the best way to fix it.
Jerry Banker
> -Original Message-
> From: John Rodgers [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2
