TWRT Image
Home » TWRT » PMO Setup Framework: How to Build a PMO from Scratch

PMO Setup Framework: How to Build a PMO from Scratch

Introduction

PMO = Project Management Office. É o “centro de excelência” de gestão de projetos da empresa.

Without a PMO:

  • ❌ Cada projeto usa processo diferente
  • ❌ Sem padrão de documentação
  • ❌ Portfolio invisível
  • ❌ Reinventar a roda cada vez

With PMO:

  • ✅ Processos padronizados
  • ✅ Portfolio visível e governado
  • ✅ Reutilização de templates, ferramentas, conhecimento
  • ✅ Taxa de sucesso de projetos sobe 40%+

This article covers:

  • Organizational Structure (Roles)
  • 5 core processes
  • Implementation Roadmap (90 days)
  • Maturity Metrics

What is a PMO?

PMO = a corporate entity that centralizes, standardizes, and governs project management.

Responsibilities:

Area Examples
Governance Approve projects, milestones, and changes
Portfolio Overview of all projects, prioritization
Processes Document templates, checklists, and workflows
Tools Implement and maintain PM software; integration
Support Training police officers, coaching, problem-solving
Metrics Data collection, dashboard, executive reporting

3 Types of PMO

Type 1: PMO Compliance (Minimum)

Tamanho: 1–2 pessoas
Custo: ~R$ 100–150k/ano
Foco: Documentação, processos, compliance

Responsibilities:

  • Charter Template
  • Documentation (minimum requirements)
  • Monthly Reports for Executives

Ideal for: SMEs, those new to project management.

Type 2: Operational PMO (Medium)

Tamanho: 3–5 pessoas
Custo: ~R$ 300–500k/ano
Foco: Governança, portfolio, suporte

Responsibilities:

  • Portfolio management (prioritization, capacity planning)
  • Governance (approval, gates, CCB)
  • Support for police officers (coaching, problem-solving)
  • Metrics (dashboard, KPIs)

Ideal for: Companies with 10 or more concurrent projects.

Type 3: Strategic PMO (Full)

Tamanho: 5–10 pessoas
Custo: ~R$ 800k–1.5M/ano
Foco: Portfolio estratégico, transformação, inovação

Responsibilities:

  • All of the above +
  • Strategic Alignment (OKRs vs. Projects)
  • Organizational transformation (methodology, tools)
  • Research and innovation (new methodologies, tools)
  • Value Analysis (ROI, Payback)

Ideal for: Multinational companies with a complex portfolio (50+ projects).


Organizational Structure

PMO Organizational Chart (Operational, 5 people)

PMO Director (reports to CEO/VP Operations)
│
├─ Portfolio Manager (1 person)
│  └─ Responsibility: Portfolio visível, priorização, capacity planning
│
├─ Governance Manager (1 person)
│  └─ Responsibility: Gates, CCB, documentação, compliance
│
├─ Project Analyst (1–2 people)
│  └─ Responsibility: Suporte aos PMs, coaching, problem-solving
│
└─ Tools & Metrics Specialist (1 person)
   └─ Responsibility: Ferramenta PM, integração, dashboard, relatórios

5 Core Processes

Process 1: Project Initiation (Approval)

Gate: Alguém propõe novo projeto
↓
Charter: Preenchido (objetivo, escopo, orçamento, timeline)
↓
Review: PMO + Patrocinador revisam
↓
CCB: Aprovação formal (go/no-go)
↓
Resultado: Projeto autorizado ou rejeitado

Process 2: Portfolio Management

Monthly:
├─ Revisar status de todos os projetos (red/amber/green)
├─ Reclassificar prioridades (mudanças de negócio)
├─ Capacity planning (temos recursos?)
└─ Decisão: Continue / Pause / Kill

Output: Portfolio dashboard (executivos sabem status)

Process 3: Gate Review (Control)

Cada projeto tem 3–5 gates:
├─ Gate 0: Charter aprovado (go/no-go para início)
├─ Gate 1: Design revisado (qualidade OK?)
├─ Gate 2: Development completo (testes passou?)
├─ Gate 3: Ready for production (go-live?)
└─ Gate 4: Lessons learned (projeto encerrado?)

Cada gate: Checklist + sign-off

Process 4: Change Control

Quando algo muda (escopo, cronograma, orçamento):

Request: PM submete change request
↓
Impact Analysis: Que impacto? (cronograma, budget, risco)
↓
CCB Review: Aprovado ou rejeitado?
↓
Implementation: Se aprovado, implementa
↓
Log: Registra em change log (auditoria)

Process 5: Reporting & Governance

Weekly:
├─ Status report (cada PM reporte status via template)

Monthly:
├─ Portfolio review (all projects, red/amber/green)
├─ Escalation review (riscos, bloqueadores críticos)
└─ Metrics dashboard (SPI, CPI, on-time %, on-budget %)

Quarterly:
├─ Executive briefing (CEO/CFO)
├─ Strategic alignment (OKRs vs. projetos)
└─ Capacity planning (ano que vem)

90-Day Roadmap

Month 1: Diagnosis & Design

Week 1:

  • [ ] Interview stakeholders (CEO, CFO, VPs, PMs)
  • [ ] Assess the current situation (processes, tools, pain points)
  • [ ] Select PMO type (Compliance / Operational / Strategic)

Semana 2–3:

  • [ ] Design the organizational structure (org chart, roles, responsibilities)
  • [ ] Map out 5 processes (charter, portfolio, gates, change, reporting)
  • [ ] Define metrics (PMO KPIs)

Week 4:

  • [ ] Submit the plan to management (for approval)
  • [ ] Recruit/assign people to the PMO
  • [ ] Schedule kickoff times

Month 2: Processes & Tools

Week 5:

  • [ ] Document 5 processes (1 page each, including a flowchart and a template)
  • [ ] Create templates (charter, status report, risk register, etc.)

Week 6:

  • [ ] Train the PM team on processes (2-hour workshop)
  • [ ] Feedback and adjustments

Week 7:

  • [ ] Choose a tool (Asana, ClickUp, Smartsheet, Jira, etc.)
  • [ ] Tool setup (organization, project, fields, integrations)

Week 8:

  • [ ] Train the team on the tool (hands-on)
  • [ ] Importar 2–3 projetos pilotos
  • [ ] Intensive support

Month 3: Operations & Metrics

Week 9:

  • [ ] Conduct the first portfolio review (monthly ritual)
  • [ ] Hold the executive briefing (CEO/CFO) first
  • [ ] Collect feedback

Week 10:

  • [ ] Implement a KPI dashboard (SPI, CPI, on-time %, on-budget %)
  • [ ] Set up automatic reporting (weekly status, monthly summary)

Week 11:

  • [ ] Run the first CCB (change control board)
  • [ ] Document changes, decisions, and lineups

Week 12:

  • [ ] Retrospective (What worked? What could be improved?)
  • [ ] Plan for the next 90 days (iteration)

Metrics & KPIs

PMO Health Metrics

Metric Target How to Measure
Adoption Rate 100% of police officers using the tool Jira/Asana logs (active in the last 7 days)
Compliance 100% of projects with a charter Monthly audit (yes or no)
On-Time Rate 85%+ of projects completed on time Percentage of projects delivered on schedule
On-Budget Rate Over 90% of projects stay within budget Percentage of projects that did not exceed their budget
Change Requests Processed < 5 dias Average time for review and approval of a change
Executive Satisfaction NPS 7+ Quarterly Survey (Is the PMO Adding Value?)

Common Mistakes

Mistake 1: An overly cumbersome PMO (bureaucracy)

❌ “Toda mudança precisa de 15 aprovadores”

→ Resultado: Lentidão, equipe frustrada.

✅ Escalação proporcional (mudança pequena = rápida, mudança grande = mais rigor).

Mistake 2: A PMO without executive sponsorship

❌ “PMO é projeto de TI, CEO não se importa”

→ Resultado: Ninguém segue processos, PMO vira decoração.

✅ CEO + CFO visem portfolio (5 min/semana, status visual).

Mistake 3: Undocumented processes

❌ “Sabemos o que fazer, não precisa documentar”

→ Resultado: Quando pessoa sai, conhecimento sai com ela.

✅ Documentar (1-page process flowchart + template).


Checklist

Month 1:

  • [ ] Diagnosis made
  • [ ] PMO type defined (Compliance/Operational/Strategic)
  • [ ] PMO organizational chart designed
  • [ ] Executive approval obtained
  • [ ] Assigned/Recruited Individuals

Month 2:

  • [ ] 5 documented cases
  • [ ] 10+ templates created
  • [ ] Selected tool
  • [ ] A team trained in processes
  • [ ] Team trained on the tool
  • [ ] 2–3 projetos pilotos rodando

Month 3:

  • [ ] Monthly portfolio review scheduled and conducted
  • [ ] Executive briefing scheduled and held
  • [ ] KPI dashboard created
  • [ ] CCB scheduled and run
  • [ ] Feedback collected, adjustments made

FAQ

Q: Is a PMO necessary?

R: Depende. Se > 10 projetos simultâneos ou complexos, SIM. Se < 5, pode começar simples (1 person).

Q: Does the PMO handle projects or processes?

A: Both. The PMO manages projects (oversees the portfolio, manages project gates) and maintains processes (templates, methodology).

Q: How much does a PMO cost?

R: Compliance PMO: R$ 100–150k/ano (1 person). Operational: R$ 300–500k. Strategic: R$ 800k–1.5M.


Final CTA

A well-structured PMO = a 40% improvement in project success rates. If you want to start a PMO, schedule a 90-minute session to design a structure tailored to your company. Otherwise, download the 90-day roadmap.

Upcoming readings:
Project Governance | Project Management Software Comparison

Scroll up