It happens that people close to the topic of software development ask: how is project work different from creating an MVP (Minimal Viable Product)? It is clear that in this case each questioner has his own context of the question - accordingly, it is necessary to answer it in different ways. However, to summarize, design and product development are very different from each other. In general, everyone. It's not so easy to grasp, so let's try to understand the problematic.
Problematization: project or product development
On the surface, software development is software development, whether it be a project or product development. There are some functional requirements - not always formalized. There are non-functional requirements that are often overlooked. There are developers, there is a certain conditional manager, and there is some methodology. Developers saw through the code, the manager cleared up obstacles in their path, and resolved issues with the end client / user / customer. At the end they show some kind of result. Sometimes, as they like to joke in the industry, the result even meets the requirements.
If you look a little deeper, it turns out that there are at least two huge areas of development that are fundamentally different from each other in literally everything: from goal-setting and the formulation of requirements to the processes of execution and delivery of the result.
These are the so-called "design" and "product" approaches to development. Each approach has its own characteristics, which we will look at a little later. So, if you dig even deeper into the product approach, then inside you can also highlight the development of MVP. Creation of MVP, being a part of product development, at the same time has its own characteristics and differs sharply from the development of an already full-fledged product with the aim of improving and expanding it. In addition to MVP, MMF (Minimum Marketable Feature) can also be highlighted. MMF is not the subject of this article, it just needs to be noted that they are different things. Unfortunately, they are often confused, saying that everything is MVP.
And now, having an idea of the existence of all these differences, you can dig deeper into the details and consider how exactly the approaches differ.
Project vs product
. , , .
: , , . “ ”, , .
, , .
, , , .
. , , . — , , , .
, , .
— -. , , : , , , , .
, . , , . — .
— 20% — 10%, — . , , — . — .
, .
, , - : , , . . : , , , .
. , , , , , . , V-model , .
, . , , . — , . — . — . ( ) — , .
. , , , . , , , , .
. . , : . , , , .
— . , . : . , , , . , .
: , , — . - “ ”. — , , , .
: . “” — , , . , “ ” .
. , , , , , , . , , , . , , .
, — . , , MVP . , — , , ..
. — “”.
— killer , . .
, , .
-, “ — — — — ” - . , , ( , ) , . — , . — — . , , — , . , “” : . , , , .
, — . , .
-, , , . — , — . — , . .
, , . , , , . . , - , full-stack .
— — . , , .
Back to MVP
, .
, MVP.
Minimal Viable Product — , “ ”, : , . , , MVP, — , .
- .
MVP — . , — , , !
, .
, , .
, , . , , , , , , . — , , , .
, , , . , , , , — . , — .
- , , , , — , !
, - ? - , . , , UX- , .
. . , , , , , ? , - . , - , , . — , .
— . - . , — . .
— , , .
, , . , .
, , MVP . — .
, . ?
. , , — . , , , , , , . , — .
— , , . , . . .
? .
. , , Scrum .
, MVP. : - ? , , -, , , , .
, Easy First, . . , , - — . , .
, — — . — , . . , - , . - , , , killer-features.
— . , . , — . Minimal Marketable Feature ( ).
MVP: , V-, . , , , . , .
use-cases , — . , — , . , . , , .
, MVP — , .
MVP — (shit and bricks). — . , “” — . -, , .
, MVP — . MVP , MMF . , . “ ”. - . — . , , .
, — — , . , , — . — , — . , , .
. , - MVP MMF. — , — , , . , , . , - , , , . , — , , . , , - , .
, , . — . . . , , , .
— , . .
, — — MVP . . — .
But at the same time, no one even tries to think about what result would be obtained if the team approached the issue in the product paradigm. Moreover, often neither the team nor the manager is simply not ready to work in this paradigm, they do not understand it. And, as a result, they simply do not know how to work differently.
But why this is happening, and what it takes to understand, be ready and be able to apply a product approach to development is a separate big conversation. Write in the comments if this topic is interesting and questions you would like to receive answers to.