The PMO was created by the organization to keep costs low and to maintain content control over the IT department. This PMO was set up with the most stringent rules that did not allow any deviation or process improvement. Whenever a PM submitted a document or put an artifact within its file share system, the leader of the PMO went over every single word, phrase, and task of that document. Project plans could not deviate from the template that the PMO had produced. And every time there was a deviation of any kind, the PMO lead had a meeting with the offending PM. This meeting was not a constructive meeting in any way. This meeting was set up to demonstrate the errors of the PM and to suggest, in very strong terms, that the PM, even the new PM, had to follow the rules and instructions of the PMO. For example:
- The PM had to use the prescribed MS Project template that was developed by the PMO even though each IT project had its own caveats.
- The PM had to present certain artifacts during certain phases. Presenting them too early or too late resulted in the project being put on hold until the PM corrected this.
- If the PM was brought in front of the PMO lead, the PM was not allowed to explain himself/herself regarding the deviation, no matter what the reason. This meeting was set up to demonstrate the errors of the PM.
If the PM made a similar error more than once, the PM was written up to Human Resources. Bob eventually left this organization.
- There was an introductory webinar for the PM defining the PMO and its methodology.
- A new PM “shadowed” another PM upon starting. Even though the new PM had projects, the shadow PM provided guidance.
- The PMO lead had regular PMO meetings and one-on-ones with the PMs to provide guidance and ensure all PMs understood the PMO process.
- New ideas from PMs to improve process were discussed in the group and if the idea provided added benefits or reduced time and costs, they were eventually introduced into the PMO.
- How are PMs and other employees treated?
- What is the culture?
- Does the PMO allow any improvements?
- Does the PMO lead have regular meetings and one-on-ones?
- What is the organization’s belief towards IT?
- Is there growth for the PM?
Whenever a PM is taking on a new role, whether it is at a new organization or a new division in the same organization, I have tried to illustrate the types of PMOs that are in existence and the ones that are obviously preferable.
When PMs are interviewing for a PM position, the obvious questions about the PMO should be:
I am open to discussion at any time on these blogs or anything else related to project management you would like to explore. If you would like to comment about this blog, please do so by posting on this blog or by responding in an email at Benny A. Recine. You may inspire a blog article. I look forward to your comments.
from BCNJ Member Blog Feed http://dlvr.it/98gF6h