# Choosing MVP Features

From a vision point of view, it is quite difficult to decide what and which features don't make it as essential. Trying to understand what must be tested in the MVP and what doesn't justify making the cut is painful. Some developers might also tell themselves they can do it all so why not? Because that's not the point. That's how you burn out and stop trying the moment you hit a barrier. There are hundreds of articles and opinions, here I attached a few that might help you build a framework for making the right choice.

You can explore all the techniques for determining the best features for your MVP in this article:

[How to Prioritize MVP Features: 9 Useful Approaches](https://rubygarage.org/blog/prioritizing-mvp-features)

Detailed explanation of every single method used for determining best features for your MVP.
What method is best? That depends on you! Some of my favorite are taking a user-centric approach how it is described in this blog:

[How to Choose the Best Features for Your MVP](https://codingsans.com/blog/features-for-your-mvp)

This takes a user-centric approach to figuring out the best way to determine which features to include in your MVP. Using some general methods which are based on charts and frameworks because personally I am very visual. Take a look at both these charts, they give me a lot of clarity for determining what features must make it.

I recommend you do this process after a user-centric approach how it was described on the blog above.

[MoSCoW Prioritization and Scoping](https://online.visual-paradigm.com/diagrams/templates/moscow-method/moscow-prioritization-and-scoping/)

Another good chart to try to fit your features is this one:


by: https://clearbridgemobile.com/planning-a-minimum-viable-product-a-step-by-step-guide/