CAPM Practice: Explain when it is appropriate to use an adaptive approach

MVP is a core adaptive/lean concept: deliver the smallest version of a product that delivers enough value to test with real users and gather actionable feedback. The MVP is not the final product — it is a learning vehicle. Feedback from the MVP informs whether to continue, pivot, or abandon the product direction, minimizing investment in uncertain directions.

**Why not B:** MVP has no meaningful connection to procurement management. Procurement management concerns selecting vendors, writing contracts, and managing supplier relationships — none of which involve iterative product delivery or user feedback validation. The MVP concept originated in lean startup thinking and is applied to product development decisions, not procurement activities.

**Why not C:** In predictive (waterfall) projects, minimum scope is defined at initiation to control cost and schedule, but this is a scope reduction constraint rather than a learning mechanism. An MVP is specifically designed to generate validated learning from real users — a purpose absent from predictive scope definition. The MVP's defining characteristic is its role as a hypothesis test, not simply a small scope.

**Why not D:** Scope reduction in traditional project management is typically done to recover schedule or reduce cost, not to enable market learning. While both involve delivering less, the intent and mechanism are entirely different. MVP scope is chosen based on what is sufficient to generate useful feedback; traditional scope cuts are driven by constraints. Conflating the two misses the learning-oriented purpose that defines the MVP concept.