Project scope is the work that must be done to deliver the product/service/result with the required features.
In simple words: scope tells what is included and what is excluded.
Clear scope is important because unclear scope causes delays, rework, and scope creep.
Example:
Scope management ensures:
It helps prevent:
A scope baseline is the approved version of scope against which performance is measured.
Typically includes:
Once baseline is set, changes should follow change control.
A WBS is a hierarchical decomposition of the total scope of work into smaller, manageable components.
Key ideas:
WBS is deliverable-oriented (focus on outputs), not just activities.
Access the complete note and unlock all topic-wise content
It's free and takes just 5 seconds
From this topic
Product scope refers to features/functions of the product. Project scope refers to all the work needed to deliver that product (requirements, design, development, testing, deployment). Clear distinction avoids confusion in planning.
Scope baseline is the approved scope used for control. It includes scope statement, WBS, and WBS dictionary. Changes to scope should be managed through change control.
Download this note as PDF at no cost
If any AD appears on download click please wait for 30sec till it gets completed and then close it, you will be redirected to pdf/ppt notes page.
Project scope is the work that must be done to deliver the product/service/result with the required features.
In simple words: scope tells what is included and what is excluded.
Clear scope is important because unclear scope causes delays, rework, and scope creep.
Example:
Scope management ensures:
It helps prevent:
A scope baseline is the approved version of scope against which performance is measured.
Typically includes:
Once baseline is set, changes should follow change control.
A WBS is a hierarchical decomposition of the total scope of work into smaller, manageable components.
Key ideas:
WBS is deliverable-oriented (focus on outputs), not just activities.
Benefits:
Work package: the lowest level in WBS, small enough to assign and estimate.
100% rule: WBS must include 100% of the work defined in the scope (including project management work).
Common exam line: “WBS ensures no work is left out and no extra work is added.”
A WBS dictionary provides detailed information about each WBS component/work package, such as:
It makes WBS more usable for execution.
Typical steps:
A Responsibility Assignment Matrix (RAM) maps:
A common RAM is RACI:
RACI reduces confusion and improves accountability.
Thus WBS is a foundation for planning.
Scope statement → Identify deliverables → Decompose → Work packages → Verify 100% rule
Get instant access to notes, practice questions, and more benefits with our mobile app.
A Work Breakdown Structure (WBS) is a hierarchical decomposition of total project scope into smaller, manageable components.
Benefits:
Scope statement → Identify deliverables → Decompose → Work packages → Verify 100% rule
Thus WBS is a foundation for planning and control.