{"id":2343,"date":"2024-03-26T15:08:12","date_gmt":"2024-03-26T15:08:12","guid":{"rendered":"https:\/\/mobilizingphd.com\/?p=2343"},"modified":"2024-06-02T10:00:46","modified_gmt":"2024-06-02T10:00:46","slug":"lesson-9-scoping-your-mvp","status":"publish","type":"post","link":"https:\/\/mobilizingphd.com\/index.php\/2024\/03\/26\/lesson-9-scoping-your-mvp\/","title":{"rendered":"Lesson 9: Scoping your MVP"},"content":{"rendered":"\n

Don\u2019t forget<\/strong> to block the Live Session in your agenda on March 26th – 15:00. If you don\u2019t have an invite, please message Kim on Slack!<\/p>\n\n\n\n

1)  What is an MVP?<\/h3>\n\n\n\n

MVP stands for minimum viable product. This term is used quite broadly, sometimes people use it to describe any prototype, sometimes people use it to refer to early-versions of their product.<\/p>\n\n\n\n

Eric Ries (Author of Lean Startup) defines it as<\/p>\n\n\n\n

“that version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort.\u201d<\/em><\/p>\n\n\n\n

However, you can learn a lot without a product in hand (think about problem interviews). Therefore, I like a definition that focuses on the Viable-aspect. Viable means that your business can sustain, a.k.a generate enough revenue.<\/p>\n\n\n\n

Therefore, for me,<\/p>\n\n\n\n

\u201cAn MVP is the minimum product or service you can actually sell to your beachhead market customer\u201d<\/em><\/p>\n\n\n\n

So, designing your MVP is all about understanding what to include and what not to satisfy that beachhead market customer. But first, ask yourself if you need one?<\/p>\n\n\n\n

2) Do you need a MVP?<\/h3>\n\n\n\n

Figuring out if you need an MVP depends on what you want to learn.<\/p>\n\n\n\n

    \n
  • MVPs are great for testing the market desirability and willingness to pay of your prospective solution.<\/li>\n\n\n\n
  • MVPs are great for testing if you can generate value for the customer<\/li>\n\n\n\n
  • If you just want to learn about technical feasibility, building prototypes is your way to go, and worry about MVPs later.<\/li>\n<\/ul>\n\n\n\n

    MVPs often are more advanced than (early) prototypes. A prototype is any manifestation of a product that allows you to learn. A sketch is already a prototype.<\/p>\n\n\n\n

    Therefore, sometimes it\u2019s easier to start with prototyping for technical learning, before going to your customer with a MVP you are trying to sell.<\/p>\n\n\n\n

    3) Scoping your MVP to Define is to Limit<\/h3>\n\n\n\n

    The M in MVP stands for minimum. Focusing on the bear minimum is hard.<\/p>\n\n\n\n

    A simple way in thining about this is the MoSCoW framework.<\/p>\n\n\n\n

      \n
    • You probably have a list of features.<\/li>\n\n\n\n
    • For each feature, ask yourself, for my MVP, is the feature a:\n
        \n
      • Must Have<\/li>\n\n\n\n
      • Should Have<\/li>\n\n\n\n
      • Could Have<\/li>\n\n\n\n
      • Will not Have<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        \n