…the minimum viable product is that product which has just those features (and no more) that allows you to ship a product that resonates with early adopters; some of whom will pay you money or give you feedback.
I apply MVP to all of the work I do. What’s the minimum amount of documentation I can do to express a new feature completely? What is the least amount of work I need to do to get the result I need?
The tricky part is figuring out what the MVP is!
If you’re not sure if what you’ve done is enough, get feedback. When I’m doing sketch wireframes, either on paper or in omnigraffle, I ask other people on the team for feedback as soon as I’ve reached a point I have a deliverable that I think stands on it’s own without any explanation or handholding from me.
What do you think about MVP? Is it the lazy person’s approach to work?
Minimum Viable Product
Minimum Viable Product (MVP) is a concept popularized for web application development by Eric Ries.
I apply MVP to all of the work I do. What’s the minimum amount of documentation I can do to express a new feature completely? What is the least amount of work I need to do to get the result I need?
The tricky part is figuring out what the MVP is!
If you’re not sure if what you’ve done is enough, get feedback. When I’m doing sketch wireframes, either on paper or in omnigraffle, I ask other people on the team for feedback as soon as I’ve reached a point I have a deliverable that I think stands on it’s own without any explanation or handholding from me.
What do you think about MVP? Is it the lazy person’s approach to work?