The smallest version of a feature that is worth shipping and testing, stripped of everything that is not essential to the core user value. In quality and testing terms, identifying the minimum viable feature helps teams focus test coverage on what actually matters at a given moment, rather than spreading effort across the full eventual scope. It is a particularly useful concept in startups where testing resources are limited and the goal is to learn fast.
For example: shipping a payment flow that only supports one card type to test whether users will pay at all; or releasing a search function that only covers the most common query patterns before building edge case handling.
For example: shipping a payment flow that only supports one card type to test whether users will pay at all; or releasing a search function that only covers the most common query patterns before building edge case handling.
