[AccessD] Determining Time for Project

Take a WAG.  Then double it.  Add a few hours of hair pulling and teeth
grinding.  Then, for every form involved, add 15 minutes if their bound, an
hour if their unbound.  Add 45 minutes for every Global variable that you
plan on using.

Once all that is done, triple your time.  Look at your projected start date,
and multiply the current 'time projection' by 100% + the current phase of
the moon divided by the average rain fall for that month over the past ten
yeats.

After all that, a one more day for good luck, and you should be as close as
you can get then.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bryan
Carbonnell
Sent: Wednesday, February 25, 2004 10:05 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Determining Time for Project


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.


--
Bryan Carbonnell - carbonnb at sympatico.ca
Unfortunately common sense isn't so common!

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com