Dr Mike O'CallaghanCoach & Project Manager| Relevant InternationalCape Town, South Africa
Hi All
I'm looking for any source of stats that will allow me to determine proportions of project time dedicated to each phase of the project.
I'm sure that there must have been research to substantiate the vague proportions that PMs have in their heads (e.g. 10 to 15 % for Planning) Saving Changes...
Sort By:
Stuart DixonProject Office Manager| Xl CatlinCrowbrough, United Kingdom
The most realisitic source of stats is the actuals as booked to the phases of each of the projects that your company has already performed. These stats will vary with the type of project performed, plus with the degree of confidence of the solution that the project has started with i.e. an upgrade project may be easier to estimate for than one using a new package, technology or methodology.
I would suggets you ask your PMO, or equivalent, to do some counting up of the actuals by phase for similar projects to yours that have occured over the last year, and then use that as general guidance for the ones you will perform in the future.
Of course the point to bear in mind is that this research will need to be updated regularly (say each year) to ensure that the percentages are still valid.
It also means that you are one step closer to continuous improvement in your company. Saving Changes...
BUBU TRIPATHYPM I| Siemens Healthcare Inc. USAFrazer, Pa, United States
The following table shows the stat for a typical new software development project:
Phase Allocation (%)
Study and planning 8
System requirements analysis 6
System design 7
Infrastructure and prototype model 5
Reuse planning and Internet 6
Software requirements analysis 8
Software design 8
Software coding and testing 15
Software integration testing 10
System integration testing 15
System deployment 10
Audits 2
Saving Changes...
Andrew MakarProgram Manager| AMAKAR LLCOakland Township, Mi, United States
Stuart is spot on with the approach!
My company pursued a similar endeavor to improve our delivery timeline....however the data is confidential. If you work through your enterprise PMO and take a random sample of projects and gain the phased based data, you'll have a good understanding of your organization's time to deliver.
Hosting a workshop to identify root cause (fishbone diagram/cause/effect) will also identify opportunities for improvement.
"We cling to our own point of view, as though everything depended on it. Yet our opinions have no permanence; like autumn and winter, they gradually pass away."
