This is going to sound fanboyish, which I hate, but there's a valid point in here:
At least as far as major new product categories go, Apple doesn't ship a Minimum Viable Product. They ship a Minimum Earthshaking Product. Anything that's strictly necessary for their new product to be earthshaking (multitouch, the little touches on the iPhone UI like the rubber band inertial scrolling) they will spend years to perfect; anything that's a niggling little feature (copy and paste) they'll leave for the next version.
The greatest problem with Customer Development and the concept of the Minimum Viable Product is that there is no rigorous classification for quality and value.
Comments
This is going to sound fanboyish, which I hate, but there's a valid point in here:
At least as far as major new product categories go, Apple doesn't ship a Minimum Viable Product. They ship a Minimum Earthshaking Product. Anything that's strictly necessary for their new product to be earthshaking (multitouch, the little touches on the iPhone UI like the rubber band inertial scrolling) they will spend years to perfect; anything that's a niggling little feature (copy and paste) they'll leave for the next version.
In the Kano Model this is called an exciter. http://en.wikipedia.org/wiki/Kano_model
The greatest problem with Customer Development and the concept of the Minimum Viable Product is that there is no rigorous classification for quality and value.
A great book to read with respect to product management is Agile Product Management with Scrum. http://www.amazon.com/exec/obidos/ASIN/0321605780
There are also slides here: http://www.mountaingoatsoftware.com/system/presentation/file...