What best defines a Minimum Viable Product (MVP)?

• A. An application that includes all possible features and meets all end-user needs.
• B. A prototype with no real functionality.
• C. A fully finished product delivered after many sprints.
• D. An application that requires the least development effort and time, but still provides useful features to stakeholders.

Answer: (D)

Minimum Viable Product is about delivering the smallest version of a product that still provides real value to users, with just enough features to be usable and to learn from real feedback. This approach aims for the fastest possible release cycle—minimal development effort and time—while ensuring the product offers something useful to stakeholders so they can validate assumptions and guide future enhancements. It isnures that you’re not waiting to perfect every feature or building a fully finished product before testing the idea.

This is why the option describing the least effort and time while still providing useful features best fits. It isn’t about a feature-complete or polished product, nor about a non-functional prototype, nor about waiting through many sprints to release something. The MVP focuses on learning quickly with the smallest viable investment.