Tue May 18 2021 15:42:24 GMT-0400
Minimum Viable Product for Developers is a method that allows to focus attention on the process that the user would carry out instead en the “awesome features” that your app could have to be.
It reduces dramatically amount of features necessary to validate your product.
Usually, requirements overloaded designs add numerous tasks to development spring that result in features that are irrelevant to end users.
Keep a good method to identify what is really important reduce user friction and save a lot of time in developing proceess.
This method is based on “MVP for Geeks by Will Dayble”. To do it ready to use for online collaborative team I added some features like:
This method permit:
You need resolve three simple and super easy steps:
Create a User Story. It will define what your MVP should resolve for user. Consider it as a contract of MVP.
Write in whiteboard every piece of data information that you think is necessary show or receive from the user. Group every field in sections of your app. Don’t worry how it will be presented to user, just write data and sections as text group.
When you finished, append sticker in every section and field.
Keep green sections and fields, remove everything in red and consider how to show information in yellow to make to more remarkable your brand.
Finally, draw lines representing the user’s journey through your app.
In this step, you will have a very reduce data requirements. It’s helps to:
Feel free to put your creative rolling and sketch your (mobile first) wireframe.
Using Whiteboards for Confluence.