1 00:00:07,470 --> 00:00:11,881 After watching this video, you will be able to define a minimum viable product (MVP) and 2 00:00:11,881 --> 00:00:16,820 recognize how an MVP should be used to give the customer what they really want. 3 00:00:16,820 --> 00:00:19,290 Let's talk about a minimum viable product. 4 00:00:19,290 --> 00:00:24,510 First, let's understand what it is not, because there are some misconceptions that a minimum 5 00:00:24,510 --> 00:00:29,220 viable product is the same as phase one of the project or, the first beta, or something 6 00:00:29,220 --> 00:00:30,500 like that. 7 00:00:30,500 --> 00:00:33,570 This is not what a minimum viable product is. 8 00:00:33,570 --> 00:00:38,680 A minimum viable product is the minimal thing that you can do to test a value hypothesis 9 00:00:38,680 --> 00:00:41,120 and gain learning and understanding. 10 00:00:41,120 --> 00:00:45,230 You might say it is the cheapest thing you can do to prove a hypothesis. 11 00:00:45,230 --> 00:00:49,500 You can finish the first MVP, then you get the results and move to the second one, and so 12 00:00:49,500 --> 00:00:50,500 on. 13 00:00:50,500 --> 00:00:53,990 The difference between these two is that the first one is all about delivery. 14 00:00:53,990 --> 00:00:54,990 What am I going to deliver? 15 00:00:54,990 --> 00:00:57,980 But the second one is all about learning. 16 00:00:57,980 --> 00:00:58,980 What can I learn? 17 00:00:58,980 --> 00:01:02,870 What can I learn from putting out this MVP and getting feedback and then maybe making 18 00:01:02,870 --> 00:01:04,559 the next one even better? 19 00:01:04,559 --> 00:01:10,440 So, it's important that at the end of each MVP you decide whether to pivot or persevere. 20 00:01:10,440 --> 00:01:15,210 Should I pivot, that is, do something different or persevere, continue doing what 21 00:01:15,210 --> 00:01:16,810 I’m doing? 22 00:01:16,810 --> 00:01:18,890 Let's look at an example. 23 00:01:19,070 --> 00:01:23,510 Here's a team that's developing a minimum viable product for a customer that wants a 24 00:01:23,510 --> 00:01:24,650 red car. 25 00:01:24,650 --> 00:01:27,590 And so, in the first iteration, they deliver a wheel. 26 00:01:27,590 --> 00:01:30,220 The customer's like, "What am I going to do with a wheel? 27 00:01:30,220 --> 00:01:31,610 I can't do anything with this." 28 00:01:31,610 --> 00:01:36,549 Well, we’re working iterations they say, we're trying to be agile here. 29 00:01:36,549 --> 00:01:38,950 In the next iteration, we'll give you something more. 30 00:01:38,950 --> 00:01:40,820 And they give the customer a chassis. 31 00:01:40,820 --> 00:01:45,049 And the customer responds, "I still can't do anything with this chassis." 32 00:01:45,049 --> 00:01:48,820 And then, they give them a car with no steering wheel and then eventually right they get the whole 33 00:01:48,820 --> 00:01:49,619 car. 34 00:01:49,619 --> 00:01:51,875 Now the customer gets this coupe, 35 00:01:51,928 --> 00:01:53,780 and there was no feedback along the way. 36 00:01:53,780 --> 00:01:56,960 The team didn't know until the end whether the customer was going to like what they built 37 00:01:56,960 --> 00:01:58,100 or not. 38 00:01:58,100 --> 00:02:02,030 The team did not understand how to create a minimum viable product. 39 00:02:02,030 --> 00:02:06,780 They were just doing iterative development with no regard to whether each increment was 40 00:02:06,780 --> 00:02:08,750 useful or not. 41 00:02:08,750 --> 00:02:12,580 The second team understands the value of creating an MVP. 42 00:02:12,580 --> 00:02:16,849 At first, they give the customer a skateboard and the customer says, "What's this? 43 00:02:16,849 --> 00:02:19,590 I asked you for a car and you're giving me a skateboard." 44 00:02:19,590 --> 00:02:23,310 The team explains, we're testing the color. 45 00:02:23,310 --> 00:02:25,060 How do you like that color red? 46 00:02:25,060 --> 00:02:26,390 Is that the color you want? 47 00:02:26,390 --> 00:02:30,900 The customer says, "Oh yeah, red's kind of cool you know it's really hard to steer though." 48 00:02:30,900 --> 00:02:33,540 The team says, “No worries.” 49 00:02:33,540 --> 00:02:35,650 In the next MVP, they give him a way to steer it. 50 00:02:35,650 --> 00:02:40,200 The customer says, "Well, okay, you did give me a way to steer it but I can't go very fast. 51 00:02:40,200 --> 00:02:43,380 I need a better form of locomotion." 52 00:02:43,380 --> 00:02:45,061 The team deals with that in the next MVP. 53 00:02:45,061 --> 00:02:49,380 In the next iteration, they give them pedals to go faster. 54 00:02:49,380 --> 00:02:54,830 Somewhere along the way, while riding on that motorcycle feeling the wind in their hair 55 00:02:54,830 --> 00:02:59,550 the customer decides, "I really want a convertible!" 56 00:02:59,550 --> 00:03:05,050 In the first instance, the customer got exactly what they asked for months prior because the 57 00:03:05,050 --> 00:03:07,470 development team was just following a plan. 58 00:03:07,470 --> 00:03:13,170 But in the second instance, the customer got exactly what they desired because they were 59 00:03:13,170 --> 00:03:17,630 working iteratively and interactively with the development team. 60 00:03:17,630 --> 00:03:21,890 In the end, you develop something that's a little bit different but it's closer to what 61 00:03:21,890 --> 00:03:24,780 the customer really wants. 62 00:03:24,780 --> 00:03:29,990 Giving the customer what they really want is the main purpose of delivering an MVP. 63 00:03:29,990 --> 00:03:32,900 A minimal viable product is a tool for learning. 64 00:03:32,900 --> 00:03:38,330 It is an experiment to explore the value proposition with your customer. 65 00:03:38,330 --> 00:03:44,250 This experiment may fail and that's okay because failure leads to understanding. 66 00:03:44,250 --> 00:03:46,030 What did you learn from that failure? 67 00:03:46,030 --> 00:03:47,290 What did it teach you? 68 00:03:47,290 --> 00:03:49,590 What is the next experiment? 69 00:03:49,590 --> 00:03:52,240 What will you do different the next time? 70 00:03:52,240 --> 00:03:57,180 These are the questions that lead to gaining knowledge and understanding about what you 71 00:03:57,180 --> 00:03:58,180 are building. 72 00:03:58,180 --> 00:04:02,510 This is why we use MVPs in DevOps. 73 00:04:02,510 --> 00:04:06,640 In this video, you learned: An MVP is the minimal thing that you can do 74 00:04:06,640 --> 00:04:07,800 to test your hypothesis. 75 00:04:07,800 --> 00:04:12,519 An MVP is not about delivery as much as learning. 76 00:04:12,519 --> 00:04:16,909 It's okay if the MVP fails—make sure that you learn from it.