Results Scope Performance Domain

PMBOK v8 Definition

The Scope Performance Domain addresses the activities and functions associated with the work required to complete the project successfully. It ensures that the project includes all the work required and only the work required to complete the project successfully. This domain focuses on defining, developing, monitoring, controlling, and validating the project scope throughout the project life cycle.

Why It Matters for the Exam

The Scope Performance Domain is frequently tested because it establishes the foundation for all project work. PMI exam questions often test your ability to distinguish between product scope (features and functions of a product) versus project scope (work required to deliver the product), and to identify the correct processes for scope definition, validation, and control.

Key Points to Remember (for the exam)

• Key Concepts: Scope performance ensures that the project delivers what was agreed upon. The two primary components are product scope (the features and functions that characterize a product, service, or result) and project scope (the work performed to deliver a product, service, or result with the specified features and functions).

• Main Process - Plan Scope Management: Creates the scope management plan that documents how the project scope will be defined, validated, and controlled. This is the first process in the scope performance domain.

• Main Process - Collect Requirements: Defines and documents stakeholders' needs and requirements to meet the project objectives. Requirements become the foundation for the Work Breakdown Structure (WBS).

• Main Process - Define Scope: Develops a detailed description of the project and product. The key output is the project scope statement, which includes project deliverables, acceptance criteria, and project exclusions.

• Main Process - Create WBS: Subdivides project deliverables and project work into smaller, more manageable components. The key output is the scope baseline, which includes the approved project scope statement, WBS, and WBS dictionary.

• Main Process - Validate Scope: Formalizes acceptance of the completed project deliverables. This process occurs at the end of each phase or at project completion, and it differs from Control Quality (which checks correctness) versus Validate Scope (which checks acceptance).

• Main Process - Control Scope: Monitors the status of the project and product scope and manages changes to the scope baseline. Scope creep (unauthorized changes) is a key risk that this process prevents.

Typical PMI Exam Example

A project manager is developing the Work Breakdown Structure for a construction project. The sponsor asks to add a new feature that was not in the original requirements. What should the project manager do first?

Answer: The project manager should follow the Integrated Change Control process. Any change to the scope baseline requires a formal change request, which must be evaluated for impact on schedule, cost, and other constraints before approval.

PMI Exam Traps

• Trap: Confusing Validate Scope with Control Quality

• Reality: Validate Scope is about obtaining formal acceptance of deliverables from stakeholders. Control Quality is about verifying that deliverables meet specified quality requirements. Quality control happens before scope validation.

• Trap: Thinking scope creep is acceptable if the change is small

• Reality: Any unauthorized change to scope, regardless of size, is scope creep. All changes must go through the Integrated Change Control process.

• Trap: Confusing the project scope statement with the scope management plan

• Reality: The scope management plan describes how scope will be managed. The project scope statement describes the actual scope (what is and is not included).

• Trap: Believing the WBS is the same as the project schedule

• Reality: The WBS is a deliverable-oriented decomposition of work. The schedule shows when that work will be performed. The WBS is an input to schedule development.

Important PMI Connections

Quick Review Questions

1. What is the difference between product scope and project scope?

2. Which process ensures that the project includes all the work required and only the work required to complete the project successfully?

3. What is the key output of the Create WBS process, and what three components does it include?

4. When should Validate Scope occur during the project life cycle?

5. What is the correct process to follow when a stakeholder requests a change that would expand the project scope?

PMBOK v8 Reference

Section 2.2 - Scope Performance Domain