Organizational Breakdown Structure (OBS)

A tree-structured view of the project organization that shows how specific work items are assigned to the organizational units responsible for doing them.

Key Points

  • Displays the project's organizational units in a hierarchy and how they relate to the work.
  • Maps WBS elements or activities to departments, teams, or roles that will perform the work.
  • Supports creation of a responsibility assignment matrix (RAM/RACI) and resource planning.
  • Clarifies accountability, reporting lines, and coordination across functional groups.

Example

On an ERP implementation, the OBS lists the PMO at the top, with Functional Finance, Supply Chain, Data Migration, QA, and Training teams beneath. WBS work packages such as "Configure GL," "Convert legacy data," and "User training" are linked to the Finance, Data Migration, and Training teams, respectively, showing who is responsible for each package.

PMP Example Question

Which artifact provides a hierarchical view that links project activities to the organizational units responsible for executing them?

  1. Work Breakdown Structure (WBS)
  2. Organizational Breakdown Structure (OBS)
  3. Resource Breakdown Structure (RBS)
  4. Responsibility Assignment Matrix (RAM)

Correct Answer: B - Organizational Breakdown Structure

Explanation: The OBS shows the project organization and maps work to performing units. The WBS decomposes deliverables, the RBS categorizes resources, and the RAM cross-references WBS and OBS to assign responsibilities.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build complete project plans in minutes with AI

Learn how to use AI to create charters, WBSs, schedules, risk registers, and executive reports while staying in control. This course gives you prompt templates and practical workflows based on real project work. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More