According to the PMBOK® Guide, specifically within the Plan Risk Management process, the Risk Breakdown Structure (RBS) is a critical tool for ensuring all potential risks are identified and categorized systematically.
Definition: An RBS is a hierarchically organized depiction of identified project risks. It is arranged by risk category and subcategory, which identifies the various areas and causes of potential risks.
Structure: Similar to a Work Breakdown Structure (WBS), the RBS starts at a high level (e.g., Technical, External, Organizational, Project Management) and decomposes into more specific levels.
Level 0: All Project Risks.
Level 1: Broad categories (e.g., Technical Risk).
Level 2: Specific subcategories (e.g., Requirements, Technology, Complexity).
Purpose: The primary benefit of the RBS is that it helps the project team to look at the project from different perspectives during the Identify Risks process. It prevents " tunnel vision " by forcing the team to consider risks across all domains of the project environment. It also provides a framework for summarizing and reporting risk data.
Comparison with other options:
A. Risk register: This is a document that captures the details of individual identified risks, including their description, owner, probability, impact, and planned responses. While it uses the categories defined in the RBS, the register is a list/database, not a hierarchical depiction of categories.
C. Risk management plan: This is the overarching plan that describes how risk management activities will be structured and performed. While the RBS is often included as a component of the Risk Management Plan, the plan itself is a narrative and procedural document, not the specific hierarchical chart.
D. Risk category: This is a singular classification (e.g., " External Risk " ). While the RBS is made of risk categories, a single category does not represent the entire hierarchical depiction asked for in the question.
