Jim DeMarco
Jdemarco at hudsonhealthplan.org
Wed Feb 25 10:25:16 CST 2004
Exactly right (subjectively of course)!! I usually make a task list that shows every object I have to create and an estimate of how long to do each item (create table A, create table B, create Form A, etc). Then like Susan says triple it. The number will look ridiculous but given the little "gotchas" that pop up you'll be glad you did. HTH, Jim DeMarco -----Original Message----- From: Susan Harkins [mailto:ssharkins at bellsouth.net] Sent: Wednesday, February 25, 2004 11:19 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Determining Time for Project Yes, subjective. :) I have learned, the hard way, that the initial estimate is always way too short -- I now triple it -- and ignore that nagging voice that says, "You're an idiot!" Then, if you finish early, you're a hero. Susan H. I know that this is all subjective, but... How do you determine the amount of time required to build an application? I need to do it for an internal project, but I have NO idea how to estimate the time. I already know what the application needs to do and produce, but I haven't got the foggiest idea how to estimate time. I will be the only one that will be developing it, so I don't have to worry about other people, just me. Thanks for any hints, tips or ideas. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com