Customer Example: Iterative Scope Refinement with MVP

PMBOK v8 Definition

In adaptive environments, project scope is refined through successive iterations, focusing on main product goals to satisfy customer expectations. The minimum viable product (MVP) is created with minimum features collected in a backlog, enabling rapid feedback and adaptation to changes. Requirements are collected as user stories, prioritized in a backlog, and scope description occurs at the beginning of each iteration for adaptive and hybrid approaches.

Why It Matters for the Exam

This concept appears frequently in situational questions about development approach selection, especially when the scenario involves uncertain requirements, new markets, or evolving customer preferences. The PMI exam tests your ability to recognize when an iterative approach with MVP is appropriate versus predictive approaches. Questions often present a project scenario and ask which development approach or scope management technique should be applied.

Key Points to Remember (for the exam)

• MVP Definition: Minimum Viable Product created with minimum features collected in a backlog, not a fully-featured product
• Scope Refinement: Scope is refined through different iterations, not defined completely upfront
• Backlog Role: Requirements are collected as user stories, then prioritized in a backlog
• Feedback Mechanism: Rapid feedback from MVP enables better support with adaptation to changes
• When to Use: Projects with little information about customer preferences, new markets, or evolving requirements
• Iteration Timing: Scope description occurs at the beginning of each iteration for adaptive and hybrid approaches
• Common Confusion: Confusing MVP with a prototype—MVP is a functional product with minimum features, not a demonstration model

Typical PMI Exam Example

A software company plans to release a mobile app in a new market where customer preferences are unknown. The project manager recommends an iterative approach with a clear MVP created from minimum features in a backlog. This approach enables rapid feedback from early users and supports adaptation to changing market needs through successive iterations.

PMI Exam Traps

• Trap: Confusing MVP with the final product

  • Reality: MVP contains only minimum features to gather feedback; scope expands through iterations

• Trap: Assuming iterative approaches always require full requirements upfront

  • Reality: Adaptive approaches define scope at the beginning of each iteration, not at project start

• Trap: Thinking MVP is only for software projects

  • Reality: MVP concept applies to any adaptive project with uncertain requirements, including non-digital products

• Trap: Confusing user stories with traditional requirements documents

  • Reality: User stories are collected and prioritized in a backlog; traditional requirements are documented upfront

Important PMI Connections

Quick Review Questions

1. In an adaptive project with uncertain customer preferences, what is the primary purpose of creating a minimum viable product (MVP)?

2. When should scope description occur for projects using an adaptive development approach?

3. What is the format for collecting requirements in an adaptive environment, and where are they stored?

4. A project for a new city park has a tight timeline but clear requirements. Should an iterative approach with MVP be used? Why or why not?

5. How does the iterative approach with MVP support adaptation to changes in customer expectations?

PMBOK v8 Reference

Section 2.2.2.3 – Define Scope Section 4.2.3 – Hybrid Approaches Section 3.3 – What to Tailor Customer Example 2 (Software project with MVP)