It all comes down to documenting the reason for building this product. Bring your team to the table and ask yourselves the following questions?
Once the problems have been defined in the previous stage, you now start to create a story around the pain areas.
Based on all the activities above, do impact and priority matrix to decide the first set of features to include in the MVP. Decide the bare minimum features that are required for the product to be taken to the market. It should be able to :-
Once the MVP is ready and before you start to market to clients, it is very important for clients to know that there is a future for this product and that this is not just a one off product concept. Clients will respond better if you can show them a future road map of features that they can expect going forward. Set an update release commitment like monthly / quarterly and so on to inspire confidence. build this commitment into your build and release stage of your DevOps life cycle.