The Delivery of Any Project's Scope Should Generate Expected Value
PMBOK v8 Definition
The delivery of any project’s scope should generate expected value that is not only worth the time and resources invested, but also ideally maximized. Scope encapsulates a project’s expected value, making it the most important component of any project’s baseline. Project teams evaluate progress and adapt to maximize the expected value, ensuring value creation and meeting or exceeding target business objectives.
Why It Matters for the Exam
This principle appears frequently in PMI exam questions testing your understanding of the relationship between scope, value, and project success. You will encounter it in situational questions about scope management decisions, gold plating, scope creep, and when to recommend project termination. The exam tests whether you can distinguish between delivering scope (outputs) and delivering value (outcomes).
Key Points to Remember (for the Exam)
- Scope = Expected Value: Scope encapsulates a project’s expected value, making it the most important component of any project’s baseline.
- Value Maximization: The delivery of scope should generate expected value that is not only worth the time and resources invested, but also ideally maximized.
- Continuous Evaluation: Project teams evaluate progress and adapt to maximize the expected value throughout the project life cycle.
- Termination Decision: If misalignment persists or the project is unlikely to deliver the intended value, it may be best to terminate the effort.
- Scope Creep vs. Gold Plating: A value-focused approach prevents scope creep (unauthorized additions) and gold plating (adding extra features not required) to keep the project focused on delivering key outcomes.
- Waste Elimination: Focus on value involves avoiding unnecessary rework and other types of waste by optimizing workflows with acceptable risk exposure.
- Outcomes Over Deliverables: Shifting focus from deliverables to intended outcomes allows project teams to deliver on the project’s vision or purpose, rather than merely creating a specific deliverable.
Typical PMI Exam Example
A project team is developing a customer relationship management system. The customer requests additional reporting features not included in the approved scope. The project manager evaluates whether these features contribute to the intended business outcome of improved customer retention. The project manager determines the features would add unnecessary complexity without increasing expected value. Correct action: Reject the request to prevent gold plating and maintain focus on delivering key outcomes.
PMI Exam Traps
-
Trap: Confusing "scope baseline" with "project value"
- Reality: The scope baseline is the approved version of formal scope documents used for comparison; value is the outcome generated by delivering that scope.
-
Trap: Assuming all requested changes should be accepted if they add functionality
- Reality: Only changes that contribute to the intended value and align with business objectives should be considered; unnecessary additions constitute gold plating.
-
Trap: Thinking project success equals completing all deliverables on time and on budget
- Reality: Success requires delivering expected value that meets or exceeds target business objectives, not just completing deliverables.
-
Trap: Believing scope creep is acceptable if it improves the product
- Reality: Scope creep diminishes value by consuming resources without contributing to intended outcomes; a value-focused approach prevents uncontrolled changes.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Scope Performance Domain | Contains this principle | The Scope performance domain includes processes to ensure the project encompasses all required work and only the required work to maximize value |
| Business Case | Input / Justification | The business case defines intended outcomes; if misalignment persists, termination may be best |
| Quality | Complementary | Focus on value involves delivering required functionality and quality by optimizing workflows |
| Portfolio Management | Decision Support | Reliable value evaluation provides key data for decisions on which projects to select or continue |
| Requirements | Foundation | A requirement is a condition or capability necessary to satisfy a business need and deliver value |
Quick Review Questions
-
What is the relationship between scope and expected value according to PMBOK v8?
-
When should a project team recommend terminating a project based on the Focus on Value principle?
-
How does a value-focused approach help prevent scope creep and gold plating?
-
What is the difference between focusing on deliverables versus focusing on intended outcomes?
-
Why is scope considered the most important component of any project’s baseline?
PMBOK v8 Reference
Section 2.2 – Scope Performance Domain Section 3.4.1 – Project Impact