What is the concept of a minimally viable product, or MVP?

Avoid implying that the Product Owner is solely responsible for deciding which stories define the scope of a minimally viable product. Other members of the team often offer technical, usability, and feedback mechanism considerations that should be considered when determining MVP scope.

A minimally viable product, or MVP, represents the product features that need to be completed for a product to launch initially. The initial release is usually developed for a small set of users who provide feedback that can be incorporated into future sprints. As a Scrum Master, I prompt teams to collaborate and define the scope of MVP at the beginning of development so that I can project when it will be ready for release and work with the Product Owner to find the right set of users for it.

This approach reduced risk, as problems and opportunities arise earlier in the process concerning usability and bugs. Early user feedback helps the Product Owner validate their user story prioritization and make adjustments as necessary. In some cases, it generates excitement and increases buy-in within user groups.