Home
Search results “Minimum viable product scrum”
Making sense of MVP (Minimum Viable Product)
 
11:47
Adapted from Crisp's blog by Henrik Kniberg. Explaining his MVP drawing. This drawing shows up all over the place, in articles and presentations, even in a book (Jeff Patton’s “User Story Mapping” – an excellent read by the way). Many tell me the drawing really captures the essence of iterative & incremental development, lean startup, MVP (minimum viable product), and what not. However, some misinterpret it, which is quite natural when you take a picture out of it’s original context. Some criticize it for oversimplifying things, which is true. The picture is a metaphor. Find the original article here: http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp Video by The CRM Team. For more great content have a look at our resources page here: http://thecrmteam.com/resources/
Views: 107769 The CRM Team
3 Awesome Minimum Viable Products (MVPs)
 
04:54
What are the best MPVs of all time? I've absolutely no idea... but Buffer, Dropbox and Zappos are three of my favourites. Grab your FREE Lean Startup Cheat Sheet: http://www.developmentthatpays.com/cheatsheets/the-lean-startup 0:15 - Ground rules for a perfect MVP 1:00 - Buffer's MVP 1:58 - Dropbox's MVP 3:23 - Zappos' MVP LINKS - Steven Cohn: https://www.linkedin.com/pulse/death-minimum-viable-product-steven-cohn - Buffer: https://blog.bufferapp.com/idea-to-paying-customers-in-7-weeks-how-we-did-it - Dropbox: http://techcrunch.com/2011/10/19/dropbox-minimal-viable-product/ - Zappos: http://www.bullethq.com/blog/lean-startup-zappos-how-zappos-validated-their-business-model-with-lean/ → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 ------------------- 35. 3 Awesome Minimum Viable Products (MVPs) Today, we're going to take a look at three of my favourite examples of Minimum Viable Products (MVPs). Before diving in. let's establish some ground rules for a "proper" MVP It's got to be Minimal It's got to be Viable And it's got to be a Prod... Actually No, it does not need to be a Product. (I'll be showing you a great example of a "non-product" in a minute or two.) Some have argued that the word "Product" in MVP is unhelpful. Steven Cohn has made a strong case for the word "Experiment". I agree. But for now let's stick with the "P" and temporarily re-define it to.... Pre-meditated. Meaning that the MVP must be a deliberate attempt to learn about the market. This rules out cases that look like MVPs in retrospect, but were really full products that - to everyone's surprise - developed into something big. Let's get going. No. 3 - Buffer ------ Buffer is a application that makes it easy to share content on social media. Here's what they put on the their site. A test, certainly. But it falls short of an MVP in my opinion. Their next test was better. They slotted this page in-between the other two pages. Now visitors to the website are not just saying "This is interesting" They're saying "I want to BUY this". Okay, there's nowhere to input your credit card details. But anyone who got this far was at least prepared to think about parting with their money. As co-founder Joel Gascoigne said: "After this result, I didn’t hesitate to start building the first minimal version of the real, functioning product." Minimal - certainly Viable - yes Pre-mediated - check Buffer's current valuation is something close to $400 million No. 2 - Dropbox ---- Dropbox, as I'm sure you know, is a file synchronisation service. Edit a file on your desktop... ... and seconds later its updated on all of your other devices. Rewind to the early days. The team - entirely composed of techies - had the basic synchronisation working. That was the easy bit. The hard bit was going to be to achieve the same trick on pretty well every platform: Mac, Windows, iPhone, etc. Given that the team was all techies, you'd have put money on them diving straight in. But CEO Drew Houston did something surprising. He made a video. The video - just three minutes long - demonstrated the synch process end to end. But it was more than just a demo: it was full of techie in-jokes... designed to appeal to early adopters. It worked like a charm In Drew's words: “It drove hundreds of thousands of people to the website. Our beta waiting list went from 5,000 people to 75,000 people literally overnight. It totally blew us away.” Minimal - Yes Viable - Not a product that could be used, but a product that could be demonstrated. Pre-Meditated - Yes Dropbox went on to do quite well. It's current value stands between $5 and $10 BILLION. No. 1 - Zappos ---- It's 1999. Co-founder Nick Swinmurn wanted to build an online store for shoes. But would people use it Here's how he went about finding out. He popped down to lis local shoe shops he went into the shops and... ... I sh!t you not... he PHOTOGRAPHED PAIRS OF SHOES! The photos were uploaded to a super-simple website. If someone clicked on the button to buy a pair Nick would pop down to the store and... BUY THE SHOES! Zero infrastructure. Zero inventory. Minimal - definitely Viable - This time it's not even up for discussion. Most definitely: real customers; real money changing hands; real shoes! Pre-meditated Check. Zappos went on to do quite well: it was acquired by Amazon in 2009 for a cool $1.2 billion. Your thoughts, please! ---- Buffer, Dropbox and Zappos. Three of my favourite MVPs. What do you think of my choices Any you disagree with Let me know in the comments. And I'd also like to he https://www.youtube.com/watch?v=xPJoq_QVsY4 https://www.youtube.com/watch?v=cjCCS3DxZRo
Views: 64785 Development That Pays
Minimum Viable Product: You're Doing It Wrong!
 
02:01
34. Minimum Viable Product: You're Doing It Wrong! // The concept of Minimum Viable Product (MVP) is not new, but it didn't 'click' for me until I saw one perfect image. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Henrik Kniberg's beautiful sketch powerfully illustrates where we've been going wrong: creating products that are MINIMAL, but not VIABLE. LINKS -- Frank Robinson: http://www.syncdev.com/minimum-viable-product/ -- Henrik Kniberg: http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 The best definition I've seen for "Minimum Viable Product" is not a set of words. It's a sketch. A sketch that encapsulates the concept so perfectly... ... that it went viral. Frank Robinson -------- Frank Robinson coined the term "Minimum Viable Product" in 2001. The idea - at least at a superficial level - is simplicity itself: Get a version of the product in front of a customer early as possible. Not with the aim of generating early income - though that is no bad thing - but with the aim of LEARNING. The chances are that you've heard of Minimum Viable Product before today.. ... and that when you heard it, you immediate "got it". As Frank himself said: “When I first said ‘minimum viable product’ I never had to repeat myself. The words went viral right before my eyes.” BUT... Is it Viable ------- Just because something is easy to grasp, doesn't mean it's easy to do. It's not easy. Far from it. Here's the problem: We - development teams, lead developers, product owners... even business owners - usually have an idea of what the "ultimate" product might look like. Ask us to come up with a minimum version and we'll hack off a feature here and a feature there. What we end up with will certainly be MINIMAL: that's the easy part. But will it be VIABLE That's the tricky part. Enter Henrick Kniberg ----- A gentleman by the name of Henrick Kniberg captured the difference between the two perfectly in his (now viral) image: In the top line, we have minimal, but not viable (until we get the final step). In the bottom line, we have minimal AND viable every step of the way. In a recent blog post, Henrik said that he was surprised that his image went viral. I'm not surprised at all. I think it's genius. Next time. ------- Next time we'll take a look at some "real world" Minimium Viable Products. https://www.youtube.com/watch?v=rmGOBzpn_98 https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 9929 Development That Pays
What is a Minimum Viable Product (MVP)
 
11:32
There are a lot of definitions of MVP. In this video I'll share mine and walk you through a concrete examples of how you define and build out your MVP.
Views: 19916 Ash Maurya
Minimum viable product (MVP). What is it and why should I care?
 
06:58
A minimum viable product is a great way of building user centric digital services in a fraction of the time. It will also lead to big cost savings.
Views: 3084 Boagworld
MVP: Quickly Validate your Start-Up
 
11:09
Whether you're creating a mobile app or a cat food delivery business, it's often helpful to start with a Minimum Viable Product. With an MVP, you'll spend more time building the things that matter, and be able to quickly test your assumptions--and the market. But how do you decide what stays and what goes? Will Dayble, director of web development company Squareweave, takes us through the process of creating an MVP.
Views: 107146 TeamLearnable
The Lean Approach: Minimum Viable Products
 
05:53
Steve Blank says a minimum viable product, or MVP, can help you test your hypotheses about the market, and your customers, before you spend too much time creating and shipping the product. THIS VIDEO CAN HELP ANSWER: What is a minimum viable product? Why should I create a prototype? Do MVPs have to be perfect? How can I use an MVP to run an experiment? ABOUT THE KAUFFMAN FOUNDERS SCHOOL Visit the website: [http://bit.ly/1EW2br7] The Kauffman Founders School presents a powerful curriculum for entrepreneurs who wish to learn anywhere, anytime. The online education platform features experts presenting lectures in series modules designed to give Founders a rich learning experience, while also engaging them in lessons that will make a difference in their business today, tomorrow, and in the future. The Kauffman Founders School series modules include Powerful Presentations, Intellectual Property, Founder's Dilemmas, Entrepreneurial Selling, Entrepreneurial Marketing, Surviving the Entrepreneurial Life, Startups, and much more. © Ewing Marion Kauffman Foundation.
The Lean Startup - 5 Keys to a Successful Minimum Viable Product Launch
 
05:20
A month ago I launched a new product - a new Minimum Viable Product. I learned a lot: here are the 5 things you need to know. Grab your FREE Cheat Sheet: http://bit.ly/lean-startup-cheatsheet In today's video, five keys to a successful Minimum Viable Product Launch: - 1. Launch before _____ _____ - 2. There are more ______ _____ than you think - 3. Launch to a _______ _______ - 4. Be ready to make _______ ______ - 5. Remember that it’s an ________ → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe ------------------- 108. The Lean Startup - 5 Keys to a Successful Minimum Viable Product Launch So you’re planning to launch a product A Minimum Viable Product Excellent. A New Course ------- Just over a month ago, our adventure into Lean - that’s “Lean” as in “The Lean Startup” - reached an interesting stage. I launched a product. A Minimum Viable Product. The “Course of Some Kind” crystalised into “Scrum vs Kanban - the Mini-course”. Here are FIVE things that I learned along the way: 1: Launch before you’re ready ----- Are you the kind of person that hears "Done Is Better Than Perfect" or “Shipping beats perfection” and thinks: “Really Are you sure ” If so, you’re in good company. “Hello. My name is Gary. I’m perfectionist.” October was hell for me. My task was take existing material and to repurpose it into a mini-course. That doesn’t sound like a recipe for torment. But the more I worked on the course, the less I liked it. I wanted to rip it up and start again. If this sounds like you, then take a note from Reid Hoffman, founder of LinkedIn "If You're Not Embarrassed By The First Version Of Your Product, You’ve Launched Too Late" So pick and date. And launch. Before you’re ready. Bonus Tip: Set things up so that the date can’t be moved. I wrote the launch into an episode of Development that Pays. At that point, I was committed! 2: Remember that there are more moving parts than you think. ---- Your focus will the on the product. That’s only natural. But a product won’t launch itself. You’re going to need plumbing. I had my three videos. I also had an email service capable of sending time-delayed emails. Three videos. Three emails. Simples. But it’s probably not a great idea to send people direct to the video: each should be on its own page... And I’m going to need a form - so that people can sign up... And the form is going to need page to “live on”... And…. I think you get the message :) 3: Launch to a limited audience ---- Although it’s important to launch before you’re ready, you don’t have to be damn fool about it; not everyone has to see your “warts and all” version. So launch… but make it a soft launch. Wikipedia defines a soft launch as “a preview release of a product or service to a limited audience prior to the general public”. In the case of the “Scrum vs Kanban the Mini Course”, I “hid” the announcement in a “regular” Development That Pays episode: only people that watched one particular episode all the way to the 4 and half minute mark got the link. 4 - Be ready to make running repairs ----- Launch day rolls around. You push the Big Green Button, and breath a sigh of relief. But don’t relax too much! To paraphrase Mickey Rouke’s character in Body Heat: “You got fifty ways you're gonna * up. If you think of twenty-five of them, then you're a genius... and you ain't no genius.” Well you may be you are a genius. I am not. A genius would not have…. wasn’t expecting to told that one of my videos had TWO audio tracks. - A genius would not have I wasn’t expecting requests for the second lesson on day one. So expect things to go wrong… and be at the ready to make running repairs. 5 - Remember that it’s an experiment ---- It bares repeating: Remember that it’s an Experiment*. This one cuts two ways: It’s a reminder not to over-egg the pudding. This is a Minimum Viable Product, not a Final Perfect Product. It’s also a reminder to measure. Your Minimum Viable Product is part of the Build Measure Learn loop. And if you don’t measure, you won’t learn. Recap ---- In summary: Launch before you’re ready There are more moving parts that you think Launch to a limited audience Be ready to make running repairs Remember that it’s an experiment https://www.youtube.com/watch?v=ark3b6d5i6A&list=PLngnoZX8cAn_vCE1plk4xhTWfJfvKEWs8
Views: 9308 Development That Pays
Minimum Viable Product
 
01:51
This video is part of the Udacity course "Engagement & Monetization | Mobile Games". Watch the full course at https://www.udacity.com/course/ud407
Views: 770 Udacity
Minimum Viable Product - How to Build a Startup
 
02:37
This video is part of an online course, How to Build a Startup. Check out the course here: https://www.udacity.com/course/ep245.
Views: 31575 Udacity
What is the Agile Analysis Technique Minimal Viable Product or MVP?
 
04:43
http://www.business-analysis-excellence.com - What is the Agile Analysis Technique Minimal Viable Product or MVP? Learn all about MVP as a business analysis technique is this short agile analysis course video.
Minimum Viable Product. What is the use of a MVP?
 
05:02
Read the article - https://www.cleveroad.com/blog/what-is-the-use-of-a-minimum-viable-product-infographic Do you know what the most frightening about apps is? The possibility of their failure. You invest money in your idea without knowing whether you will get ROI or not. However, the ambition to get to the top 5% of App Stores provokes entrepreneurs to give it a try. Fortune favours the brave, you may say. Sure. But we have a better alternative! It’s known as a Minimum Viable Product or MVP. MVP approach to app development stands out for the as early product launch as possible. Having a minimum set of features that provide only main benefits for users, the product will let you validate whether your idea is worth investing money. If something goes wrong, you have a wiggle-room to change the initial plan. No wonder such big names as Dropbox, Uber and Twitter started their business with an MVP. Watch our new episode of All About Apps to know everything you need about the Minimum Viable Product approach.
Minimum Viable Product (MVP): Letting Customers Help You Profit
 
30:31
Whether producing a software product for a new market in a startup, or introducing a major change in an enterprise - planning a minimum viable product is a good idea. When building a minimum viable product (MVP), you should select a feature that shows users your core value proposition, as well as two features that "delight". The core value proposition is a part of the Business Model Canvas, a visual tool created by Alex Osterwalder that you can use to determine which aspect of the business is being effected by a change. The "delighting" features provide something sexy for users that attracts potential customers due to it's sleekness, innovation, or ease of use. When planning what goes into an MVP, don't budget for only the MVP. Budget for enough to build software for 6-12 months that will adapt to feedback. Spend a small portion of the total budget to release the MVP, and use the majority of the remaining budget to adapt so you can deliver exactly what customers want - and in the way they want to buy it. These other "ways" than the product's features itself are the other aspects of the business model canvas. If you only budget enough for the MVP, you won't have money left over to adapt. Adaptation is the difference between a product that "meets needs" and one that "exceeds expectations". It is this latter category of products that cause companies to be leaders in their market and cause substantial growth. When selecting technologies for the MVP, don't box yourself into feeling you need to use technologies already familiar to the development resources you might have. Hiring a specialist in a technology that is faster to build prototypes and minimal products in can save substantial money. Should the market lead you to find that what you've built is successful, you can always change the technology used down the road to meet scaling challenges, if the original technology can't handle the volume. This is a GOOD problem to have, and means you've found a large user base - but until this happens, don't spend the time and money planning for it! You need as much budget as possible to simply ADAPT at first, and so your money is better spent with excess funds for adaptation than building out an infrastructure or technology stack that assumes a size of user base you don't yet have. Subscribe for more videos about Healthy Software Development: https://www.youtube.com/c/JaymeEdwardsMedia?sub_confirmation=1 Related Videos: "Lean Software Development - It's About Uncertainty!": https://goo.gl/4zeFRW You can watch a video about the Business Model Canvas here: https://www.youtube.com/watch?v=IP0cUBWTgpY "Agile Project Management - Is It Stopping You From Being Agile?": https://goo.gl/iXfTSH #programming #productmanager #mvp
Harvard i-lab | Creating Your Minimum Viable Product with Abby Fichtner
 
48:45
Do you have an idea for a startup but aren't quite sure where or how to start on your product? You can't just ask people what they want -- that's a great way to send yourself spinning in 50 different directions. And you can't just go off and start building the product you envision -- 9 out of 10 new products fail and If You Build It, They Will Come is not the path to success. Creating Minimum Viable Products allows you to quickly test out the assumptions you're making about your business, validate that customers are indeed interested in -- and willing to pay for -- your solution, and help you to prioritize your product's features. Hear case studies on what other, well-known startups have done and learn a number of MVP tools you can use to get your startup on the path to viability. Learn more about the Harvard Innovation Lab at http://i-lab.harvard.edu/ and follow us on Twitter at http://twitter.com/innovationlab and like us on Facebook at https://www.facebook.com/harvardinnovationlab
Minimum Viable Product: what it means for web development?
 
06:49
It's time for the second episode of Merixstudio's video blog! This time we wanted to talk about MVP, what it, is and how it influences web development and the work of software houses around the world. Let us know what you think! Don't forget to follow us on our social media channels: https://www.facebook.com/worldofmerix/ https://twitter.com/merix_studio https://www.instagram.com/merixstudio/ https://pl.linkedin.com/company/merix...
Views: 97 Merixstudio
Minimum Viable Product FAIL!!!
 
02:59
51. Minimum Viable Product FAIL!!! // There are some amazing MVP examples out there. Alas, this isn't one of them! When I made this cup holder, I told myself is was a Minimum Viable Product (MVP). Now I'm not so sure. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Let's break it down: 1. Is it a PRODUCT? It is in the sense that it was produced for a specific end user (Me!) And it's more than a prototype: it's been primed and painted and varnished. 2. Is it MINIMAL? Not really. This part is made of oak. If you know your timbers, you'll know that oak is a hardwood. Hardwood means that it's (a) expensive and (b) difficult to work. 3. Is is VIABLE? It's not terrible. It's easy to "park" a cup. And it holds the cup securely. But it has problems: difficult to pick up without spilling; no dust protection. Here's the thing: I could have discovered these shortcomings without making a not-so-minimal not-so-viable MVP. A quick and dirty PROTOTYPE would have done the trick. Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Minimum viable Products. There are some great examples out there. but today we're going to look at a really bad one. Hi this is Gary Welcome to Development That Pays I like to think that I know a fair bit about working in an AGILE way. I even know a little bit about working in a LEAN fashion. But I don't always DO what I KNOW. And today I want to show you a perfect example of me NOT doing what I KNOW. It's in my shed. And that's where we'll be heading... just as soon as I've made a nice cup of tea. All done. Let's go. Here we are. Not as untidy as usual - I must have been expecting you ;) Just pop my tea here. It's actually this cup holder that I've brought you to see. When I made it, I told myself is was an MVP. Now I'm not so sure. Let's break it down. Is it a PRODUCT It is in the sense that it was produced for a specific end user (Me!) And it's more than a prototype: this back panel has been primed and painted. And this bit has been varnished. That's more work than I would ever do for a prototype. What about Minimal Not really. This part is made of oak. If you know your timbers, you'll know that oak is a hardwood. Hardwood means that it's expensive. It has maans that it's hard - difficult - to work. This part here is angled. I don't have a power tool to do this - it had to be shaped by hand. And I can tell you it took ages. Finally, is is VIABLE It's not terrible. It's easy to "park" a cup. And it holds the cup securely. (Shame this is the only cup it works for.) There are a couple of things there are less than ideal: If I'm not careful and I jam my cup in too hard, when i pick it up the whole thing comes off. There's then a danger that I spill my tea, perish the thought! The second issue is to do with the environment. I work with wood. And power tools. That means sawdust. Lots of it. It goes everywhere, including into my tea. A holder with some sort of cover would have been a good idea. Here's the thing: I could have discovered these shortcomings without my not-so-minimal not-so-viable MVP. A quick and dirty PROTOTYPE would have done the trick. Thank you very much for watching If you enjoyed this episode please give it a thumbs up. if you hated it, give it a thumbs down - that's good too. If you'd like more videos like this, there's a new episode of Development That Pays each and every Wednesday. Click the big red button... and I'll see you on the other side. https://www.youtube.com/watch?v=VOjU3-veCVY https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 3618 Development That Pays
Lean Minimum Viable Products
 
03:03
A Minimum Viable Product is a tool for performing experiments in your business. It will help you quickly discover whether the assumptions you make in your business model are true or false.
Minimum Viable Product: An MVP from MDF!
 
04:34
37. Minimum Viable Product: An MVP from MDF! // Join me as I attempt to create a Minimum Viable Product for a VERY demanding client: my wife! ;) → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe 1:18 - Eric Ries' definition of a Minimum Viable Product (MVP) 1:41 - Step 1 - Basic SketchUp 2:22 - Step 2 - Basic Prototype 2:58 - Step 3 - Printer swap 3:19 - Step 4 - Updated prototype 3:53 - Step 5 - Updated Sketch-up Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Wood. Check. Saw. Check. Drill. Check. Glue. Check. Let's build a Minimum Viable Product! In the last couple of episodes, we've been looking at Minimum Viable Products. Today I'm going to attempt to make one. Out of MDF. Peripheral Proliferation ----- This is my iMac. I love this machine. It's a pleasure to use. But the REAL reason I love it, is that it's the first computer that's pretty enough to be allowed into the kitchen. It looks good. At least it did when it first arrived. Then we added a printer. Then an external drive. Then an another external drive. And with them came lots and lots of wires. My wife, Sheila, has a word for this peripheral proliferation: unacceptable. The brief ------ The challenge, then, is to hide all the guff... without too much impact on the usability of the printer. I can feel an MVP coming on! Eric Ries - author of The Lean Startup has a good definition of MVP: "[the] version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort." The operative words here are: "Validated learning" and "Least effort". Neither of these are natural for me: I'm more of a zero research, over-engineered kind of guy. This is going to be... challenging. My first port of call: SketchUp. Do you know SketchUp I really like it. But I have to be careful not to get carried away and go too far with the design. It's important to be... minimal. Here's a printer and two drives. Think the printer will go on top with the drives underneath. Going to make a shelf big enough of the printer. Plus a bit of extra space around the edge. Move it into place. And copy it. And... And nothing. I have the basic measurements I need to build something. A here it is. Question: is this a Minimum Viable Product It's minimal, certainly. But as we've talked about previously, it's the customer that decides what's viable. The customer - that's Sheila - wasted no time in letting me know that this was NOT viable. Not even close. Let's call it a prototype. Printer fits. Excellent. Better just check that everything is useable. Pop a spot of paper in the printer. Ah. That's vexing. Hadn't thought of that. Either I'm gong to have to make the cabinet much taller... or.... .... get a new printer! Never liked that old printer anyway :) This one's about the same size, but it has paper tray. Perfect. Ah. This is annoying. Didn't spot that bit before I bought it. Tried to remove the out-feed thing without success. I'm going to have to change the design to accommodate it. Glad I didn't lavish too much love an attention on the first prototype: it's really been sliced and diced. It's morphed into something... really ugly. If anything, it's less viable than it was before. The new printer fits. Excellent. We'll need a flap on the front. Another issue I hadn't foreseen: the new printer has screen. And the screen is hard to see. I'll need to have a head-scratch about that. Back to SketchUp. This is more or less a cleaned-up version of Prototype II. The drop-down flap is more work than I'd hoped for, annoyingly. But I'll save some time by having this lower panel fixed. Access to the drives - and the inevitable (wiring) spaghetti - will be from the back. Think at last I'm ready to build an MVP! Join me next time to see how it turns out. https://www.youtube.com/watch?v=cIe8Xt9nByY https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 3667 Development That Pays
The Lean Startup - Minimum Viable Experiment without Measurement?
 
06:41
I launched an MVP. In all the excitement something important got left out. The most important aspect of a Minimum Viable Product: The Measurement! It’s five weeks since I launched "Scrum vs Kanban the Mini-course". It was much more work than I was expecting. In the rush to get it live, something important got left out. Something that is, arguably, the most important aspect of a Minimum Viable Product: The Measurement! Luckily, it’s never too late for a great Experiment! But when I came to think about the measurement side of things, I got stuck; I’m going to need your help on this one. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe ------------------- 109. The Lean Startup - Minimum Viable Experiment without Measurement? So you've launched your MVP Your Minimum Viable Product. Congratulations! But did you forget something Did you forget that it's an EXPERIMENT Did you forget.. about the MEASUREMENT Five keys to a successful MVP launch ------- If you say last week’s episode, you'll know that I laid out FIVE keys to a successful Minimum Viable Product launch. No 5 was the big one: Remember that it's an EXPERIMENT. Experiment means MEASUREMENT. I dropped the ball ---- I launched my Minimum Viable Product about 5 weeks ago. I confess that I was more concerned with getting it out there than performing a great experiment. But I believe it’s never too late for a great experiment. Now that it’s out there, I’d like to improve the measurement side of things. And I’d like to involve you in the process of deciding what should be measured. If you’d be up for it. The end to-end process --- I guess we should start with a look at the system under test. “Scrum vs Kanban, the mini-course”. In a three-lesson - three-video - mini-course. The videos are delivered by email - sent on consecutive days. To get the course, you have to first find your way to the course landing page, AND click the button, AND fill in the form. That’s the core system. Upstream, there are a bunch of potential paths to the landing page: The socials (such as Facebook, LinkedIn and Twitter) Search engines (such as Google) YouTube Downstream, there’s an email that goes out on the fourth day. (I say more about that in a moment.) The person is then added to my mailing list - that’s the regular Wednesday email. Think that’s the whole thing. Plenty of moving parts. Plenty of things that I could measure. But what should I measure What would you measure The low-hanging fruit ------- There’s some low-hanging fruit here: Conversion rates on the upstream part Watch figures for each of the lessons. But the downstream area. That where things get a trickier. That’s where I’m struggling. That where I need your help. To tee things up, I’d like to play you a clip from episode 85. It concerns the Lean Startup Build-Measure-Learn loop. “... the flow here is in a clockwise direction. Of course it is. It would be weird if it wasn’t. Anyway. It’s a flow of doing. A flow of action. What’s clear if you read the book, is that there’s also an anti-clockwise flow. It’s a flow that you’ll struggle to find in a Google Image search - although I did find one eventually. Check this out: Assumption, Metric, Experiment Notice that it’s a flow of “thinking” rather than a “doing”. A flow that comes - just case it’s not 100% obvious - before the “doing” The hidden anti-clockwise / counter-clockwise flow is, in my opinion, the key that unlocks the power of the Build Measure Learn model. Thank you Gary. Wise words indeed. To work out what to measure - the metric - we need to start with the assumption. In the same episode, I took a stab at it: “The Mini-course will result in more email opt-ins” Definately measureable. And easy to measure. Excellnet. Job Done. The End. Not so fast. There’s a more important assumption that’s hiding between “The Mini-course will help to grow my audience” “The Mini-course will result in more email opt-ins” I don’t just want people to opt-in. I want them to stay opted-in. Consider these two cases: Person A that stumbles across dtp… sees a link to a cheat sheet.. Downloads it. Person B stumbles across dtp… sees a link to the Mini-course.. Signs up. Goes through all three lessons. QUESTION: When Wednesday rolls around and I send out an email to say “check out today’s episode” Who is more likely to open the email Who is more likely to click to watch the episode. And… who is more likely to click the unsubscribe button My assumption is that The assumption that wraps this all together is something like. “The Mini-course will result in more emails subscribers with high engagement.” Easy t https://www.youtube.com/watch?v=FZEKdQXVP0g&list=PLngnoZX8cAn_vCE1plk4xhTWfJfvKEWs8
Views: 1457 Development That Pays
The Art of the MVP: 5 Steps to Building a Functional Minimum Viable Product
 
01:28:19
Over the past several years, the lean startup movement has made the Minimal Viable Product (MVP) a key approach to incrementally discovering effective products and services. In this talk, Levent Gurses will discuss a 5 step MVP process for building great minimum viable products that's been used in real client engagements. His process has been developed working with more than 20 enterprise full-stack and mobile clients over the course of several years. Topics will include the challenges of creating the MVP vision, scoping the activity, what should an MVP cost in time and money, and what should you have when you are “done”. Not only sharing his tales of MVP development, he will provide insights in how he's developed methods to effectively drive vision and development execution. What is an MVP? A product that has the absolute minimal set of core features necessary to prove a hypothesis, generally linked to commercial success or market validation. The MVP seeks the highest return on investment versus risk. The Rise of the Lean Startup Movement The lean startup movement came about as a result of analysis of many startup successes and failures. Development timeframes have become shorter and customer engagement has increased, which is helping companies better product-market fit and a path to success. Presentation Outline: • The MVP Vision (What will I have at the end of the effort?) • Brief history of the lean startup movement • Scoping • Budgeting for MVP • Features: The MVP Way • Essential vs. peripheral features • Must have to prove a hypothesis vs. nice to have • Assembling a team • Hiring contractors or vendor firms to build the MVP • Choosing a technology • Fake it until you make it: How to create mock features for an MVP Presenter Levent Gurses - Developer, speaker, and entrepreneur, Levent is the founder www.movel.co, an enterprise mobility company based in Virginia. He’s a nationally-recognized leader in mobile technologies and is a frequent speaker at tech communities on mobile and full-stack development. Levent holds a BS in Computer Engineering and is a Certified ScrumMaster and Certified Product Owner.
Views: 419 Movel
Definition of Minimum Viable Product
 
01:53
Greg Cohen is the author of Agile Excellence for Product Mangers and a Lean Product Management expert. He is here today to help us define Minimum Viable Product, or MVP. First Greg explains what an MVP actually is and why it's critical. The idea of the MVP was initially brought on the scene by Lean Startup although these days the meaning can be very different depending on who you ask. What we have found to be the most straightforward and useful is to think of the MVP as an actual product. It is the minimum product that is useful to a segment of your customers. Specifically a segment of early adopters who would rather have your product in it's current format that wait any longer for an improved version. The Minimum Viable Product is something that can actually be put in the market place and used by customers in real life. In addition to practical utility, it's important to consider whether the customers are inclined to exchange value for the product, i.e. pay for it. Basically a Minimum Viable Product is something that your customers are willing to pay for and that has just enough functionality to solve their pain point. If you would like to learn more about the fascinating world of Lean Product Management, attend Greg's upcoming webinar: 6 Lean Steps to Get to Market in Record Time https://theaipmm.lpages.co/6-lean-steps-to-get-to-market-in-record-time/ and download his free book: Lean Product Management http://280.gr/2hmMFVk
Views: 553 280 Group
Minimum Valuable Product in Mobile App Development. App MVP Explained
 
04:09
Learn what role plays minimum valuable product in app development. How to create app MVP and what are the benefits of the early product release. Test your app idea with minimal money and time invested / More at http://yalantis.com/blog/mvp-explained-by-yalantis-updating/
Views: 4617 Yalantis Pulse
AGILE TALK SHOW - S2E15 - Minimum Viable Product | MVP
 
17:43
Hi folks, good morning, good evening, good night! Welcome to EP 15, MVP! MVP is how we deliver products in an Agile way, its how we practice course correction and incremental creation. We are honored to present you all with a few special guests, who accepted the challenge to share their experiences with MVP work and product creation,, They are working on the second MVP delivery of a Agile Glasses, designed to help identify Bad Habits or Good habits within agile teams. Thank you @maik @Marcelo and @karen dunder for your participation in this weeks Episode and your hard work at our MVP projects. We love you guys! #berealtobeagile
Software Estimates: Minimum Viable Product
 
07:11
Minimum Viable Product (MVP) is a common first step in software product evolution. It is usually created within a limited budget, while the product requirements are not fixed strictly. Nevertheless, the product owner requires an estimate for development. Here, we'd love to show all opportunities and pitfalls that every product owner needs to know in order to have a successful start of the project and get more precise estimates. Read full article here: https://mobidev.biz/blog/software_estimates_minimum_viable_product
Views: 811 MobiDev
What to Build First: Defining MVP with Scenarios - Agile on the Beach 2018
 
43:48
Tatiana Kolesnikova and Arvid Torset Norway – Seniordev Product Management (F) 2018 Thursday 15:15 - 16:00 Session type: Lecture Session level: Suitable for all Please note: apologies for the darkness of this video. Quality has been improved as much as possible What to Build First: Defining MVP with Scenarios What to Build First and Why: Goal-Oriented MVP What is the minimal version that should be build? We ask this question when we configure both a brand new product or a new set of functionality in an existing one. How to define what is in and what is out? How to leave emotions and company politics out of MVP equation? Goal-oriented MVP is a practical implementation of Lean Business and human-oriented design principles in development process. It is a methodology that helps the team define what to build first so that the result is really minimal, complete and helping reach business goals. The centre of this methodology is outcome scenarios: understanding how the first version of the product will work or rather how people will work with this first version. During this lecture we cover the whole process – from initial idea all the way to the backlog of the first release. What we suggest is not a strict framework, but a set of flexible techniques that are applicable in different projects with different stakeholders and team composition. The participants will learn: • How to decide what is really necessary to build in the first version of the product and what can easily wait until stage two; • How to make this first version as small as it can be and send it to the market as early as possible; • How to proceed from the overall vision all the way to well structured Agile sprints. TATIANA KOLESNIKOVA - BIOGRAPHY Norway – Seniordev – Head of Design UX design consultant with academic background in both IT and design, Tatiana’s main role is to breach the gap between these two disciplines. She has extensive working experience in information architecture, usability analysis and full range UX and UI design both in-house and as an external consultant. Now as a head of design at Seniordev, Tatiana’s responsibility is to facilitate defining product strategy, organize collaboration between design, development and product parts of the teams and train and mentor UX and UI designers. She kick starts about half a dozen projects every year and making it as effective as possible is her most urgent need. Therefore she is deeply interested in the the most efficient methodologies and techniques in her field: she studies the experience of others, applies them in her everyday work and speaks about the results at tech and design conferences. ARVID TORSET - BIOGRAPHY Norway – Seniordev – Technical Architect Building software development teams from ground up has been Arvid´s main specialty for more than ten years. His task is to assemble the technologies that are suitable for a particular business problem and then find the right set of people and skills for them. He has done this for clients in hugely diverse domains and also for several companies where he was a co-founder. Work on all these projects have revealed the same problem: traditional tools and artefacts are not very suitable to establish efficient communication in team that try to work lean way. It is a new process that is needed, the process that ties all the stakeholders and developers closer together – from the CEO to the QA. Arvid is working on creating this process and teaching the teams to sustain and evolve it. Agile on the Beach is a leading annual conference in Falmouth, Cornwall UK. Since 2011 Agile on the Beach has been a two day agile conference, set on the Cornish coast with a beach party in between. The conference explores agile software, products, teams, business and practices. With over 400 attending, the conference hosts 50 seminars and workshops to provide the ultimate agile learning experience, along with ample opportunities for networking at its 3 evening events. www.agileonthebeach.com
Views: 314 Agile on the Beach
Silicon Valley - sales and product
 
04:09
Clips from Silicon Valley, season 3, episode 2 Tinny audio quality b/c I used my internal mic
Views: 675827 Tracy Kennedy
The Minimum Viable Product Pattern
 
02:41
An MVP, or Minimum Viable Product, is often assumed to be the minimum feature set needed for an end user to obtain value. Dr. Ian Mitchell explains why this is not the case, and why an MVP is really a tool for validated learning and testing hypotheses as cheaply as possible.
Views: 223 Agile Patterns
Minimum Viable Product part 1
 
02:05
Basic information about the MVP as Eric Ries describes it in the Lean Startup. Use real customer data to develop your product!
Views: 3694 Jasper Alblas
The Wizard Of Oz Minimum Viable Product (MVP)
 
03:22
36. The Wizard Of Oz Minimum Viable Product (MVP) // Minimum Viable Products come in all shapes and sizes. Today we'll throw back the curtain (geddit?) on the Wizard of Oz MVP. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Key take-aways: - Zappos is the best example I know of a Wizard of Oz MVP - Zappos began in 1999 - They needed to know if people would by shoes online - They visited shoe shops and photographed shoes. These photos went on to the website - If someone ordered a pair of shoes, they would return to the shop, buy the shoes, and ship them to the customer - Note that from the customer's point of view, everything appears to be fully functional. - Other example of the Wizard of Oz MVP include Aardvark and Cardmunch Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Minimum Viable Products come in a range of shapes and sizes. Today we going to look at the one with the coolest name. Join me as we throw back the curtain on the Wizard of Oz MVP. 1999 ---- Its 1999. You're thinking about selling shoes online. You know that people buy shoes. What you don't know is whether people will buy shoes online. (It's never been tried before.) You devise a cunning plan. You go into town. You go into shoe shops. And you ... err... take photographs of shoes! Later, you upload the photographs to a website. What happens when someone buys a pair of shoes No problem. You pop back into town. You pop back into the shoe shop. And you buy the shoes! You then ship them off to the customer. Did you spot it ----- This, as you might have spotted, it the story of Zappos. It's the best example I know of a Wizard of Oz MVP. So called, because from the customer's point of view, everything appears to be in place. The customer has no idea that behind the scenes it's a little bit... manual. in Zappos case, all of the going to town, going into shops, taking photos... .... going back to town, going back into shops, buying shoes... is hidden behind the curtain. From the customer's point of view, the Zappos business looked and operated like a fully functional eCommerce operation. Different world ----- I love the Zappos story, with one teeny weeny reservation. It's not directly applicable to my world. For one thing, it's a long time since I dealt with a physical product. Perhaps you thought the same thing Let's look a couple of other examples. In each case, see if you can guess what's behind the curtain. Aardvark ---- Aardvark was about connecting people with questions to people with expertise. Behind the curtain Perhaps a neural network of stunning complexity No. A bunch of Interns! Cardmunch ------ Cardmunch is an app that scans business cards and converts them into contacts. It somehow managed to transcribe blurry photos of business cards better than any other Optical Character Recognition (OCR) system at the time. A technological breakthrough Nope. Behind the curtain Amazon’s Mechanical Turk! Amazon’s Mechanical Turk has a curtain of its own. What's behind the green curtain People! Minumum vs. Viable ----- One final thought before we click our heels together and head back to Kansas: David J Bland says the hard part about MVPs is that ... you decide what’s Minimum... ... the customer determines if it is Viable. A Wizard of Oz MVP all but guarantees a high 'viability' rating: the 'minimal' (usually manual) process is hidden behind the curtain. The customer, has no idea that corners have been cut. https://www.youtube.com/watch?v=VPVec5eupTY https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 9761 Development That Pays
The Lean Startup - Minimum Viable Experiment RESULTS + FREE CHEAT SHEET
 
07:20
It's time to reveal the RESULTS of our real life Minimum Viable Product / Minimum Viable EXPERIMENT. Watch as "Agile Done Right", "Real Life Agile" and "Agile That Pays" go head to head! - Will we be cleared for take-off? Cleared to PERSEVERE? - Or will we before forced to regroup and try something else? To PIVOT? All will be revealed in this week's episode! Grab your free Cheat Sheet: http://www.developmentthatpays.com/cheatsheets/the-lean-startup → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 ------------------- 92. The Lean Startup - Minimum Viable Experiment RESULTS + FREE CHEAT SHEET Previously... We pulled on to the “Lean Startup” runway, and pressed the starter button on our Minimum Viable EXPERIMENT. Today... We’ll look at the results. Will we be CLEAR to PERSEVERE Or will this PILOT need to PIVOT Recap Welcome back to a rather exciting stage in our Lean Startup journey. Today I’ll reveal the results from our Minimum Viable Product / Minimum Viable Experiment. To recap very quickly: this whole thing started with a plan to create a 5-day mini-course. And to do so using principles from The Lean Startup - the book by Eric Ries. We looked at the Build Measure Learn model, and its hidden counter-clockwise flow: Assumption, Metric, Experiment After some waffling I came up with this assumption: “The 5 Day Mini-course will result in more email opt-ins” Which implied this metric: “Email opt-ins” But what would be a good experiment What might we use as our Minimum Viable Product We looked to Zappos, Dropbox and Buffer for inspiration. Long story short: Buffer’s “fake door” approach seemed the most applicable, even though it would FAIL to provide the METRIC we were looking for: a direct measurement of email sign-ups. It would, however give us a direct measurement of INTEREST and DESIRE - necessary precursors to the the ACTION of email sign-ups. And in the absence of an alternative, we pressed on. Buffer's MVP ---- Buffer’s MVP delivers the old one-two by (a) promising something awesome, then (b) apologising that “it’s not quite ready”. I stole it, painted it yellow and dubbed it the Mundane MVP. All that remained was a mechanism to get people to the Landing Page. A Facebook advert would seem to fit the bill. Set things up correctly, and we get two very useful metrics: The proportion of people that see the ad that go ahead and click through The proportion of people that get to the Landing Page and click to "stay informed" I know what you’re thinking: why run one experiment when you could run three Excellent point. You were good enough to provide 100+ possible names for the course of some kind, from which we selected a final three. (Actually four. One didn’t make it past Facebook’s profanity filter.) Three experiments - differing only in the name of the course. That’s the theory. Wanna see how it looks in practice The Real Experiment ---- Here’s the ad in my Facebook News Feed. Before I click the button, I should warn viewers of a nervous nature should move away from the screen Ready This is the Landing Page. Not sure what was thinking about putting my mug shot in there. Anywhere, there’s a nice big action button, a few bullet points, and another big button. Both buttons lead to the “Thank you” Page - which should probably be called the “I’m very sorry page”. A word of caution ---- One last thing before I show your the results: it’s all too easy when running an experiment to look at the result and convince yourself that the results confirm... whatever you want them to confirm. We’re not going to fall into that trap, are we After all. We have an important decision to make. We need to decide whether to persevere, or pivot. So before looking at the results, we should have a feeling for what good and bad looks like, starting with this metric: the click-through rate from the Ad to the Landing Page. According to Wordstream, the average across all industries is just 0.9%. My targeting was rudimentary: Region:USA Age range: 25 - 65+ Interests: a short list of Agile-related keywords Not very sophisticated. So I’ll be surprised to get a result above 1%. What about the second metric: The click-through from the Thank You page Well, I’d like to think that anyone who made it this far would be quite likely to click through. Unless, of course, my ugly mug puts them off. Perhaps somewhere in the region of 50% The results ----- No more stalling: here are the results. The adverts for "Agile Do https://www.youtube.com/watch?v=K8NcF9SmkeM&list=PLngnoZX8cAn_vCE1plk4xhTWfJfvKEWs8
Views: 1192 Development That Pays
UX Easy - what's an MVP?
 
02:52
Each episode, Adam from Natural Interaction will take you through a complex UX concept or phrase, breaking it down into something easy to understand - and all in under 5 minutes! This is our first episode and it's focused on one thing: MVP, or Minimum Viable Product. Enjoy!
Views: 191 Natural Interaction
Pluralsight trailer for: Agile Requirements Process: Idea to Minimum Viable Product
 
09:37
This is a 10m trailer for a 2 hour course on taking a software idea and turning it into a minimum viable product. See the full video at http://osmy.in/1Igyx2C
Views: 259 Rusty Divine
Game Development :  Minimum Viable Product
 
02:54
This video shall give you some game development tips on your journey towards making a business by creating games. This lecture shall explore what is Minimum Viable Product and its importance towards success. You can Find me on Facebook : https://www.facebook.com/Funny-Finance-Guy-628211513987752/ If you want to learn more please find me at : https://www.udemy.com/fundamentals-of-accounting-for-business-owners/learn/v4/overview
Views: 1124 Funny Finance Guy
MVP vs MMF
 
02:19
Views: 134 dvkdk
The Lean Startup - Mundane MVP™ + FREE CHEAT SHEET
 
04:38
87. The Lean Startup - Mundane MVP™ + FREE CHEAT SHEET // Grab your FREE Cheat Sheet: http://bit.ly/lean-startup-cheatsheet Last time, we looked at MVPs from Zappos, Dropbox and Buffer. This time, I’m going to borrow - heavily - from one of them. Can guess which one? I'm going to be designing an end-to-end Minimum Viable Product - Minimum Viable EXPERIMENT, if you prefer. It's the most basic - the most MUNDANE - that I can think of. I'd be very interested to have your thoughts on the model... especially if you can think of a way of going even MORE mundane! LET ME KNOW IN THE COMMENTS BELOW. Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Previously... We looked at 3 awesome Minimum Viable Products. Today… I’ll attempt to design something a little more... Mundane. On track -- Our “course-of-some-kind” is still on track. We've successfully navigated around a couple of traps: The trap of jumping straight in and “building the damn thing”. And the trap of asking customers what they want. (Think surveys and polls.) I introduced this model - the Build-Measure-Learn loop - and revealed its hidden power: the Assumptions-Metric-Experiment anti-clockwise flow. That led us to Minimum Viable Products aka MVPs. And we looked at the MVPs of Zappos, Dropbox and Buffer. Of the three, Zappos is by far my favourite. It was a genius way to determine if people would buy shoes online - at a time where few people were buying anything online. It was the perfect EXPERIMENT for its time. But now that we can get EVERYTHING online, it’s not an example that’s particularly transferrable. Dropbox’s MVP - the demonstration of a working prototype - is more transferable. And then there’s Buffer’s MVP. Not nearly as impressive as the other two. It is, dare I say it, rather mundane. But very, very steal-able. Shall we try it out for size We’ll need a landing page. To outline the details of the course. Listing the benefits. Encouraging people to sign up. A big button, of course. And clicking the button leads to a Thank You page. And there’d be an opportunity for people to enter an email address - so that we can get in touch when the course is ready. Traffic --- Now all we need to do is get people to this page - the landing page. I could put a link on my website. I could put a link in the description of my videos. But there’s a problem with that: I’d be talking to people… that are already here. It would be a “cleaner” experiment if the visitors to this page were people other than, well, other than you. So I’m thinking that running an ad would be a good idea. Facebook ads are capable of quite specific targeting, So I could get an ad in front of people that are interested in Agile… or Scrum… or Kanban as appropriate. End to end, the system - our Minimum Viable Product, Minimum Viable EXPERIMENT if you prefer - looks like this. Let’s just check in with the model; the hidden part of the model: Assumption: The course will result in an increase in the number of email subscribers. Metric: The system would generate a range of numbers: % of people that saw the ad… and clicked through % of people that made it to the landing page… and clicked the button % of people that made it to the ‘thank you’ page… and entered an email address As was the case with Buffer, it’s not a perfect experiment: the percentage of people who enter an email address to “express interest” will be much lower that the percentage that would email an email address to get their hands on “the real thing” (our 5 Day Mini Course). So the final metric will be skewed. The other metrics should be accurate. The Mundane MVP ----- I rather like this Mundane MVP. And and I'm quite taken with the notion of Mundane MVPs. So I'd love to know your thoughts on this model. And I'd love to know if you can think of an MVP that's even more mundane! Let me know in the comments below. https://www.youtube.com/watch?v=6WopoEusJkE&list=PLngnoZX8cAn_vCE1plk4xhTWfJfvKEWs8
Views: 1306 Development That Pays
Minimum Viable Product: Part 2
 
00:56
I decide to build a MVP as quickly as possible so that I have something concrete to work with. Previously I've had business ideas and then lost interest when it has taken too long to take action.
Views: 8 BeBirbal
Minimum Viable Product
 
01:23:25
Views: 60 ideatoipo2
COACH AGILE : L'APPROCHE MVP
 
02:12
L'approche MVP (Minimum Viable Product) est une stratégie de conception par la réalisation d’une version produit simplifiée qui permet, de manière itérative et incrémentale, à une équipe de recueillir la quantité maximale d’apprentissages validés sur les early adopters. Elle permet de répondre très vite au besoin client et de le satisfaire à terme plus qu'avec les méthodologies classiques. Vous trouverez tous les détails sur cette approche sur le site http://coach-agile.com/2015/04/coach-agile-approche-mvp/ A bientôt !
Views: 2611 COACH AGILE
Building an MVP (Minimum Viable Product) II
 
04:46
38. Building an MVP (Minimum Viable Product) II // Wood has been cut, glued and screwed. The spray gun has made and appearance. Hardware has been fitted. It's time for the BIG REVEAL! → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe I don't think I need to say it, but the point of the exercise was not to encourage you to take up carpentry :) No, the point of the exercise was to - hopefully - uncover something useful about the process of creating an MVP (Minimum Viable Product). Ideally, something that would be just applicable in my "day job": software development. And I did learn! In ways that surprised me. My experience of Step 6 - the final build of my MVP - was especially... WEIRD. Enjoy the video! Remember to comment, like and share :) LINKS -- Part I: https://www.youtube.com/watch?v=cIe8Xt9nByY Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Wood has has been cut, glued and screwed. The spay gun has made an appearance. Hardware has been fitted. It's time to reveal the "MDF MVP" Hi this is Gary. Welcome to Development That Pays And welcome back to the the second part of the Minimum Viable Product build. If you missed Part 1, you should find a link on or around this video. I don't think I need to say it, but the point of the exercise was not to encourage you to take up carpentry. No, the point of the exercise was to, hopefully, uncover something useful about the process of creating an MVP. Something that would be just applicable in my "day job": software engineering. I did learn. In ways that surprised me. My experience of Step 6 - the final build of my MVP - was especially... weird. Step 1 ---- This was the 'back of a fag packet' level of design. Compare this with other things I'd done in SketchUp, and you'll see that I was holding back, trying to me "minimal" Step 2 ----- Again, so minimal by my standards. I even went as far as missing out one of the shelves! In terms of viable... I knew the printer would fit - I'd taken the dimensions directly from SketchUp But there was an 'unknown unknown' (I'm sure you spotted it. But I didn't) The damn paper feed! In the language of software development: the prototype passed the "unit tests" of: wide enough high enough deep enough. But it failed the 'behavioural tests' of "as a user, I must be able to load A4 paper" "as a user, I must be able to print on A4 paper... and catch the paper as it comes out of the printer" Step 3 ---- I thought long and hard about how get around the paper problem... ... but I wasn't happy with any of them. So it was out with the old (printer) and in with the new. Think that's what the Lean community would refer to as a 'pivot'. Step 4 ----- This second prototype served a couple of purposes: match dimensions of the new printer extend the "prototyping" to include the wheels (which I did with four sticks of wood!) And to check the overall height, to make sure it would fit under the table. These were all about ensuring that the thing would be viable. I also uncovered another "unknown unknown": the difficulty in seeing the printer's display panel. Step 5 ---- Spet 5 took me back to SketchUp for the final time. Although the eagle eyed among you may have spotted that I snuck in an extra shelf. What can I say. It's not easy for me to me "Minimal" At this point you might be thinking: 'Hold on a second, this is just prototyping ' Yeah. I had that thought too. I think we're okay: the ideas of 'minimal' and 'viable', I really took them to heart. They became my 'prime directives'; I was much more focussed than usual on creating something that would be viable. And I tried (not always successfully) not to embellish. So, yes, it's prototyping. But it's been prototyping for an MVP, rather than for a PRODUCT, And the two feel different. Talking of feeling different. Time to Step 6. Step 6 ---- Okay. This was weird. I've built a lot of stuff. But this build, it was different. It FELT different. I once heard someone talk about operating as if you have 'one foot on the accelerator and one foot on the brake'. That's how it usually feels when I'm building something. Guess is because I'm building... and designing... and wondering-if-I'm-building-thing-right-thing the whole time. Not this time. I just got on and built it. Just like that. Forward gear all the way. I suppose with a couple of prototypes behind me - and 'just' an MVP in front of me (rather than an must-be-completely-perfect-final-product) - means there's really nothing left to worry about. It's an incredibly satisfying mode to get in to. The Reveal --- it's time for the big reveal. Viable It 'works' https://www.youtube.com/watch?v=4_sL_tOu2Xc https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 1832 Development That Pays
Planning Your MVP: Lean Canvas & User Stories
 
49:57
Video recording from the webinar. Slides: https://www.slideshare.net/maxsemenchuk/planning-your-mvp-lean-canvas-user-stories
Views: 290 4IRE labs
MVP - Minimum Viable Product
 
04:43
Co to jest MVP (Minimum Viable Product) i czy faktycznie jest on niskiej jakości? Patrz także: https://bialko.eu/agile/mvp-minimum-viable-product/
Views: 106 #białko
Silicon Valley Seizoen 1 - Preview afl.01 'Minimum Viable Product'
 
00:31
Bekijk hier de preview van aflevering 1 van Silicon Valley 'Minimum Viable Product'. Vanaf 7 april te zien bij HBO. http://www.itshbo.nl/series/silicon-valley/seizoen-1
Views: 1130 HBO Nederland
Começando o seu MVP - Minimum Viable Product
 
05:48
https://www.mindmup.com/ https://moqups.com/ https://marvelapp.com/ https://bootstrapstudio.io/
Agile Development 101 Ep 02: Product Roadmap and MVP
 
11:53
In this episode, I have just completed a 1.0.0 release and am looking to create a roadmap for my product. I plan for a 2.0.0 release and reduce the functionality as much as possible to come up with an 'MVP' (Minimum Viable Product).
Views: 86 James Burgess
Hacking Painting: Minimal Viable Painting (MVP) Method Explained
 
03:17
In this video, the creator of #techgiants art project explains the MVP - Minimal Viable Painting Method she developed to paint tech entrepreneurs in an agile way by crowd-sourcing feedback from friends on social networks: 1. draft painting 2.feedback via WeChat 3. Iteration More at: techgiants.tumblr.com
Views: 73 Chenyu Zheng
De l'idée au Minimum Viable Product - Méthode Agile | Matters Meetup | Thomas Meyers - Meetup
 
26:54
Vous avez une idée de produit et ne savez pas comment la mettre en oeuvre ? Cette vidéo explique comment passer de l’ébauche d’un projet au Minimum Viable Product avec les méthodes Agile. Subscribe : http://bit.ly/2EHSdU7 Chapitres dans la description. Pour participer à nos meetups : http://bit.ly/2G3sV3v https://matters.tech/ Dans ce Matters Meetup, retrouvez les étapes clés pour piloter votre projet, de l’idée au Sprint 0. Avec l’exemple du Lean Canvas de Dropbox, Thomas Meyers vous aide à gagner du temps, à vous poser les bonnes questions et à trouver les solutions adaptées à vos problématiques. Utiliser l’approche MVP, c’est réduire les risques et s'adapter rapidement, poser son idée et tester ses hypothèses. CHAPITRES - Qu'est-ce qu'un MVP ? 1:01 - Pourquoi faire un MVP ? 2:05 - Lean Canvas d'un MVP avec l'exemple de Dropbox 4:22 - Comment réduire le risque ? 13:13 - Conclusion 19:40 - Questions/Réponses 20:48 Blog : https://blog.matters.tech/ Twitter : https://twitter.com/matterstech?lang=fr Linkedin : https://www.linkedin.com/company/inovia-team/ Facebook : https://www.facebook.com/matterstech/ Instagram : https://www.instagram.com/matterstech/
SCRUM
 
39:47
Everything is a Remix https://vimeo.com/139094998 Making Your First Game: Minimum Viable Product https://www.youtube.com/watch?v=UvCri1tqIxQ&feature=youtu.be
Views: 21 Marcus Ingvarsson
Scrum vs Kanban - The Cheat Sheet Episode
 
03:58
69. Scrum vs Kanban - The Cheat Sheet Episode // Download your FREE CHEAT SHEET: http://bit.ly/scrum-vs-kanban-cheatsheet Did you see the previous episode? Seems it was very well received: more than 3000 views in its first week. (If you missed it, you can find it here: https://www.youtube.com/watch?v=rIaz-l1Kf8w) Embarrassingly, the Cheat Sheet that went with it was awash with typos. I was inspired to create a brand new version. Hope you like it. Video credit: https://www.youtube.com/watch?v=3bO-lP4pric Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Previously... A well-received episode on the differences between Scrum and Kanban. Today... Agile Inception. And a Cheat Sheet. Scrum vs Kanban ------ Did you see the last episode It was on the subject of the Differences between Scrum and Kanban. I wouldn't be mentioning it today... but for two things: The video did rather well. Not quite "Viral", but getting there. This video came with an accompanying Cheat Sheet. Let's just say... it wasn't my best work. Inception ----- What has any of this got to do with Inception Rewind a fortnight or so, and the video and the cheat sheet on the subject of Kanban and *Scrum ... were themselves backlog items. Backlog items in what is, I suppose, a Scrum system. I publish a new video every Wednesday, so my Sprints are a week in duration and run from Wednesday to Wednesday. Two weeks ago on Wednesday, this episode joined the Sprint Backlog. And I set to work. On the Video. By Sunday, I knew I was in trouble: there was a ton of work still to do on the video - and I'd given no thought to the Cheat Sheet. Monday... no Cheat Sheet Tuesday... no Cheat Sheet. Wednesday: decision time. The easy options would have been to remove all reference to the Cheat Sheet from the video. But I was curious to see how well it would be received. Would anyone even download it I decided to go for it: The video was uploaded before I left for work. The Cheat Sheet was created - from start to finished - in my lunch break. As I said earlier, the video did quite well. As did the Cheat Sheet: so far, it's been downloaded 55 times. Which is (a) Amazing and (b) Mortifying. 55 of you have a document from me containing... spelling mistakes! (I don't usually do spelling mistakes.) At emotionally challenging times like this, I'm often comforted by Three Letter Abbreviations: I'm classifying my cheat sheet as an MVP, a Minimum Viable Product. It was was certainly minimal. It was also viable - just. And it did what every good MVP should do: it informed: The moment I saw that people were downloading it, I started work on a new version. And I've really gone to town with it. Pictures and everything. It's even got half-decent spelling! The "Unfortunate 55" have already received the upgraded version from me by email. For everyone else, you can get your copy from my blog via a link that you'll find somewhere around this video. Minimum Viable Product ------- Now, before you go and grab your copy, there's something you need to know. Don't tell anyone, but this new shiny version is also... an MVP. Less minimal and more viable that the previous one. But an MVP nonetheless. I'm already working on the next version. But this time I'm going to need your help. So when you get your copy, I would be SUPER GRATEFUL if you could come back here and let me know your thoughts: -What works What doesn't work What could be worded more clearly Thanks in advance for your help! https://www.youtube.com/watch?v=edJKu6p4LEw&list=PLngnoZX8cAn8VEVJtgWUKyidEaV-mJKKe https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=C3P44ZYXTBs
Views: 5117 Development That Pays