Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
RK
Uploaded byRolands Krumbergs
PPTX, PDF1,137 views

Building an MVP

The document discusses building a minimum viable product (MVP) for a project idea. It provides examples of MVPs for Facebook, Dropbox, and Zappos and explains how they tested hypotheses with very simple initial products. The meeting's agenda is then to understand lean startup methodology and MVPs, see examples, and use story mapping to define an MVP for a semester project. Story mapping is introduced as a technique to replace feature lists with a two-dimensional map focusing on user activities and vision. Attendees will work in groups to define an MVP for a project helping users find and share healthy recipes.

Education◦
Downloaded 57 times
Building a minimum viable product Youth Techclub meet-up 14.03.2016
First open meet-ups 14.03.2016 – minimum viable product (and some lean startup) 23.03.2016 – website prototyping xx.04.2016 – Visual Studio Code (IDE) and GitHub usage (source control)
Goals Understand core idea about lean startup methodology. Understand what is minimum viable product. Understand how to use story mapping in defining MVP. MVP for this semester’s project idea.
Agenda Lean startup methodology (just for MVP) Minimum viable product MVP examples Excercise for building MVP for project idea
Startup A human institution designed to create a new product or service under conditions of extreme uncertainty.
Problems with startups Most of them do not know yet what they are building. They tend to spend a lot of time building a product that later on is something that noone wants and uses.
Solution (possibly?) Lean manufacturing ideas – focuses on removing waste. Defines Build-Measure-Learn cycles.
It’s all about hypothesis Value hypothesis – tests whether a product or service really delivers value to customers once they are using. Growth hypothesis – tests how new customers will discover a product or a service.
How to test your hypothesis? You do not need fully featured product or service to do test value/growth hypothesis. Maybe you do not need to do any programming at all. Make the test cycle as short as possible.
Build-Measure-Learn This is were MVP is built. MVP is a version of a new product which allows a team to collect maximum amount of validated learning about customers with the least effort. It’s not necessarily smallest product imaginable, it can range in complexity from extremely simple smoke test to actual prototype.
Lets look on some real-life examples
Facebook
Dropbox Team wanted to test their leap-of-faith question – if Dropbox can provide a superior customer experience, will people give it a try? Product requires deep technical expertise and big development effort. Their MVP – a video explaining the technology. Result – waiting list went from 5,000 to 75,000 in one night.
Zappos Hypothesis – are the customers ready and willing to buy shoes online. Testing the hypothesis – founder began asking local shoe stores if he could take the pictures of their inventory, in exchange for permission, he would post the pictures online and come back to buy the shoes at full price if a customer bought them online.
Lets assamble! Groups of maximum 3 people. 1. Find your team members (choose people that you do not know personally) 2. Make your acquaintance 3. 5 minutes for the task 4. 20 seconds for presentation
What would be MVPs for these companies?
Before we define MVP for project idea lets understand one of the techniques building MVPs
Story mapping core idea Replace the traditional one dimensional list of features ordered according to business value with two dimensional map which focuses on user activities and the overall vision of the product.
In the practice Step 1 – capture primary goal of your product Step 2 – define the main process in the product Step 3 – create a list of features for each stage Step 4 – prioritize the features inside lists Step 5 – define the MVP
Step 1 – capture primary goal Imagine you are developing a product which helps people to assemble their own customized shoes. Product allows users to choose colors, fabrics, decorations and shapes. Primary goal could be – Allowing users to receive an individual, customized pair of shoes.
Step 2 – define main process Think more about tasks that user has to do instead of features. Customize shoe Buy shoe Manage order Deliver order
Step 3 – list of features Customize shoe Buy shoe Manage order Deliver order Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature
Step 4 – prioritize features Customize shoe Buy shoe Manage order Deliver order Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature
Step 5 – define MVP Customize shoe Buy shoe Manage order Deliver order Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Walking skeleton Your MVP
Project idea Core problem – it is hard to find an online place/site that would contain personalized recipes with healthy food. Primary goal – allow users to find and share healthy recipes according to their taste.
Task in groups Define a MVP for project idea 1. Same groups 2. 15 minutes for task 3. 2 minutes for presentation At the end we will choose the features for MVP alltogether.
That’s all! Thank you! Don’t forget to leave some feedback – both positive and constructive  Follow us on Facebook Apply – www.youthtech.lv Next meet-ups: 23.03 18:00 – prototyping 06.04 18:00 (?) – IDE and source controle
More info: Lean startup methodology: http://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous- Innovation/dp/0307887898/ref=sr_1_1?ie=UTF8&qid=1458056711&sr =8-1&keywords=lean+startup+eric+ries Story mapping: http://blog.cayenneapps.com/2014/11/25/5-steps-to-building- minimum-viable-product-with-story-mapping/