On Tue, Aug 19, 2008 at 2:15 PM, MB Software Solutions General Account <[EMAIL PROTECTED]> wrote: > Stephen Russell wrote: >> On Tue, Aug 19, 2008 at 12:34 PM, Michael Madigan <[EMAIL PROTECTED]> > wrote: >>> What is the rule of thumb for what percentage of hours of a total > software development project should be devoted to >> >> Requirements 30% >> >> Design + Code 30% >> >> QA Testing and debug 30% >> >> Documentation 10% >> >> that is the guideline we follow. >> > > > So for billing purposes, you could take your coding estimate of hours > and triple it to get the bill you should charge, assuming equal rate > across all. For ISVs like myself, it's all the same rate, but perhaps > in larger shops, it's a different rate since different folks are doing > the different aspects of the work. > > I like that formula...thanks, Steve! -----------------------------------------------------------
Through 40+ projects our TIME spent on the project follows this fairly close. If it took the project team 3 weeks to define requirements and they do a very good job!!!!! It would take or dev team just as long to knock out the TDD, and code it. Usually one coder on a project but lately we have been running 4+ on our projects just to get them out the door REAL fast. Our documentation is done by our training department, it is not an IT function. :) -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] 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.
