Home / Project Management Office / Execution Excellence / Should You Divide PMO Functions?

Should You Divide PMO Functions?

“PMO” can mean a lot of different things these days—maybe too many things? P can stand for project, program, or portfolio. And even then, the nature of the PMO will vary from one organization to another. In a post for the Association for Project Management, Emma-Ruth Arnaz-Pemberton wonders if it is time to “divorce” some key functions of the PMO in order to provide tighter focus on pertinent areas.

It ultimately comes down to if the PMO really needs to be the central integrator of all things that right now fall under the PMO blanket, from benefits realization to knowledge management. Is standardization and oversight provided by one body a true necessity? Or is it time to let some sub-disciplines cultivated by PMOs to go bloom on their own? Arnaz-Pemberton sides with the former camp over the latter, as she believes a strong PMO is the only way to stop new silos from sprouting up. And she may very well be right. But what do you think?

You can view the original post here: https://www.apm.org.uk/blog/pmchat-divorcing-the-pmo/

About John Friscia

John Friscia is the Editor of Computer Aid's Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

How to Build PMO Capabilities in Small-to-Medium IT Organizations

Process and structure should fit the size of the organization, regardless of other factors. If …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time