News for hackers. Stuff that matters.

A comment on A Minimum Viable Product Is Not a Product, It’s a Process.

Re:A Minimum Viable Product Is Not a Product, It’s a Process by applecore on Saturday January 23, 2016 @09:32AM (#10958490)
>The problem is that these teams do not understand the point of an MVP. [...] In fact, the MVP doesn’t have to be a product at all.

By definition, a minimum viable product is always a product: http://www.startuplessonslearned.com/2009/08/minimum-viable-...

[ Parent | on HN ]
Re:A Minimum Viable Product Is Not a Product, It’s a Process by brikis98 on Saturday January 23, 2016 @12:29PM (#10959086)
That article, and Eric Ries' book, define an MVP as a "version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort." A "version of a new product" doesn't have to be a product.

The classic example of an MVP that Eric Ries uses is the explainer video Drew Houston created for DropBox before building the actual product [1]. The video worked as an MVP by helping Houston test his assumptions, but I don't think you could say the video itself was a "product."

[1] http://techcrunch.com/2011/10/19/dropbox-minimal-viable-prod...

[ Parent | on HN ]