>labedl 5, 10, 20, 30, 50, 60, 70, 80, 125 and so forth. When a client >wanted to know how long the job would take, how many billable hours >were involved or what the cost of the job was, the consultant would >spin the Bill-O-Meter and apply the correct units of measure (weeks, >months, hundreds of dollars, hundreds of hours, fortnights, furlongs, >etc.) to the result. We found the numbers correlated with the >length/cost/duration of the project as accurately as any estimate we >ever worked with, and was a much quicker ROI. > >--
Nice to know you didn't settle for any arbitrary old figure. I'm curious, are these the same methods Whil uses in the Software Developers Guide? _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
