Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Benchmarking Project Mmgt Effort

1 reply [Last post]
Fraser Haffenden
User offline. Last seen 21 years 6 weeks ago. Offline
Joined: 5 Mar 2003
Posts: 4
Groups: None
I have recently been reviewing a tender for developing a corporate email system. I was a little concerned over the effort that was being attributed to the Project Management task. As a result of my concern I did a quick look at similar project in my department and found that PM effort levels varied from 15% upto 30% of the budgeted effort. In light of this large variation of effort I want to get more data so I could refine the metric I would use. With this info I would then be able to provide evidence to negotiate the tender figure up or potentially down.

I would be grateful if anyone can provide me with a rough estimate from project that they have worked on or alternatively point me in the direction of a web site which contains such information.
TY
FraserH

Replies

Forum Guest
User offline. Last seen 2 years 27 weeks ago. Offline
Joined: 28 Jan 2009
Posts: 1
Groups: None
Speaking as a PM who might have put together the number from the opposite side, there are a number of ways the effort could be derived.

One way is to base the effort on a percentage of the overall project effort. This can result in a very large number. I find this method is used if theres a fair degree of project risk that makes it difficult to calculate a firm number.

Another way is to calculate how many days per week a PM intends to spend on a project. For instance, I might average 2 days a week managing a project over the project life cycle of 26 weeks = 52 man-days (416 hours). This number can fluctuate depending on the skillset of the team, the complexity of the project, reporting requirements, etc.

Finally, sometimes PMs assign time to resources for meetings and client communication, which sometimes get included into a total PM effort.

While this doesnt answer your question (ie similar project) I hope this helps you out in at least understanding how that number could be generated.

Rubin Jen, P. Eng, PMP