Are there any benchmark time frame (eithe rabsolute or relative) figures available for the "four" phases, viz., Plan, Design, Develop and Implement of projects. Ofcourse it varies with the size and the industry, but relative fiure may be available Saving Changes...
Actually, as rightly said by you breakup depends upon the duration of project, but ideally the time frame for 4 phases can be Req 17% Design 18% Code 25% Test 40%
Applying this percentage on total efforts we can get timeframe
Following on this I am interested if anyone knows of any industry papers either FOR or AGAINST putting some kind of "guidline" for how much time to spend in each of the project processes (in general) for the pm processes (initiating, planning, executing, etc). Anyone know of anything that exists arguing something either way? Saving Changes...
I'm with Frank Patrick on this topic. You need to factor in size, complexity, objectives, culture, processes, skill sets, technology, executive support, PM organizational maturity, reporting requirements, and so on, not to mention past historical performance which is probably your best indicator. Saving Changes...
By the way, if you spend more than 15% of the project schedule on the test phase, then you need to take a very serious look at your processes in place and the qaulity of your IT staff immediately. Saving Changes...
