Project Scope Principle: The Foundation of Project Value Delivery

PMBOK v8 Definition

Project scope encompasses the work performed to deliver a product, service, or result with the specified features and functions. The project scope helps ensure that the expected value is achieved. Scope encapsulates a project’s expected value, so it is the most important component of any project’s baseline.

The principle of Adopt a Holistic View directly supports scope management by fostering alignment of all project activities with the overall project scope, preventing scope creep and misalignment by considering the entire project ecosystem.

Why It Matters for the Exam

The Project Scope principle appears in 15-20% of PMI exam questions, typically in situational scenarios where you must identify scope creep, determine proper scope definition, or select the correct baseline component. Questions often test your ability to distinguish project scope from product scope and recognize that scope is the primary driver of value delivery.

Key Points to Remember (for the exam)

• Scope = Value: Project scope encapsulates the expected value—it is the most important component of any project’s baseline
• Holistic View Prevents Creep: Applying a holistic view throughout the project life cycle ensures alignment and prevents scope creep
• Scope vs. Product Scope: Project scope = work performed; Product scope = features and functions of the deliverable
• Alignment with Strategy: Projects managed with a holistic view contribute positively to organizational strategic objectives
• Baseline Priority: Scope baseline is the foundation—schedule and cost baselines derive from it
• Creative Solutioning: A holistic view encourages focusing on organizational objectives rather than merely end deliverables, allowing simpler, more sustainable solutions
• Traceability: A holistic view makes it simpler to trace problems to their origins, enabling interdisciplinary problem-solving

Typical PMI Exam Example

A project manager is reviewing stakeholder requests for additional features mid-project. The sponsor wants to add functionality that would require 30% more work. The project manager should:

• First: Evaluate if the new scope aligns with organizational objectives
• Then: Assess impact on the scope baseline
• Action: Request a formal change request through integrated change control

This scenario tests your understanding that scope changes must be evaluated holistically against value delivery.

PMI Exam Traps

• Trap: Confusing project scope with product scope

  • Reality: Project scope = work performed; Product scope = features/functions of the deliverable

• Trap: Thinking scope creep is acceptable if the change adds value

  • Reality: Any scope change without formal change control is scope creep, regardless of value

• Trap: Believing scope is defined only once at project initiation

  • Reality: Scope is progressively elaborated throughout the project life cycle, but changes must follow change control

• Trap: Assuming the scope baseline includes only deliverables

  • Reality: The scope baseline includes the scope statement, WBS, and WBS dictionary—not just deliverables

Important PMI Connections

Quick Review Questions

1. Why does PMBOK v8 state that scope is the most important component of any project’s baseline?

2. A project team discovers that a stakeholder has been adding small features without formal approval. What principle is being violated, and what is the first action the project manager should take?

3. How does the principle "Adopt a Holistic View" specifically prevent scope creep?

4. What is the difference between project scope and product scope? Provide one example of each.

5. During a phase review, the project sponsor asks if the project is still on track to deliver value. Which baseline component should the project manager examine first, and why?

PMBOK v8 Reference

Section 3.3 – Adopt a Holistic View (Principles) Section 2 – Project Management Performance Domains (Project Scope definition) Glossary – Project Scope definition

Key Exam Takeaway: Remember that scope = value. Every scope-related question on the PMI exam ultimately tests whether you understand that scope is the vehicle for delivering organizational value, and that the holistic view principle is your primary tool for keeping scope aligned with that value.