Minimum Viable Product strategy

We adopted this MVP strategy because Kneaver has already tons of features but many of them have a very limited user interface and little testing. We tailorer the product to a minimum of functions targetting a few initial use cases. Like this we can achieve better support, test coverage and documentation. It is also a unique possibility for our early adopters to be part of the adventure and interact, guide our priorities.

From Wikipedia: In product development, the minimum viable product (MVP) is a strategy used for fast and quantitative market testing of a product or product feature. The term was coined by Frank Robinson and popularized by Eric Ries for web applications.[1][2] It may also involve carrying out market analysis before hand.

A minimum viable product has just those features that allow the product to be deployed, and no more. The product is typically deployed to a subset of possible customers, such as early adopters that are thought to be more forgiving, more likely to give feedback, and able to grasp a product vision from an early prototype or marketing information.

An MVP is not a minimal product,[3] it is a strategy and process directed toward making and selling a product to customers. It is an iterative process of idea generation, prototyping, presentation, data collection, analysis and learning.

The plan is to produce staged minimum viable products all along 2014.

MVP0 was December 2013

MVP1 was February 2014 includes Twitter chat supports.

What’s next ? Let us know your priorities and wishes, that’s the game.

now your priorities and wishes, that’s the game.[/kneaver]