Project management is quite a large topic of discussion, but for the purpose of costing an application I personally like to use the Function Point Analysis, Optimistic-Likely-Pessimistic and Delphi models to determine a time/effort estimation. A function point analysis becomes more accurate the larger the application so I mostly use the OLP and delphi models for web development, but each to their own. A good set of standard project management doco's goes a long way.
As for charging for time taken producing an estimation - I dont think I have ever charged. It would be very difficult to charge clients and might start the relationship on a bad note to request compensation. If a client doesnt have a detailed specification that cant expect an accurate quote. my 2c. > Just wondering, how do any of you guys out there deal with creating > proposals? > > I mean a quick proposal is just a figure sucked out of thin air. > > Without proper requirements you really do not know how much time you are > going to spend or how much to charge etc. > But once you spend the time on real requirements gathering you spend at > least a day if not more to create something proper, does anyone do this > and > then bill it on to the client, or .... ? > And if billed on to the client, how does the client react? Surely they > have > no clue and see it as money down the drain unless you are talking with > large > companies who have gone through the process before. > > Just curious ;-) > > > Taco Fleur - Pacific Fox > an industry leader with commercial IT experience since 1994 . > http://www.pacificfox.com <http://www.pacificfox.com/> - Web Design and > Development > > > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to > [EMAIL PROTECTED] > > > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
