Please login or join to subscribe to this thread
You question can be answer from multiple visions. The first one is to take into account the enterprise architecture. Organizations are open and adaptable systems then enteprise architecture is critical to survive. The enterprise architecute is defined following the strategy. So, the common is to have business, applications, technology layers at a minimum inside the architecture. Each one can have its own PMO and on top of that, "sitting to the right of the father" is the EPMO (enterprise PMO). The EPMO integrates all layers for all portfolio/programs/projects inside the organization. An unique demand management process must be share by all the PMOs. Relating your second part of the post, to be or not to be a "project managers provider" depends on the type of PMO you have in place. In my actual work place we are project manager providers and we consider that each project manager can manage 3 projects at the same time then it is the indicator to decide when to hire or not a new project manager. About the PMIS, each portfolio/program/project manager must manage it having the needed information updated.
It is time to hire new PMs when the capacity you have insufficient for the legitimately concurrent level of work they need to manage. Ideally, as part of this you will be establishing a career path for PMs so that if you hire them at a junior level, they can progress to take on more and more responsibilities.
Quantify what the current effort involved with PMIS administration is and what the planned near term usage for it is likely to be - that will help you determine whether you need someone specifically focused on maintaining the tools. The complexity of the tools themselves will also be a good guide - some are too difficult to master (from an admin perspective) for someone to do it off the side of their desks. In general, the greater the utilization of the tools and the broader the scope of their usage, the greater the need for such support.
Finally as far as scaling up the services provided by the PMO, it comes back to the relative maturity level of the governance bodies and what their priorities are. If there is a need to expand the scope of the intake process, that will require more effort on the part of the PMO, the decision making governance bodies and those submitting projects for consideration. While you can staff up for the former, the latter two will likely be perceived as "more work", so the benefits will need to significantly outweigh the costs.
Kiron and Sergio provided solid advise but I would add one more thing: I feel you are at a stage now were you need to hire an SME or two to help with scaling your PMO. When the PMO maturity is low (Early Stages), scaling can be challenging in many ways.
"... needs some help when reviewing project requests that come in outside of major projects that are planned well in advance, and how to structure the review of those requests as they come in..."
This is a common issue at the beginning. From my experience, this part can not be controlled and planned 100%. There are picks and there are silent days.
Projects are coming all the time, some are pushed as urgent, and so on.
But constantly asking/reviewing the organization what is in the funnel helps a lot.
Also, I think each organization scales up in not linear fashion. Also in generating projects. There is a physical cap. Which is good.
We kept employing people into PMO until we reached a balanced workload - simply organization could not bring any more projects over what it was, so we do not need to scale up anymore.
At a certain moment we had to scale down a person or two, then got a new one again. But this is quite normal.
Of course, getting approval for employing people is always a challenge, but I believe You can justify it with the current bandwidth of people and project streams.
I watched a good webinar the other day that might help you:
Session 3: The Right PMO for You
A lot depends on "what" a PM is expected to do, how much support they receive from their sponsor and key stakeholders, as well as the "heaviness" of the organization's PM standards and practices.
I've seen it vary anywhere from only one project per PM to up to five or six depending on the factors I listed as well as the complexity and other contextual characteristics of the project.
Anything over that, and the PM will purely be reactive or firefighting.
Please login or join to reply