0:00 → 0:06
Now, why you're doing all this is to define the Minimum Viable Product.
0:06 → 0:10
Or sometimes called the MVP, for short.
0:10 → 0:19
The MVP basically is what product or service you're building in your first instance that's delivered to customers.
0:19 → 0:24
And the MVP is not an alpha or beta, it's a big idea.
0:24 → 0:30
In the old days, the product development process would go from seed funding to concept to a
0:30 → 0:37
market requirements document to an engineering requirements document and blowout into an entire waterfall development process.
0:37 → 0:41
And part of those steps were alpha test, beta test and first customership.
0:41 → 0:47
And you'd be shipping and telling customers, here's a buggy unfinished product, why don't you test it for me.
0:47 → 0:51
And then you'd always argue with sales about whether you should charge for it or not.
0:51 → 0:54
But the MVP is actually quite different.
0:54 → 1:01
The MVP says, no, no we're not suspecting a version 1.0 product that has a spec 18 pages long.
1:01 → 1:09
We're actually doing the work outside the building first and trying to understand what's the minimum version of a version 1.0,
1:09 → 1:16
not what engineering or the founders thought. But what is it customers are going to tell us? They'll pay for our use now
1:16 → 1:24
and while it might be quite a beta product we never use that word, we actually tell customers it's a Minimum Viable Product.