Build an enterprise-level project management system (05)-do you need PMO?

When the number of projects in the organization begins to grow, the risk of project failure begins to increase. Due to resource gaps, regulatory vulnerabilities may occur. In this case, it is very important to define the project management process, set metrics, and introduce best practices. For many companies, this means creating a functional organization called PMO.

Specifically, when you find the following signs, you should consider setting up PMO:

1. The project scope is constantly changed during the project lifecycle;

2. Project delays or overspending have become common;

3. A group of resources are managed by multiple projects at the same time;

4. The scale and scope of the project lead to the company's frequent need to hire subcontracting or suppliers from outside;

5. the project owner must submit the Integration Report and measurement results on behalf of all projects;

6. Clear communication between the customer and the management should come from a single channel;

7. The project needs resources from different geographic regions.

 

You can use the above evaluation criteria to measure and see if your organization needs PMO?