Predictive Approach Quality: Scope Baseline and WBS Fundamentals

PMBOK v8 Definition

Quality is an integral attribute of scope and can include both functional and nonfunctional requirements of the product, service, or result. In projects using a predictive approach, the Work Breakdown Structure (WBS), together with the project scope statement and the WBS dictionary, constitutes the scope baseline. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of scope management in predictive projects. Questions often ask you to identify the components of the scope baseline, distinguish between WBS levels, and recognize that quality requirements are embedded within scope definition rather than treated as a separate activity.

Key Points to Remember (for the exam)

• Scope Baseline Components: Project scope statement + WBS + WBS dictionary (all three together form the scope baseline)
• 100% Rule: The total of work at the lowest levels must roll up to higher levels so nothing is left out and no extra work is performed
• Work Package: The lowest level of the WBS with a unique identifier
• Quality as Scope Attribute: Quality includes both functional and nonfunctional requirements—it is NOT a separate process in predictive projects
• Decomposition Limit: Excessive decomposition leads to nonproductive management effort, inefficient resource use, and difficulty aggregating data
• Rolling Wave Planning: Details for future deliverables are deferred until the deliverable or subcomponent is agreed upon
• WBS Purpose: States project objectives and defines required deliverables in a structured, hierarchical manner

Typical PMI Exam Example

A project manager is creating the WBS for a construction project using a predictive approach. The sponsor asks how quality requirements will be tracked. The project manager explains that quality is an integral attribute of scope and is captured within the functional and nonfunctional requirements documented in the project scope statement, which is part of the scope baseline along with the WBS and WBS dictionary.

PMI Exam Traps

• Trap: Confusing the WBS with the project schedule

  • Reality: The WBS is a hierarchical decomposition of scope work, not a time-sequenced plan

• Trap: Thinking quality management is separate from scope definition in predictive projects

  • Reality: Quality is an integral attribute of scope and includes functional and nonfunctional requirements

• Trap: Believing the WBS alone constitutes the scope baseline

  • Reality: The scope baseline includes THREE components: project scope statement, WBS, and WBS dictionary

• Trap: Assuming all WBS levels must be fully decomposed at project initiation

  • Reality: Rolling wave planning allows deferring detailed decomposition for future deliverables

Important PMI Connections

Quick Review Questions

1. What are the three components that together form the scope baseline in a predictive approach project?

2. What is the 100% rule as it applies to the WBS, and why is it important?

3. How is quality addressed within scope management in a predictive approach?

4. What is the lowest level of the WBS called, and what does it have that identifies it uniquely?

5. When might a project management team use rolling wave planning for WBS development?

PMBOK v8 Reference

Section 2.2.2.4 – Develop Scope Structure Section 5.4 – Scope Baseline Components Section 5.3.3.2 – WBS and 100% Rule