Search


  Advanced Search
 
Popular Authors
  1. Michael Cooch
  2. Admin User
No popular authors found.
 
 »  Home  »  Human Resource Management  »  Programme Management Office (PMO): Headcount Sizing Guide
 »  Home  »  Programme / Project Management  »  Programme Management Office (PMO): Headcount Sizing Guide
Programme Management Office (PMO): Headcount Sizing Guide
By Michael Cooch | Published  10/27/2006 | Human Resource Management , Programme / Project Management | Rating:
Michael Cooch
Educated in New Zealand, Michael achieved an Honours Degree in Manufacturing and Industrial Technology. Since then he has gone on to achieve Project Management Professional (PMP), PRINCE2 Practitioner and a Diploma in Business Analysis (ISEB).

He has worked at the leading edge of the programme/ portfolio/ project control industry for 9 years and has experience working with Accenture, Unilever, London Stock Exchange, NHS, Morgan Stanley, Orange, TYCO and the Office of Rail Regulation. 

View all articles by Michael Cooch
To Finish
Once you have calculated your FTE Equivalent for each functional area you will have a total estimated headcount for your PMO.

There are a few important points to note before you head off and use these numbers in anger! ...namely;

- The mathematical model that supports this article has been derived from twenty-two best practice engagements (a new version will come out in 2008);
- You should remember to uplift/decrease your estimate based on the additional variables we discussed earlier;
- If your actual headcount is significantly lower than the estimate, common reasons are that your people are working a lot of uncharged overtime (remember an FTE is a Full Time Equivalent based off a standard working day - usually about 8 hours a day), you have strong support from senior management (and clear authority), you have strong automation of processes and tools or you have a very experienced and skilled workforce; and
- If your actual headcount is significantly higher than the estimate common reasons are that your team isn't working as efficiently as it could on direct PMO value-added activity or is doing work that isn't strictly PMO activity, you have an unskilled team, you have little support from senior management (or limited authority) or your level of automation is much lower than you think.

Whilst this isn't an exact science it should give you a good indicator of how big your PMO should be and some of the factors that contribute to it's size.
How would you rate the quality of this article?
1 2 3 4 5
Poor Excellent

Verification:
Enter the security code shown below:
img


Add comment
Comments
  • Comment #1 (Posted by an unknown user)
    Rating
    A brilliant article. A nice combination of useful summary information and detailed mathematical modelling.
     
  • Comment #2 (Posted by an unknown user)
    Rating
    I've been looking for the answer to this question for a number of years and this is the first time I've come across a comprehensive explanation of how to estimate a PMO headcount!
     
  • Comment #3 (Posted by an unknown user)
    Rating
    What a great article. This is the first article that answers the question in enough detail to support a decent estimate. Thanks!
     
  • Comment #4 (Posted by www.thatzcool.co.uk)
    Rating
    good job. well done
     
Submit Comment