What is a PMO, what types exist, and how do I set one up?

What a PMO does

A PMO exists so that projects across the organisation are run in a consistent, visible way. Typical services:

• Standards: a light method, templates for charters, schedules, risk registers and status reports.
• Reporting: one view of all projects, their status, cost and risk, for leadership.
• Governance: stage gates, change control, approval thresholds.
• Planning support: scheduling, estimating and project controls expertise.
• Capability: coaching and training for project managers.
• Portfolio support: helping leadership choose and prioritise projects, and balancing people across them.

Names vary: you will see project, programme, portfolio and enterprise PMOs. A project PMO supports one large project, a programme office supports a group of related projects, and an enterprise or portfolio office serves the whole organisation.

The three PMO types

These are points on a scale, not boxes. Many PMOs are controlling for reporting and governance but supportive for methods. Choose the lowest level of control that fixes your actual problem; you can tighten later.

Where the PMO reports also matters. A PMO that reports to a single department tends to serve that department's projects; one that reports to an executive sponsor or a leadership group finds it easier to set standards across the organisation and to bring difficult portfolio decisions to the table.

How to set up a PMO, step by step

1. Name the problem. Write one or two sentences: for example, "leadership cannot see which projects are late" or "every project reports differently". The PMO's first services must address this.
2. Find a sponsor. A senior leader who wants the outcome and will back the standards when teams push back.
3. List the projects. Build a simple inventory: name, owner, budget, start, finish, status. This is often the first useful product.
4. Pick three to five services. For example: a project inventory, a monthly status report, a risk register template and a gate review for new projects.
5. Set minimum standards. Decide what every project must have (a charter, a schedule with milestones, a risk register, a monthly report) and what is optional. Size the standard to the project: a small task board should not carry the same paperwork as a large capital project.
6. Choose one tool and one reporting cycle. Shared data beats a pile of spreadsheets emailed on Fridays.
7. Run a pilot. Apply the standards to a few willing projects for two or three cycles, then adjust.
8. Measure and publish value. Track things you can count: projects reporting on time, projects with a baseline, decisions made at gates.

A starter service plan

The timings are a suggestion. A small organisation may do all of this in a few weeks; a large one may need longer for the pilot.

PMO roles and how to show value

A small PMO usually needs three kinds of skill, whether held by one person or several:

• PMO lead: owns the service plan, works with the sponsor, and chairs portfolio and gate reviews.
• Project controls or planning: builds and checks schedules, runs earned value and risk analysis, and keeps baselines honest.
• PMO analyst or coordinator: maintains the project inventory, collects updates, produces the monthly report, and keeps templates current.

Showing value is the PMO's ongoing job. Pick a few measures you can count from your own data and report them every quarter, for example: the share of active projects with an approved charter and baseline, the share of status reports submitted on time, the number of schedules passing quality checks, and the number of decisions taken at gate reviews (including projects stopped or reshaped). Avoid claiming credit for project outcomes you cannot link to a PMO action. A short note of decisions the PMO's data made possible is often more convincing than any metric.

Common mistakes when setting up a PMO

• Starting with a thick methodology. A large process manual before any visible help makes the PMO look like overhead.
• Reporting for its own sake. If nobody makes a decision from a report, drop it or change it.
• One standard for every project size. Scale requirements to risk and value.
• No sponsor. Without senior backing, a controlling PMO becomes a supportive one nobody uses.
• Collecting data in many places. Re-keying spreadsheets each month burns the PMO's time and introduces errors.
• Policing instead of helping. If project managers see the PMO only when something is late, they will hide problems. Offer planning help early, and the reporting gets easier.

How to do this in Critova

Critova supports projects at three levels (a simple task board, a timeline with dependencies and milestones, and full project controls), which lets a PMO scale its standards to each project. Portfolios group projects, and eleven dashboards, including executive, portfolio, cost, schedule and risk, give leadership one view, alongside a printable status report per project and DCMA 14-point schedule checks. Sponsors get free viewer seats. See the portfolio features and the ready-made project templates.