Software Programming

Kunuk Nykjaer

How to build a minimum viable product – not like this – like this

with one comment


Cool image randomly discovered on Linkedin.

minimum-viable-product

http://en.wikipedia.org/wiki/Minimum_viable_product

The idea is simple.
Make the minimum usable product as fast as possible to get feedback.
With the feedback you can adjust progressively until you get the desired outcome.

The image makes me think of the difference between the Waterfall model and the Scrum model.

I discovered a similar image on the Internet from the blog The Myth of Incremental Development

minimum-viable-product2

Notice the difference in the emotions and the car result. There are two different kind of cars.

The person is highly dissatisfied until the car is produced in the first line. That’s makes sense. Nothing is usable until the very last result.

In the second line the person is dissatisfied for the skater product. Maybe the skater product was not wanted by the person.
Slowly the happiness increases as newer products are produced.

The key difference is the feedback loop.

What if it took X years to build the car and it was the wrong kind of car?
Maybe it was the right car X years back but we are X years wiser now.
Then it would have taken X years to find out that we are building the wrong thing.

Advertisements

Written by kunuk Nykjaer

October 12, 2014 at 10:42 am

Posted in Development

Tagged with ,

One Response

Subscribe to comments with RSS.

  1. That’s cool.
    I like the message of it..
    😀

    Hassan

    May 10, 2016 at 8:55 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: