Tweet
Tweet

Slide 1

Slide 1 text

Minimum Viable Product What? Why? How?

Slide 2

Slide 2 text

The Minimum Viable Product is one of the most popular outcomes of the Lean Startup methodology by Eric Ries.

Slide 3

Slide 3 text

What is it not? "Typically, when IT budgets are crafted and portfolio of investments are put together. There is always this expectation that the first release will be full featured and perfect in a way that you will never have to invest on it afterwards." - Paul Chapman, CIO of HP (2015)

Slide 4

Slide 4 text

What is it not? MVP ≠ Beta MVP ≠ Excuse to build a crappy product

Slide 5

Slide 5 text

What is it? "A version of a product which allows a team to collect the maximum amount of validated learning about customers with the least effort." - Eric Ries (2009)

Slide 6

Slide 6 text

What is it? "A version of a product which allows a team to collect the maximum amount of validated learning about customers with the least effort." - Eric Ries (2009) A release

Slide 7

Slide 7 text

What is it? M - The minimum V - Viable P - Product

Slide 8

Slide 8 text

What is it? M - The minimum V - Viable P - Experiment

Slide 9

Slide 9 text

What is it? "Time to value. How quickly can you start to extract value from the investment that you are making" - Paul Chapman, CIO @ HP (2015)

Slide 10

Slide 10 text

What is it? An annoying Buzzword

Slide 11

Slide 11 text

What is the goal?

Slide 12

Slide 12 text

What is the goal? Vision

Slide 13

Slide 13 text

What is the goal? Vision Reality

Slide 14

Slide 14 text

What is the goal? "What's the smallest thing I can do to figure out if am I building a business or if it is just a hobby." - Abby Fichtner, Creator of Hack Boston (2013)

Slide 15

Slide 15 text

What is the goal? "You're way too dumb to figure out whether your idea is good or not." - Andrew Mason, CEO of Groupon

Slide 16

Slide 16 text

What is the goal? To avoid Feature Creep

Slide 17

Slide 17 text

What is it? - Build the minimum set of features that is viable enough to test your key assumptions. - Learn more about your customers and the problem you want to solve.

Slide 18

Slide 18 text

What is the goal? - To learn if your vision matches the reality. - To avoid "feature creep".

Slide 19

Slide 19 text

MVP Tools some

Slide 20

Slide 20 text

- Concierge Service / "Wizard of Oz" - Existing Tools Mashup - Custom development - Customer Interviews - Landing page / Ghost product - Crowdfunding - Video Validate the problem (Smoke Test) Validate your solution

Slide 21

Slide 21 text

Landing page / Ghost product

Slide 22

Slide 22 text

Video

Slide 23

Slide 23 text

Crowdfunding

Slide 24

Slide 24 text

- Concierge Service / "Wizard of Oz" - Existing Tools Mashup - Custom development - Customer Interviews - Landing page / Ghost product - Crowdfunding - Video Validate the problem (Smoke Test) Validate your solution

Slide 25

Slide 25 text

Concierge Service / "Wizard of Oz"

Slide 26

Slide 26 text

Existing Tools Mashup

Slide 27

Slide 27 text

Custom development Boitata

Slide 28

Slide 28 text

How to do it?

Slide 29

Slide 29 text

How to do it? 1) Validate the problem. 2) Validate your solution. 3) Build - Measure - Learn

Slide 30

Slide 30 text

How to do it? 1) Validate the problem. - Customer Interviews - Landing page / Ghost product - Crowdfunding - Video 2) Validate your solution. 3) Build - Measure - Learn

Slide 31

Slide 31 text

How to do it? 1) Validate the problem. 2) Validate your solution. - Concierge Service / "Wizard of Oz" - Existing Tools Mashup - Custom development 3) Build - Measure - Learn

Slide 32

Slide 32 text

How to do it? 1) Validate the problem. 2) Validate your solution. 3) Build - Measure - Learn - Customer Interviews - Customer Feedback - Analytics / Metrics - A / B Testing

Slide 33

Slide 33 text

Cases (da Leroy Merlin) - PriceHistory - Dashboard with metrics - WebsiteSearch - ReportGenerator - AttributeGroup - AdvancedRelation - label "Compre Online". - ClickAndCollect - Estoque das Lojas - lista.leroymerlin.com.br -

Slide 34

Slide 34 text

Conclusion "The same basic concepts have clearly become the consensus for software development in general. Agile software management provides the same wisdom — that the only certainty is uncertainty and we need not map out the entire solution prematurely." - Ben Halpern, co-founder of Texts.com (2016)

Slide 35

Slide 35 text

Conclusion - MVP - Lean Startup Methodology - Iterative development - Agile - LUF - Management 3.0 - A/B Testing - Marketing

Slide 36

Slide 36 text

Resources How To Do MVPs Right! - Hatchery http://hatchery.io/blog/how-to-do-mvps-right What is an MVP? - Customer Development Labs http://customerdevlabs.com/2016/04/06/what-does-minimum-viable-product-mean/ Minimum viable product myth - HP Technology https://www.youtube.com/watch?v=FLPHCRS--Rg Scalpel, not a Swiss Army Knife - 33voices https://goo.gl/xBl96N Creating Your Minimum Viable Product with Abby Fichtner - Harvard i-lab https://www.youtube.com/watch?v=cjCCS3DxZRo Don’t Use “MVP” as an Excuse to Write Bad Software - Ben Halpern https://dev.to/ben/dont-use-mvp-as-an-excuse-to-write-bad-software