Differences
This shows you the differences between two versions of the page.
|
se:project:milestones:m7 [2018/12/02 15:34] emilian.radoi |
se:project:milestones:m7 [2024/12/19 23:21] (current) emilian.radoi |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== M7 - 07.01.19 ====== | + | ====== M7 - 08.01.25 ====== |
| - | <hidden> | ||
| - | ====== More Validation and MVP ====== | ||
| - | A minimum viable product (MVP) is the the most pared down version of a product that can still be released. An MVP has three key characteristics: | + | ====== Minimum Viable Product - MVP ====== |
| - | It has enough value that people are willing to use it or buy it initially. | + | For this milestone you are required to build an MVP. |
| - | It demonstrates enough future benefit to retain early adopters. | + | |
| - | It provides a feedback loop to guide future development. | + | |
| - | The catch to this development technique is that it assumes that early adopters can see the vision or promise of the final product and provide the valuable feedback needed to guide developers forward. | + | |
| - | This suggests that technically orientated products used by technical users may be most appropriate for this type of development technique. | + | A minimum viable product (MVP) is the most pared down version of a product that can still be released, which solves the problem that you are targeting to solve. An MVP has three key characteristics: |
| + | * enough value that people are willing to use it or buy it initially | ||
| + | * demonstrates enough future benefit to retain early adopters | ||
| + | * provides a feedback loop to guide future development | ||
| + | The assumption behind the MVP is that early adopters can see the vision or promise of the final product and provide the valuable feedback needed to guide developers forward. | ||
| - | Minimum Viable Product - [[https://en.wikipedia.org/wiki/Minimum_viable_product|MVP]] | + | Search online for more information about MVPs. |
| + | |||
| + | Your aim is to use it to confirm that people are willing to use / pay for your product or service. At this stage you are not looking to prove retention, thus you can go for an early prototype instead of an MVP (a prototype is more basic compared to an MVP). | ||
| + | |||
| + | Building an MVP without proper validation of the problem, solution and business feasibility (milestones M2, M5, M6) has very little value, and will be graded as such. Therefore, in case it is needed, validate more of your assumptions before proceeding to building the MVP. | ||
| + | |||
| + | Present any further validation and the MVP on the Fiki. | ||
| + | |||
| + | **Motivate all aspects of the MVP!** We will mostly grade the aspects for which justifications are provided. | ||
| - | Merge si doar un prototip. | ||
| - | Daca inca sunt probleme cu validarea, sa mai faca validare! | ||
| - | Implementarea oricarui prototip nu va avea valoare fara validare | ||
| - | </hidden> | ||
