No formula here. Factors to consider include the experience of the programmer, the intellectual property of the studio, the level of customization required (including use of pre-built and pre-tested code), the amount of support available for similar types of application (bleeding edge technology vs. crunch and punch), and the main time delayer... amount of client-supplied content or requirements involved.
Or you could just use the factor of 2. "How long until you're finished?" "Oh, a couple of hours" "When will you deliver?" "In a couple of days" "How long for build?" "2 weeks" "When will we get paid?" "In a couple of months" :) Chad who will be done in a couple of hours On 4/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > A bit OT I know but does any one work with a formula that takes an > estimated number of hours in dev and then calculates (roughly) how much > time is required for specs, dev, documentation, testing? > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
