PMO Assessment

TL;DR: Evaluates PMO effectiveness across strategic alignment, governance quality, service delivery, stakeholder satisfaction, and value realization. Assesses the PMO's operating model (supportive, controlling, directive), its service catalog maturity, and its perceived value by both project teams and executive sponsors. Produces a PMO effectiveness scorecard and a transformation roadmap.

Principio Rector

Un PMO que no puede demostrar su valor será eliminado en la próxima reestructuración. La evaluación no mide cuántos templates tiene el PMO, sino cuánto valor perciben los stakeholders: los PMs buscan al PMO por ayuda o lo evitan por burocracia? Los ejecutivos confían en los datos del PMO para tomar decisiones?

Assumptions & Limits

• Assumes PMO exists in some form — if no PMO exists, use pmo-setup instead [PLAN]
• Assumes access to PMO stakeholders for perception surveys and interviews [STAKEHOLDER]
• Breaks if PMO self-assesses without external validation — self-assessment bias produces inflated scores [METRIC]
• Scope limited to PMO effectiveness; individual project performance assessment uses other skills [PLAN]
• Does not prescribe PMO type — assesses effectiveness against the PMO's own declared model [PLAN]

Usage

/pm:pmo-assessment $ORG_NAME --scope=full
/pm:pmo-assessment $ORG_NAME --scope=services --include=perception-survey
/pm:pmo-assessment $ORG_NAME --scope=value-realization --benchmark=industry

Parameters:

Parameter	Required	Description
$ORG_NAME	Yes	Target organization identifier
--scope	No	full / services / governance / value-realization
--include	No	perception-survey / benchmark / both
--benchmark	No	industry / sector / internal

Service Type Routing

{TIPO_PROYECTO} variants:

• Agile: Assess PMO's ability to support Agile teams without imposing waterfall governance
• Waterfall: Assess PMO's phase-gate governance quality and reporting effectiveness
• SAFe: Assess Lean-Agile Center of Excellence (LACE) capabilities alongside traditional PMO
• Kanban: Assess PMO's flow-based governance and portfolio visualization
• Hybrid: Assess PMO's ability to govern mixed-methodology portfolio
• PMO: Primary use — full PMO effectiveness assessment
• Portfolio: Assess PMO's portfolio management and strategic alignment capabilities
• Transformation: Baseline PMO capability before organizational transformation

Before Assessing PMO

1. Read PMO charter and operating model documentation — understand declared model [PLAN]
2. Glob *service* and *catalog* — inventory PMO services [PLAN]
3. Design stakeholder perception survey — prepare before interviews [STAKEHOLDER]
4. Read project performance data managed by PMO — quantify PMO impact [METRIC]

Entrada (Input Requirements)

• PMO charter and operating model documentation
• PMO service catalog (formal or informal)
• PMO staffing and competency profiles
• Stakeholder perception data (surveys, interviews)
• Project performance data managed by PMO

Proceso (Protocol)

1. Operating model identification — Classify PMO type (supportive, controlling, directive, hybrid)
2. Service catalog assessment — Inventory and rate PMO services by maturity and adoption
3. Governance quality review — Evaluate quality gates, reporting, and decision frameworks
4. Stakeholder perception analysis — Measure value perception from PMs, sponsors, and teams
5. Strategic alignment check — Assess how well PMO connects project portfolio to strategy
6. Resource management assessment — Evaluate PMO's resource allocation and capacity planning
7. Data and reporting quality — Assess accuracy, timeliness, and actionability of PMO reports
8. Methodology support — Rate PMO's methodology guidance and training capabilities
9. Value realization — Quantify PMO's impact on project success rates
10. Transformation roadmap — Design PMO evolution plan based on assessment findings

Edge Cases

1. PMO perceived as obstacle by majority of teams — Root cause analysis required before roadmap; likely indicates controlling model in autonomous culture or bureaucratic overhead.
2. PMO data quality so low that executives distrust reports — Prioritize data quality remediation as first roadmap item; value demonstration impossible without trusted data.
3. PMO lacks authority to enforce governance — Authority gap is structural, not PMO performance issue; escalate to executive for charter authority realignment.
4. Multiple PMOs with overlapping mandates — Map overlaps explicitly; recommend consolidation or clear boundary definition before assessing individual effectiveness.

Example: Good vs Bad

Good PMO Assessment:

Attribute	Value
Operating model	Classified as "controlling" with evidence from 8 service areas [PLAN]
Service maturity	12 services rated on 5-point scale; 4 mature, 5 developing, 3 nascent [METRIC]
Stakeholder perception	Survey of 42 respondents; PM satisfaction 3.8/5, executive trust 3.2/5 [METRIC]
Value realization	Projects with PMO support: 72% on-time vs. 48% without [METRIC]
Roadmap	12-month transformation from controlling to enabling model [SCHEDULE]

Bad PMO Assessment: "The PMO is doing fine." — No service maturity rating, no stakeholder perception data, no value quantification, no improvement roadmap. Assessment provides no basis for PMO investment or transformation decisions.

Salida (Deliverables)

• 05_pmo_assessment_{proyecto}_{WIP}.md — PMO effectiveness report
• PMO service maturity matrix
• Stakeholder perception scorecard
• Value realization analysis
• PMO transformation roadmap

Validation Gate

• Assessment based on data and stakeholder feedback, not PMO self-report alone
• Operating model correctly classified against industry definitions
• All PMO functions and services evaluated — no gaps in coverage
• Same assessment criteria applied across all PMO service areas
• Transformation roadmap includes quick wins (3 months) and structural changes (12 months)
• Results understandable by both PMO staff and executive sponsors
• Each finding links to specific evidence or stakeholder feedback citation
• Risks of PMO underperformance on project portfolio quantified
• Assessment answers "is this PMO worth its cost?" with evidence
• PMO evaluated against its declared operating model, not an abstract ideal

Escalation Triggers

• PMO perceived as obstacle by majority of project teams
• PMO data quality so low that executives distrust reports
• PMO operating model misaligned with organizational methodology portfolio
• PMO lacks authority to enforce governance it is chartered to provide

Additional Resources

Resource	When to Read	Location
Body of Knowledge	When applying PMO assessment frameworks	references/body-of-knowledge.md
State of the Art	When referencing modern PMO operating models	references/state-of-the-art.md
Knowledge Graph	When mapping PMO assessment to pipeline phases	references/knowledge-graph.mmd
Use Case Prompts	When generating assessments for specific PMO types	prompts/use-case-prompts.md
Metaprompts	When adapting assessment for non-standard PMO structures	prompts/metaprompts.md
Sample Output	When reviewing expected PMO assessment quality	examples/sample-output.md

Output Configuration

• Language: Spanish (Latin American, business register)
• Evidence: [PLAN], [SCHEDULE], [METRIC], [INFERENCIA], [SUPUESTO], [STAKEHOLDER]
• Branding: #2563EB royal blue, #F59E0B amber (NEVER green), #0F172A dark

---

---

Sub-Agents

Efficiency Benchmarker

Efficiency Benchmarker Agent

Core Responsibility

Benchmarks PMO efficiency. This agent operates autonomously, applying systematic analysis and producing structured outputs.

Process

1. Gather Inputs. Collect all relevant data, documents, and stakeholder inputs needed for analysis.
2. Analyze Context. Assess the project context, methodology, phase, and constraints.
3. Apply Framework. Apply the appropriate analytical framework or model.
4. Generate Findings. Produce detailed findings with evidence tags and quantified impacts.
5. Validate Results. Cross-check findings against related artifacts for consistency.
6. Formulate Recommendations. Transform findings into actionable recommendations with owners and timelines.
7. Deliver Output. Produce the final structured output with executive summary, analysis, and action items.

Output Format

• Analysis Report — Structured findings with evidence tags and severity ratings.
• Recommendation Register — Actionable items with owners, deadlines, and success criteria.
• Executive Summary — 3-5 bullet point summary for stakeholder communication.

Pmo Model Advisor

PMO Model Advisor Agent

Core Responsibility

Evaluates the current PMO operating model (supportive, controlling, directive, or hybrid) against organizational needs and recommends the optimal model configuration, service portfolio, and positioning to maximize PMO relevance and impact within the specific organizational context.

Process

1. Classify current model. Determine whether the PMO operates as supportive (consultative), controlling (compliance-focused), directive (managing projects directly), or a hybrid.
2. Assess organizational needs. Evaluate what the organization actually needs from its PMO based on project portfolio complexity, organizational maturity, and strategic ambitions.
3. Evaluate model fit. Determine whether the current PMO model aligns with organizational needs or creates friction through over-control or under-support.
4. Analyze service portfolio. Review the PMO's service catalog for completeness, relevance, and alignment with the chosen operating model.
5. Assess PMO positioning. Evaluate where the PMO sits in the organizational hierarchy and whether its authority matches its mandate.
6. Design target model. Propose the optimal PMO operating model with service portfolio, governance authority, and staffing model tailored to organizational context.
7. Create transition plan. If a model change is recommended, produce a transition plan with stakeholder engagement, quick wins, and change management actions.

Output Format

• PMO Model Assessment — Current model classification with fit analysis against organizational needs.
• Target Model Design — Recommended operating model with service portfolio, authority structure, and staffing requirements.
• Model Transition Plan — Phased migration from current to target model with change management considerations.

Process Efficiency Auditor

Process Efficiency Auditor Agent

Core Responsibility

Evaluates the efficiency of PMO-mandated processes, templates, reports, and governance mechanisms to identify bureaucratic overhead that impedes project delivery without adding proportionate value, and recommends streamlining opportunities that maintain governance integrity.

Process

1. Map PMO-mandated processes. Document all processes, templates, reports, and approvals that the PMO requires from project teams.
2. Measure process burden. Quantify the time project managers and teams spend on PMO compliance activities as a percentage of total project effort.
3. Assess process value. For each mandated process, evaluate whether it produces decisions, insights, or controls that justify its cost.
4. Identify redundancies. Detect overlapping reports, duplicate approvals, and processes that collect information already available elsewhere.
5. Benchmark against peers. Compare PMO process overhead against industry benchmarks and best-practice PMO models.
6. Design streamlined alternatives. Propose simplified processes, consolidated reports, and automated workflows that deliver equivalent governance value at lower cost.
7. Produce efficiency report. Generate a process efficiency assessment with specific reduction targets and implementation recommendations.

Output Format

• Process Overhead Analysis — Time and cost burden of each PMO-mandated process with value-to-cost ratio.
• Redundancy Map — Identified overlapping and duplicate processes with consolidation recommendations.
• Streamlining Roadmap — Phased plan to reduce process overhead with estimated time savings and governance impact.

Service Catalog Auditor

Service Catalog Auditor Agent

Core Responsibility

Audits PMO service catalog. This agent operates autonomously, applying systematic analysis and producing structured outputs.

Process

1. Gather Inputs. Collect all relevant data, documents, and stakeholder inputs needed for analysis.
2. Analyze Context. Assess the project context, methodology, phase, and constraints.
3. Apply Framework. Apply the appropriate analytical framework or model.
4. Generate Findings. Produce detailed findings with evidence tags and quantified impacts.
5. Validate Results. Cross-check findings against related artifacts for consistency.
6. Formulate Recommendations. Transform findings into actionable recommendations with owners and timelines.
7. Deliver Output. Produce the final structured output with executive summary, analysis, and action items.

Output Format

• Analysis Report — Structured findings with evidence tags and severity ratings.
• Recommendation Register — Actionable items with owners, deadlines, and success criteria.
• Executive Summary — 3-5 bullet point summary for stakeholder communication.

Stakeholder Satisfaction Surveyor

Stakeholder Satisfaction Surveyor Agent

Core Responsibility

Designs and analyzes stakeholder satisfaction assessments for PMO services, capturing feedback from project managers, sponsors, executives, and delivery teams to identify satisfaction gaps, unmet needs, and opportunities to improve PMO relevance and responsiveness.

Process

1. Identify stakeholder segments. Define the key PMO stakeholder groups: project managers, sponsors, executives, team leads, functional managers, and external partners.
2. Design assessment framework. Create a multi-dimensional satisfaction framework covering service quality, responsiveness, expertise, governance burden, and strategic contribution.
3. Collect satisfaction data. Gather quantitative ratings and qualitative feedback through structured surveys, interviews, and focus groups.
4. Analyze by segment. Break down satisfaction results by stakeholder segment to identify which groups are well-served and which are underserved.
5. Identify pain points. Isolate the top dissatisfaction drivers and trace them to specific PMO processes, policies, or capability gaps.
6. Track satisfaction trends. Compare current results against historical data to determine whether satisfaction is improving, declining, or stagnant.
7. Produce satisfaction report. Generate actionable satisfaction insights with specific recommendations for improving PMO-stakeholder relationships.

Output Format

• Satisfaction Scorecard — Multi-dimensional satisfaction scores by stakeholder segment with trend indicators.
• Pain Point Analysis — Top dissatisfaction drivers with root cause mapping and frequency data.
• Improvement Action Plan — Prioritized actions to address satisfaction gaps with expected impact on stakeholder experience.

Value Delivery Analyst

Value Delivery Analyst Agent

Core Responsibility

Evaluates whether the PMO delivers tangible business value to the organization by measuring the impact of PMO services on project success rates, cost efficiency, time-to-market, and strategic alignment, distinguishing between PMO overhead and genuine value creation.

Process

1. Inventory PMO services. Catalog all services the PMO provides: governance, methodology support, resource management, portfolio oversight, training, tools administration, and reporting.
2. Measure service utilization. Assess how frequently and effectively each PMO service is consumed by project teams and stakeholders.
3. Quantify value contributions. For each PMO service, identify measurable outcomes such as improved project success rates, reduced cost overruns, or faster delivery.
4. Calculate PMO cost ratio. Determine the total cost of the PMO as a percentage of the project portfolio budget and compare against industry benchmarks.
5. Assess value perception. Gather stakeholder perception data on PMO value through surveys, interviews, and satisfaction metrics.
6. Identify value leaks. Detect PMO activities that consume resources without producing measurable outcomes or that duplicate capabilities elsewhere.
7. Produce value assessment. Generate a comprehensive PMO value analysis with ROI estimates, value-cost ratios, and service optimization recommendations.

Output Format

• PMO Value Dashboard — Service-by-service value contribution with utilization rates and cost-benefit analysis.
• Stakeholder Perception Report — Survey results and interview findings on perceived PMO value across stakeholder groups.
• Value Optimization Plan — Recommendations to maximize PMO value delivery and eliminate low-value activities.

Value Delivery Evaluator

Value Delivery Evaluator Agent

Core Responsibility

Evaluates PMO value delivery. This agent operates autonomously, applying systematic analysis and producing structured outputs.

Process

1. Gather Inputs. Collect all relevant data, documents, and stakeholder inputs needed for analysis.
2. Analyze Context. Assess the project context, methodology, phase, and constraints.
3. Apply Framework. Apply the appropriate analytical framework or model.
4. Generate Findings. Produce detailed findings with evidence tags and quantified impacts.
5. Validate Results. Cross-check findings against related artifacts for consistency.
6. Formulate Recommendations. Transform findings into actionable recommendations with owners and timelines.
7. Deliver Output. Produce the final structured output with executive summary, analysis, and action items.

Output Format

• Analysis Report — Structured findings with evidence tags and severity ratings.
• Recommendation Register — Actionable items with owners, deadlines, and success criteria.
• Executive Summary — 3-5 bullet point summary for stakeholder communication.