Date:         Wed, 22 Dec 2004 08:54:55 -0500
Reply-To:     "Bosch, Jules" <jules.bosch@SPCORP.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Bosch, Jules" <jules.bosch@SPCORP.COM>
Subject:      Re: Somewhat OT statistical programming question
Content-Type: text/plain

The two most important aspects of estimating programming time are having a
detailed specification and then having the estimate prepared (or reviewed)
by a person or persons who have in-depth experience with the project type.
The few major SAS projects where I have done estimates were done in a Word
table that had line-by-line work descriptions with estimated time (hours),
required resources, and dependencies.  Line items read like, "Create a frame
entry named X for...," "Add a list box named Y to frame entry X for...,"
"Create a SCL list to populate list box Y," etc. To the bottom line of the
time estimate was added a contingency ranging from 25 to 100% or more
depending on the adequacy of the specification and the size of the
project--less spec, more contingency.

Finally, I would create pseudo code in separate programs based on the line
items from the estimate.  It worked fairly well.

HTH,

Jules Bosch


*********************************************************************
This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.