Best Practices: Establishing a Program Management Office
Centralizing Control: 6 Best Practices for Establishing a PMO
Managing by project and adding rigor to overall IT governance can make your organization transparent and go far in aligning technology objectives with business strategy—making establishment of a program management office, or PMO, a long-term cost-saving measure as well as a way to increase excellence. The road to these lofty goals, however, is paved with gotchas that can cause false starts and waste time and money. Fortunately, many errors are preventable, as we’ll discuss. One truth that must be dealt with upfront, however, is that in some organizations we’ve worked with that have established PMOs, the role of IT has changed dramatically. Whether that change is healthy or disruptive depends largely on how well the new PMO functions and meshes with the enterprise.
The responsibilities of PMOs are diverse but commonly include setting standards and methodologies for project management as well as oversight to ensure smooth and on-budget project execution. There is, however, no one-size-fits-all PMO. When setting up a program office, a designated executive or group must define roles and responsibilities, and the structure of the PMO must be customized to the needs of the organization.
Here are our top six best practices to help you achieve this vision.
Table of Contents
3 Author’s Bio
4 Time to Build
4 Figure 1: Why Establish a PMO?
5 Figure 2: Basic PMO Org Chart
9 Figure 3: SLA Elements
11 Making the PMO a Reality: Customer Portal Example
12 Figure 4: Basic PMO Implementation Plan
13 Introducing a Program Management Office



Be the first one to comment.