Skip to content
PMPCAPM

Minimum Viable Product (MVP)

A Minimum Viable Product (MVP) is the smallest version of a product that can be released to customers to validate a business hypothesis and gather maximum learning with the least effort.

Share:

Explanation

The concept of MVP comes from lean startup methodology. The goal is not to build the smallest possible product but to build just enough to test whether the product concept is viable. An MVP includes only the core features needed to solve the customer's primary problem and gather feedback on whether the team is building the right thing.

The MVP approach reduces risk by shortening the time to market and minimizing investment before validating that customers actually want the product. Once the MVP is released, the team collects data and feedback, then decides whether to pivot (change direction), persevere (continue building on the concept), or stop. This build-measure-learn cycle is repeated to evolve the product.

For the exam, understand that MVP is about learning and validation, not about delivering a low-quality product. The MVP must be viable, meaning it must work well enough for customers to use it and provide meaningful feedback. It is the minimum set of features needed to test the value proposition.

Key Points

  • Smallest product that can validate a business hypothesis
  • Focused on learning and gathering customer feedback
  • Follows the build-measure-learn cycle from lean startup
  • Must be viable and usable, not just minimal

Exam Tip

MVP is about validated learning, not minimum effort. The product must work well enough for real customers to use it and provide feedback.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Part of

Agile & Hybrid

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.