i think this is a poor example unless the customer gets paid for being a beta tester.

Good explanation

Nice, you should repurpose this and say , " we called it, 4 years ago" nice to see this pop after watching your co pilot webinar.

Thank yoyu for sharing this short yet informative presentation

Is it possible to make calls or send voice notes through the whatsapp channel? or what is required to do it?

Very Useful,Thanks

Wait so they want a car but you make a skateboard than a bike? How about build the car slowly like the frame, color, design, tires…..

"earliest testable version" is a great term. it implies that the purpose is feedback then whether to zig or zag from there.

Awful

amazing video, very helpful

Hi CRM Team. I'm not sure you should be using the word "Bastardise" in here, given what it means, it's a bit "rapey"...

AgeOfGods is a perfect example of this. A crypto GameFi project implementing this philosophy in its development process.

Thanks for sharing 🙏🏻

thanks

Now I understand why people has been misleading about MVPs! Who the heck ordered a car and want be happy with a skateboard?! It’s wrong! Wrong! The illustration is misleading you! A to B was not the request! If the customer wants just something to run around on the campus why are you going to spend money to make a car?!! It’s all wrong!! Spend time with your customers! Try to solve their problems!

So many things wrong this - I hardly know where to start. I don't know what the top progression is supposed to represent - but noone designs this way. We have a conversation about the requirements first. We agree on paper what the client might be looking for - before committing expensive resources developing it. We do not manage customer expectations so that clients expect to be excited about a half built car. As for the bottom continuum. I get the potential advantages. Especially when it comes to SW and how hard it is to tie down clients on requirements who don't really know what they want. I might even say - it is a horse for courses decision which way you go.But let no one be under any illusion here. Iterative design is incredibly inefficient and the justification for it is a lazy one. How hard was it to sit down with the client and find out day one that what they wanted was a convertible? Not hard at all. Each of the steps is a pretty much a do over. Like an ant crawling up a wall and falling off at increasing heights - and starting from the floor once again. Very few of the iterations are 'go live' usable with actual customers. So what exactly do the iterations achieve other than to confirm 'this does not meet your requirement'? I'll absolutely accept that waterfall can go badly wrong too. It does. But let's not pretend that iterative design addresses any of waterfall's fundamental issues. It doesn't - It introduces a host of further challenges and only succeeds in a very small number of niche scenarios. Get your requirements right to start with - and then execute. And don't expect your client to find any of the component parts useful, in isolation of the finished product.

The example is seen in many places. MVP is incremental development. The second picture showing skating, cycle etc are not incremental, as they are very different things. So it’s easy to justify as a metaphor but in reality it’s bit difficult to find exact MVP features though it is not impossible

🔥Nice video! I have also done a video on MVP, happy to get your feedback! 🙏

This does not work. Skateboard and skooter has nothin in common with a car. If you are delivering a car, creating skateboard or skooter wastes your time as nothing is really reusable on a car development. This is a bullshit pushed by project manager who do not understand how "their" product works. We have exactly this issue with our banking software where our managers wanted to have a MVP asap so we created "different" application with similar UI (to confuse the user). However, almost nothing behind the UI could be reused and we had to start over (more preciselly we were doing it in parallel). This is such a resource waste. You can make even half of car driveable (wheels with single seat and an engine can be driveable). Perhaps if you stoped with the chopper, it might have worked to some extent (as at least a bike is somewhat similar to a chopper - but still requiring a lot of redos).... But making a car out of chopper? No way you can do that.

Brilliant video. Thanks for uploading!

This is not a MVP. This is delivering a simple product to a customer who asked for a car and expecting feedback that will result in a car. A MVP is an experiment to test a hypothesis such as A customer wants to travel from point A to point B faster than walking. A team goes off and creates something and brings it to the customer...it can be as simple as a drawing that demonstrates the ability to get somewhere faster. You're testing your hypothesis to get feedback - do they like it. What do they like/dislke about the features..what else do they see as a way to meet their need to get somewhere faster. It is intended to be a throw away, not create a release plan. If the customer is keen you build the skateboard, then get more feedback and voila your hypothesis has been proven successful and you are working with the client to build a skateboard, that one day may end up being a car.

could you please create vedio for Omnichannel for Customer Service - phone call Integration(CTI)

thanks for the video

Simply awesome

This video is the ABC of MVP... Thank you for putting out the great content 👍

This is the clearest and understandable MVP video I've ever watched~! Thx for the great work!

Almost 5 years later and here I am listening to a fellow South African talking about MVP. Lekker explanation bru.

Thank you for educating me.

It's very powerful image

Excellent video. Thanks!

Learning will cost more for a customer and instead of a car, he will get a bike for the same money. You need to be sure, that customer can afford it and ready for another approach. Then you can find out that not all customers need to be learned, cause some of them evolved since the times Agile came from.

Donpt givap

The picture is the Minimum Viable Product for explaining the concept of Minimum Viable Product.

CD PR delivered us a wheel. You know what I mean 😄

Companies try to sell to most people, not to create the best product. That's why they need feedbacks and feedbacks and feedbacks... they just want money, they don't want to be in a specific line or even industry. I think it's not the right mindset, but I act like it is the right mindset so I can get a job as a designer 😄

Step 4 wouldn't be a car, the client wanted a car, they'd get something with 18 wheels 200 headlights that only goes backwards.

Great explaining

Please, don't adapt this to software development in any way - it doomed to fail. Do incremental builds (from not like this image) and iterative designs. And yeah, BMW, Mercedes or Toyota always start with delivering skateboards when designing cars. I bet you all have seen these skateboards on the street, right?

Greate Video sir.

@4:31 Whaaat!!!!! I pay you to build the car and not to learn how to build it XD

Please, for the benefit of mankind and to save face for your company - remove this video from the internet.

me looking for the hypixel ranks found this not interesting thing

always disagree with this example - even in video still is wrong.

Nobody delivers a wheel.

So if I have understood it correctly, e.g. it is better to first create a UI without any functionality so the user already has something to evaluate rather than to implement the backend first with nothing more than some console logs of the calculated data as output, because the user will not be able to evaluate this in any way and not understand its benefit. And if you start to implement the backend, you would first only make the basic functionalities working and do not care about security, performance, etc. It is better to have all the basic functionalities working somehow, than only have one functionality working perfectly. Is that right?

This is brilliant and how I have always seen the world.This video is a gamechanger and goes against how MOST school system work.I love the metaphor.Thankins from the tribal team here in Sydney.Its Time

This video is gold 😍

Hi, i have a question, MVP is part of Scrum?

Thank you for the various and meticulous thoughts, but still, on the other hand, I've always been wondering about the cons of MVP.