Steps for creating an ERP PMO

 1. Scope : At what level do you define “Project” – at the module level, submodule level, or the entire implementation is one project? A lot of people use module, but it’s really a function of what a PM should be able to handle. Before you create what will be handled by a PMO, you have to be clear about what the PMO will NOT handle and should be handled by the individual PMs at their own level.

2. Span of Operations: Remember that a PMO is only ONE step above the PM. If you need program management, create a Program Management Office. If you are working on something even bigger, don’t hesitate to create a portfolio management team. Determine the complexity and the experience of a team, and then arrive at a considered decision.

3. Workflows: Determine workflows for decisions, escalations and status updates. At the very least.

4. Information Sharing: Determine what information will be shared with the PMO, by whom and at what frequency.

5. Rules and Authority to Decide: Who has the authority to decide? What is the quorum? For instance, can a decision about a module be taken if the module lead was not in the meeting? Can a release be approved without the change manager?

These should cover the fundamental setup of a PMO.