How would you rate the overall maturity of your PMO in terms of structure, processes, tools, and performance tracking?
Not Mature4%
Slightly Mature50%
Moderately Mature28%
Very Mature15%
Fully Mature3%
74 PARTICIPANTS
Not Mature4%
Slightly Mature50%
Moderately Mature28%
Very Mature15%
Fully Mature3%
Presentation of proposal materials11%
Relationship43%
Simplicity of packaging17%
Price22%
Roadmap5%
Other
We don't use any 3rd-party scripts17%
We can't monitor or restrict 3rd-party script behavior on our website31%
We trust vendors based on initial reviews21%
We test scripts periodically17%
We use Web Privacy Management, WebAppSec, or PriSec Software9%
We outsource website privacy and app security monitoring services3%
Other (please describe)
No selling.
No recruiting.
No self promotion.
Rules of EngagementFAQsPrivacy
© 2025 Gartner, Inc. and/or its affiliates. All rights reserved.
As you develop your PMO, ensure you have reasonable limits for the size of the project relative to the amount of PMO requirements. Example, 1 person project for 8 weeks, only internal labor certainly doesn't require the level of Project Management that an SAP deployment to 20,000 USERS over 8 countries, with hundreds of various project participants. In my experience, those working on projects vs. those in the PMO have vastly different opinions on the level of project management tools required per the size of the actual project. Every company will be different on what is appropriate, but I would recommend you start off with "light" PMO touch where you can or you will lose a lot of enthusiasm from non-PMO participants. It's a delicate balance of the right amount of tracking, and still getting the work done. If the labor hours for completing PMO paperwork exceed the hours working on the project something has gone horribly wrong.