Keywords consisting of only 1 word are not allowed

PrisilaSH

The types of MVPs that I am going to list should not be understood as rigid categories they are coordinated to understand whether what we need at a given moment is more like "almost nothing" in Jared Spool's example or an "almost finished" product, or something in between. MVP P stands for Proof An MVP in its purest sense is focused on learning things we don't know its fundamental requirements are to start from a question, be economical and iterative. The fact of being a concrete "thing", however, is not a requirement. For this reason James O'Brien argues that we should use the term Minimum Viable Proof what we are looking for is proof that we are going in the right direction, or in the wrong one. We're not trying to make something beautiful or lasting. This meaning is particularly suited to the initial stages of a project, when we are exploring the possibility that an idea might actually have an audience and satisfy a need. For example, a web form might be enough to gather public interest for an application that we have yet to develop.

ETP test, test, test Another thing is when we need a concrete product, because we photo editing servies want to put it in front of real users in a context similar to that of the future final product at this point our MVP has the additional requirement of being functional compared to what it promises to be do, that is, it must actually enable users to satisfy the need for which it was designed. This is the case of the classic illustration by Henrik Kniberg, where we see the MVPs for a customer who needs to travel from point A to point B henrik -kniberg-and-Henrik Kniberg For this type of MVP Kniberg proposes the definition of Earliest Testable Product the important attribute is that our product because it is a product now is testable , therefore it works and allows the user to do the thing he wants in this move from.



A to B  All other principles remain intact starting from a question, being economical, and above all iterating. In fact, what we tend to forget is that at the beginning the path looks like this the customer's reaction to MVP will determine the next step and so onThe customer's reaction to MVP will determine the next step, and so on. That is, the path is not traced at the beginning each subsequent step is determined by the results of the previous one, and we do not know how many steps it will take. Users perform tests and provide us with positive and negative feedback that allows us to determine the next question to answer.