In the product development process, the "minimum viable product" is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. Think of it as a "beta" released initially to a rather small number of power users, to test features, find bugs and prepare for a "full production" product.
The idea is sort of like "prototyping." One wants to quickly figure out what features everybody wants, which features nobody wants, and find out fast.
Friday, September 3, 2010
More on "Minimum Viable Product" in Product Development Process
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Subscribe to:
Post Comments (Atom)
-
We have all repeatedly seen comparisons of equity value of hyperscale app providers compared to the value of connectivity providers, which s...
-
It really is surprising how often a Pareto distribution--the “80/20 rule--appears in business life, or in life, generally. Basically, the...
-
One recurring issue with forecasts of multi-access edge computing is that it is easier to make predictions about cost than revenue and infra...
No comments:
Post a Comment