PMO Design and Structuring

Managing potential and current PMO customers, orchestrating solutions to their needs, articulating and evolving the PMO value proposition, and designing and implementing PMO services.

5 minutes 5 Questions

In the PMI PMO Certified Professional (PMI-PMOCP) context, PMO Design and Structuring is the work of building a Project Management Office that fits an organization's strategy, culture, maturity and stakeholder needs. A PMO is not a one-size-fits-all function. It is shaped so that it delivers measur…

Concepts covered
Needs Assessment for PMO ServicesPMO Case Studies and Success StoriesContinuous Improvement of the PMO Value PropositionPMO Service CatalogTargeted Value Messaging for Customer GroupsPrioritization Framework for PMO Customer NeedsReviewing and Updating the PMO Value PropositionPMO Customer PersonasCustomer Feedback Loop for PMO Service ImprovementIdentifying and Categorizing PMO CustomersSurveys and Interviews to Assess PMO Customer NeedsMeasuring and Quantifying the PMO's ContributionStandardized Processes for PMO ServicesContinuous Service Improvement MechanismTailored Service Offerings for Customer GroupsCapturing and Analyzing PMO Customer RequirementsCustomer Check-Ins and Feedback MechanismsPromoting PMO Services to Potential CustomersArticulating PMO Benefits and ValueService Level Agreement Framework for PMO Offerings
Test mode:
Start practice test

PMI-PMOCP - PMO Design and Structuring Example Questions

Test your knowledge of PMO Design and Structuring

Question 1

Which statement best distinguishes a PMO service catalog from a service level agreement (SLA)?

Correct Answer: The catalog describes each offered service and how to request it; an SLA records agreed performance commitments with a customer.

A PMO service catalog is the published menu of services. It describes what each service is, who it serves, and how to request it. An SLA is a negotiated agreement with a specific customer that records committed performance levels such as turnaround times and quality targets.
The reversed option swaps the two roles. The catalog is not a list of future services only, since it describes services currently offered. Neither document is a charter appendix of authority or a definition of escalation paths. Those belong to the PMO charter and the governance framework.
Key concept: service catalog (what is offered and how to access it) versus SLA (agreed service performance commitments).

Question 2

An enterprise PMO leader is preparing for the executive committee's annual review, where sponsors will decide whether to renew the PMO's funding. The leader can present only one success story to support the PMO value proposition. Four case summaries are available. Which case summary provides the MOST credible evidence of value to the PMO's customers?

Correct Answer: Portfolio intake case: sponsors validated fewer late-stage cancellations against the baseline agreed before launch.

The sponsor-validated intake case is the most credible because the PMO's customers confirmed the business outcome against a baseline agreed before launch, so the value claim is independently verified and tied to what sponsors care about.
The PMO-calculated version relies on a self-reported, post-launch estimate, which invites doubts about bias and moving baselines. The reporting case measures outputs and efficiency (more dashboards, fewer preparation hours), not outcomes that sponsors value. The team development case shows internal PMO capability gains, not benefits delivered to customers.
Key concept: demonstrating PMO value through customer-validated, outcome-based evidence measured against a pre-agreed baseline.

Question 3

A portfolio PMO's service catalog lists each service by its internal process name, the responsible PMO owner and the SLA response time. Six months after launch, most requests still arrive as informal messages to individual PMO staff. Project managers say they cannot tell which service fits the problem they are facing. What does this pattern MOST likely indicate about the catalog?

Correct Answer: Entries describe PMO internal processes rather than the customer needs, outcomes and request steps each service addresses

The catalog is organized around the PMO's internal view: process names, owners and SLAs. Project managers cannot map their problems to a service, so they bypass the catalog and contact people they know. Entries should describe customer needs, expected outcomes and how to request each service.
Loose SLAs would not explain why customers cannot tell which service fits their problem. Too many services is not indicated, because the confusion comes from how entries are described, not how many there are. Stricter enforcement treats the symptom and ignores why customers avoid the catalog.
Key concept: customer-centric service catalog design that builds PMO value and adoption.

More PMO Design and Structuring questions
488 questions (total)
Practice 100 questions
One session at a time, always new questions