"PMOs do not have to be big", says Ardi Ghorashy, PMP, PgMP, a partner with 80/20 Consulting Inc., Markham, Ontario, Canada, told me in a recent interview.
"The biggest mistake I think that companies make is that they create a monster organization with a lot of overhead and they also bring all the project managers to report into a PMO. That creates a big lump sum of cost sink that becomes very visible at the executive level every year when you review your finances.
Then the question will always get asked, 'What's the return value on this investment.' And project management has traditionally been very difficult and notorious at quantifying its ROI.
... By its nature, a PMO has such an encompassing impact on the organization that it affects a lot of things. You can't really measure it very easily. .... These days we say PMOs need to be implemented extremely thinly. [Thin] PMOs will demonstrate the value very, very easily."
What do you think? Are "thin" PMOs the way to go?
Hello Kelly and Ardi,
I read Ardi's post and I have to ask just how much experience either of you really have to make such a statement concerning large PMOs (not to be rude)?
I believe on the other hand that PMO value is scaled to the organization based on availability to serve. If the PMO is not producing then something else is wrong.
I resist the notion that a large PMO is wasteful. Just the opposite, its nirvana to those who believe in the value proposition of project management. Many PMOs would love to have more people that they can in-turn help the business with.
My Kindest Regards!
An "appropriate" PMO is the way to go. What determines the PMO's appropriateness? The effort required by the PMO to orchestrate the efficient and effective delivery and execution of an organization's critical strategic initiatives is the indicator. This effort will dictate the role(s) the PMO will have to assume to "make it happen" AND the number of resources required to "get the job done."