Minimum viable/Marketable/Lovable product
MVP, MMP and MLP are defined as solution with incremental features, each of which meets the defined criteria of solution-market fit.
Basis the impact and effort required for the development of Epics and User stories, we decide on what minimum features should we release the solution with, in each increment.
Minimum Viable Product (MVP): The minimum viable product is the first version of the released solution, which consists of minimum set of must-have (core) features, catering to the most important Epics. Since a Minimum Viable Product is created with the minimum core features, it can be developed at a faster pace. Moreover, an MVP helps in providing the data or feedback loop from our early adopters or other groups to enhance the product.
Minimum Marketable/Saleable Product (MMP/MSP): Based on the feedback from the users, the MVP is enhanced into a Minimum Marketable/Saleable Product, which consists of the features that add competitive value advantage to the solution.
Minimum Lovable Product (MLP): The minimum loveable product has the features to make users fall in love with it. It targets to offer solution that appeals to the user's emotion beyond fulfilling their need.
Product roadmap
Solution/Product Roadmap in Agile Methodology is defined as release plan of each increment of the solution. The first release is made with Minimum Viable Product. Subsequently, new epics are added in next releases. The new release also includes feature enhancement on earlier releases, based on the user feedback.
The Product/solution roadmap is developed with details on what all User stories and Epics to be considered in each releases of the solution, as it moves from Minimum Viable Product (MVP) to Minimum Lovable Product (MLP). Though the roadmap must be prepared and agreed on before the development starts for the first release (MVP), it may undergo change based on feedback from stakeholders (including users), over the development process. User stories and Epics considered in each releases of the solution is called "Scope" of the development.
Sprint management
In Agile Methodology, the features to be included in a sprint undergoes constant prioritization and de-prioritization, based on the feedback from stakeholders. However, no changes are expected once the sprint starts. Within a sprint, it follows the same development cycle of design-build-test.
Each Epic planned for the next release are detailed in terms of User stories written in form of expected features of the solution. These features are consolidated as Product Backlog by Product Manager/Product Owner. Each features in the Product Backlog are assigned a priority number based on Impact and Effort of the development. Features with top priorities, are moved into the Sprint Backlog, after considering the developers' availability. Sprint Backlog serves as the Scope for the development, and the developers starts working on designing, developing and testing those features. The development is reviewed during Daily Scrum Meeting for addressing roadblocks or do recalibrations (if required).