Question

Describe the difference between a minimum viable product approach and providing all requirements before deployment by using examples in your everyday life.

Answer 1

Solution:

MVP -(Most Viable Product )--> In this agile model everyone is concentrating on the development in phases in this MVP is the phase where we will cover the important features or function

Example: If we are developing an online store our base requirement is like user should log in, add the product to cart and then check out. This is the core function of any online Store. There can be many more features but these are the most important things without that your application has no significance. This is like if we complete developing these features we can release. But this is not the complete Application we can go on with versions of release on top of the MVP to complete the Application complete features like suggestions top picks and many more.

providing all requirements before deployment:

This is like we will give complete requirements of an application and start developing that.

EXAMPLE: Take the same example as the above case after the development of MVP we will release products to the users. But when we go on with all the requirements approach we need to wait until the development of all the features of the application. Like if we can deliver an MVP in 6 months complete requirements development takes years to do that and then here we don't figure out which we need to start implementation so there is no classification of importance which will result in the delay of the application version 1 release.

Best approach is MVP.