{"id":15185,"date":"2020-03-03T00:00:00","date_gmt":"2020-03-03T06:00:00","guid":{"rendered":"https:\/\/blog.planview.com\/when-an-it-pmo-transitions-to-epmo\/"},"modified":"2020-03-03T00:00:00","modified_gmt":"2020-03-03T06:00:00","slug":"when-an-it-pmo-transitions-to-epmo","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/when-an-it-pmo-transitions-to-epmo\/","title":{"rendered":"When an IT PMO Transitions to EPMO"},"content":{"rendered":"
\n
\"When<\/div>\n<\/figure>\n

<\/p>\n

Is your IT project management office (PMO) functioning on a department level, program level, or project level? <\/p>\n

<\/p>\n

Regardless, there is one thing all IT PMOs have in common: They are constantly inundated with urgent requests and demands for technology updates, technical support, and seamless implementations from all across their organizations. <\/p>\n

As technology has expanded into every aspect of business operations, IT PMO roles have also expanded to take a higher-level view of enterprise-wide projects and resource allocation—especially as businesses grow.<\/p>\n

When your conventional PMO’s responsibilities evolve to manage IT projects linked to important executive-level business objectives, it may be time to think about transitioning to an enterprise project management office (EPMO). Here’s a look at the different values offered by a PMO versus those of an EPMO, and how to manage this transition when the time comes.<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n