rsmethurst at UK.EY.COM
rsmethurst at UK.EY.COM
Wed Feb 25 10:24:12 CST 2004
Good advice...me thinks. Better to end early, than late. Since it's only you, you won't have to take into account what other people are doing, or what is the critical path of the project, you'll only be able to do things one at a time and in a step by step process. Roughly, break the project as a whole down into small, manageable 'modules' or tasks. (At least into packages that you will be able to have a guestimate as to how long you will take to get them done.) Then have a look at how long each module will take. If you are reliant on anyone or anything to get modules done, be sure to build this into your timeframes, and as Susan said, be generous...there's always something out there just waiting to trip you up! :) Ryan "Susan Harkins" <ssharkins at bellsouth.net> Sent by: accessd-bounces at databaseadvisors.com 25/02/2004 16:18 Please respond to Access Developers discussion and problem solving To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> cc: 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 This e-mail and any attachment are confidential and contain proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient, please notify the author immediately by telephone or by replying to this e-mail, and then delete all copies of the e-mail on your system. If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this e-mail. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachment has been checked for viruses, we cannot guarantee that they are virus free and we cannot accept liability for any damage sustained as a result of software viruses. We would advise that you carry out your own virus checks, especially before opening an attachment. The UK firm Ernst & Young LLP is a limited liability partnership registered in England and Wales with registered number OC300001 and is a member practice of Ernst & Young Global. A list of members? names is available for inspection at 1 More London Place, London, SE1 2AF, the firm?s principal place of business and its registered office.