Organizational Breakdown Structure (OBS) for the PMP Exam

What Is the Organizational Breakdown Structure?

The Organizational Breakdown Structure (OBS) is a hierarchical representation of the project organization arranged to show the relationship between project activities and the organizational units responsible for performing them. While the WBS breaks down the project by deliverables, the OBS breaks it down by organizational responsibility.

On the PMP exam, the OBS typically appears in questions about resource management, cost accounting, and responsibility assignment. Understanding how it complements the WBS and RAM gives you an advantage on integration-focused questions.

OBS vs. WBS: The Relationship

The WBS and OBS are mirror structures that intersect at the work package level:

WBS answers: "What work needs to be done?" It decomposes the project scope into deliverables and work packages.
OBS answers: "Who is responsible for the work?" It maps organizational units — departments, teams, or groups — to work packages.

When you overlay the OBS onto the WBS, the intersection produces cost accounts. A cost account is the point where a specific work package meets a specific organizational unit, enabling precise cost tracking and accountability.

How the OBS Supports Resource Planning

The OBS provides several resource management benefits:

Workload visibility — Managers can see how much work is assigned to each department, preventing overallocation.
Cost aggregation — Costs can be rolled up by organizational unit, enabling department-level budget tracking.
Accountability mapping — Every work package has a clear organizational owner, reducing ambiguity about who is responsible for delivery.
Communication structuring — The OBS helps determine who needs to be included in which project communications.

Building an OBS

An OBS follows the same hierarchical decomposition principles as the WBS:

Level 1 — The project itself
Level 2 — Major organizational divisions (e.g., Engineering, Marketing, Operations)
Level 3 — Departments within those divisions (e.g., Software Development, Quality Assurance)
Level 4 — Teams or workgroups (e.g., Frontend Team, Backend Team)

The depth of the OBS depends on the project's complexity and the organization's structure. A small project may need only two levels; a program spanning multiple business units may require four or more.

OBS and the Responsibility Assignment Matrix

The OBS directly feeds the Responsibility Assignment Matrix. While the RAM assigns individuals to tasks, the OBS provides the organizational context. If a RAM shows that "John Smith" is responsible for a work package, the OBS shows that John operates within the Quality Assurance department under the Engineering division.

This connection is important for escalation paths and decision authority. When issues arise, the OBS clarifies the management chain above the responsible individual.

PMP Exam Applications

OBS-related PMP questions tend to focus on:

Cost control — How are costs tracked by department? Through the OBS-WBS intersection (cost accounts).
Resource conflicts — A department is overallocated. The OBS makes this visible by aggregating workload by organizational unit.
Organizational process assets — An existing OBS from previous projects can be used as a template for new projects.

Exam tip: if a question mentions "cost accounts," think of the OBS-WBS intersection. This cross-reference is a reliable signal that the question is testing your understanding of how organizational structure connects to project scope.

Study Strategy

Do not study the OBS in isolation. Learn it alongside the WBS, RAM, and Resource Breakdown Structure. These four structures form an integrated framework for understanding who does what work, how costs are tracked, and where resources are allocated. Our PMP topic reviews cover each structure and their interrelationships with exam-focused explanations.