Scope Structure is the hierarchical and documented representation of the total scope of work, combining both:
Predictive elements (Scope Baseline, WBS, WBS Dictionary)
Adaptive elements (User Stories, Product Backlog) - Will discuss about these in the section 'Agile Project Management'
It answers:
What work needs to be done?
How is it organized?
How will it be delivered incrementally?
The Scope Baseline is the approved version of the scope that serves as a reference for comparison and control and comprises of;
Project Scope Statement
Work Breakdown Structure (WBS)
WBS Dictionary
These three together form the foundation for scope control.
The WBS is a hierarchical decomposition of the total project scope into smaller, manageable components.
It follows the principle: “Break the work until it becomes manageable and assignable”
Definition
The 100% Rule states that:
The WBS must include 100% of the work defined in the project scope, including all deliverables—internal, external, and project management work.
Key Aspects
Covers everything in scope
Includes project management activities
No extra work outside WBS
The 8–80 Rule suggests that:
A work package should ideally take between 8 and 80 hours of effort
Purpose
Ensures work is neither too large nor too small
If the work is more than 80 hours, it becomes too difficult to track and results in poor estimation
If the work is smaller than 8 hours, it results in too much micro-management
1. Solar Power Plant Project
1.1 Site Preparation
1.2 Procurement
1.2.1 Solar Panels
1.2.2 Inverters
1.3 Installation
1.4 Testing & Commissioning
Solar Plant
/ | \
Site Prep Procurement Installation
/ \
Panels Inverters
Level 1 → Project
Level 2 → Major Deliverables
Level 3 → Sub-deliverables
Level 4 → Work Packages
Lowest level = Work Package (manageable unit)
Define Scope → Create WBS → Develop Schedule → Estimate Cost → Execute & Control