[I4trust-mentors] i4Trust - 1.OC - Stage 3 - Deliverable MVP (Minimum Viable Product)

Rajiv Rajani | iSHARE rajiv at ishare.eu
Mon Oct 10 09:13:25 CEST 2022


Hi Juanjo and Gernot,

Yes, the answer matches my definition that I have been explaining to
projects and mentors. A bit surprised though that this is still a question
for some mentors. However, reading the answer the good part is we are on
the same page.

Just to make sure I share following with projects when asked about
evaluation of MVP deliverable is following:

   - MVP meaning Minimum Viable Product and as we promise in our program
   that we help bring experiments to reach TRL level 8 which essentially says
   that the product is ready to be used in real situations - Refer to the EC
   definition on the same -
   https://ec.europa.eu/research/participants/data/ref/h2020/wp/2014_2015/annexes/h2020-wp1415-annex-g-trl_en.pdf
   - As opposed to prototype which is used to prove a certain solution is
   achievable and feasible MVP is product based on that solution which is
   ready for market and that means not showing the functionality using postman
   or other such tool since one does not go to their customer and ask them to
   use postman or similar tools and rather gives them something that is
   functional.
   - The delivery requirements and process is similar to that of prototype
   - i.e. a live recording of the session where now they demonstrate a working
   MVP and explanation of their solution as they would to their customers
   followed by basic checks on the backend and logs as we did for prototype
   validation.


I hope this makes it clear for all on the deliverable of MVP.

On other hand, I would appreciate that such questions and answers are not
shared directly into this group without discussion with partners or in
mentors sync to avoid any kind of confusion in future.

Regards,
Rajiv Rajani


On Mon, Oct 10, 2022 at 12:15 AM Juanjo Hierro <juanjose.hierro at fiware.org>
wrote:

> Hi,
>
>   Thanks Gernot for sharing as I asked you.  Certainly we need to come
> with a common perspective how to evaluate MVP demo at the end of stage 3.
>
>   Further development of my answer: that is why demo in stage 2 is
> referred to PoC (Proof of Concept) while demo in stage 3 is referred to MVP
> (Minimum Viable Product).   And, literally, MVP means something that
> implements the core functionalities and is ready for bringing it to early
> customers (see a valid definition of MVP
> <https://en.wikipedia.org/wiki/Minimum_viable_product>).
>
>   Question to Rajiv is: the answer I gave to Gernot and I further develop
> above is my take on the matter.  Does it match yours?   We should as
> partners within the consortium be aligned here.
>
>   Cheers,
>
>   Juanjo
>
>
> On 9/10/22 21:10, Gernot Boege wrote:
>
> Hi all,
>
> I raised that question in our FF internal mentor chat because I was not
> aware of the way how to evaluate.
>
> Juanjo found that question relevant to all, therefore, here the
> question/answer couple.
>
> *Q:*
> Do we have any specific requirements to the MVP Demo at the end of stage
> 3? ... Something higher than end of stage 2? ... different criteria or
> evaluation aspects?
>
> *A from Juanjo:*
> Stage 2 is expected to be a PoC. Stage 3 is expected to be something way
> more mature.  Sort of pilot. Something that may be enough mature as to
> trust it can be moved into production in near term.
>
>
> Maybe it helps a bit.
>
>
> Best regards
>
> --
> Gernot Böge
>
> *FIWARE Solution Architect*
> *FIWARE Foundation*
>
> Franklinstrasse 13 A
> <https://www.google.com/maps/place/Franklinstraße+13A,+10587+Berlin/@52.5211727,13.3263511,17z/data=!3m1!4b1!4m5!3m4!1s0x47a851103bb2736d:0x93ab7f58251a69b3!8m2!3d52.5211727!4d13.3285398>
> 10587 Berlin - Germany
> <https://www.google.com/maps/place/Franklinstraße+13A,+10587+Berlin/@52.5211727,13.3263511,17z/data=!3m1!4b1!4m5!3m4!1s0x47a851103bb2736d:0x93ab7f58251a69b3!8m2!3d52.5211727!4d13.3285398>
>
> mail: gernot.boege at fiware.org
> www.fiware.org
>
> <http://www.fiware.org>
>
> <https://nexus.lab.fiware.org/fiware.signature>
>
> __________________________________________________________________________________________
>
> You can get more information about our cookies and privacy policies on the following links:
> - https://fiware-legal.readthedocs.io/en/latest/PersonalDataProtectionPolicy.html
> - https://fiware-legal.readthedocs.io/en/latest/FIWARECookiesPolicy.html
>
>
> i4trust-mentors mailing listi4trust-mentors at lists.fiware.org
>
> To unsubscribe from i4trust-mentors mailing list, go to the information page of the list at:https://lists.fiware.org/listinfo/i4trust-mentors
>
>
> __________________________________________________________________________________________
>
> You can get more information about our cookies and privacy policies on the
> following links:
> -
> https://fiware-legal.readthedocs.io/en/latest/PersonalDataProtectionPolicy.html
> - https://fiware-legal.readthedocs.io/en/latest/FIWARECookiesPolicy.html
>
>
> i4trust-mentors mailing list
> i4trust-mentors at lists.fiware.org
>
> To unsubscribe from i4trust-mentors mailing list, go to the information
> page of the list at:
> https://lists.fiware.org/listinfo/i4trust-mentors
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/i4trust-mentors/attachments/20221010/b35dccfb/attachment-0001.html>


More information about the I4trust-mentors mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy