Taking the minimum viable product approach
For a successful solution, always put the customer first, while also taking care of architectural constraints. Think backward from the customers' needs, determine what is critical for them, and plan to put your solution delivery in an agile way. One popular method of prioritized requirement is MoSCoW, where you divide customer requirements into the following categories:
- Mo (Must have): Requirements that are very critical for your customers, without which the product cannot launch
- S (Should have): Requirements that are the most desirable to the customer, once they start utilizing the application
- Co (Could have): Requirements that are nice to have, but their absence will not impact upon the desired functionality of the application
- W (Won't have): Requirements that customers may not notice if they are not there
You need to plan an MVP for your customer with must-have requirements and go for the...
