MVP development from software developer perspective
0 likes203 views
The document discusses what a minimum viable product (MVP) is and why and how to build one. It defines an MVP as the simplest version of a product that allows customers to be tested with minimum effort. Building an MVP focuses development on the core idea, allows for early testing and feedback, takes less time and resources. The document provides tips for building an MVP such as building less features, fixing budgets/time while flexing scope, releasing something daily, and breaking work into small tasks. Examples of successful MVPs from companies like Facebook, Dropbox, Amazon are also included.
More Related Content
Similar to MVP development from software developer perspective(20)
MVP development from software developer perspective
- 1. MVP DevelopmentFrom SoftwareDeveloper’s Perspective
- 2.
- 3. What is MVP? WhyBuild MVP? How to build MVP?
- 4.
- 5. “Minimum Viable Productis that version of a new product which allows a team to collect maximum amount of validated learning about customers with the least effort.” — Eric Reis, Entrepreneur, Blogger, and Author
- 6. “A lot ofpeople misuse the term Minimum Viable Product. To be clear an MVP is not a beta, not a prototype, but rather an experiment designed to test your value proposition’s assumptions by measuring a behavior and learning from the results. ” –Stephen Forte, Managing Partner of Fresco Capital
- 8.
- 9. Saat platform inidirilis, versi MVP-nya hanyalah untuk menghubungkan pelajar atau mahasiswa melalui aplikasi pengirim pesan. Idenya adalah menghubungkan teman melalui media sosial supaya bisa saling kopdar. Aplikasi ini diluncurkan untuk di ujicoba ke pengguna dan mendapatkan feedback yang sangat banyak. Hasilnya mampu membuat aplikasi ini sangat populer di Internet. Saat ini memiliki lebih dari 1,3 miliar pengguna aktif.
- 11. Saat itu tahun1990, seorang anak muda yang ingin membeli sepasang sepatu. Kemudian ia pun pergi ke mall terdekat, namun, ia tidak dapat menentukan mau membeli sepatu yang mana. Ia pun frustrasi, akhirnya memikirkan sebuah ide untuk menjual sepatu secara online. Disinilah ceritanya dimulai. Sebuah MVP pun lahir. Daripada melakukan riset pasar yang mahal dan menyeluruh, ia langsung membuat web sederhana. Kemudian ia mendekati para pemilik toko sepatu, mengumpulkan foto-foto sepatu dan menampilkannya di website tersebut. Ketika menerima pesanan, ia membeli sepatu di toko terkait dan mengirimkannya kepada pelanggan.
- 12. Meskipun ia kehilanganuang di setiap transaksi, cara tersebut sangat efektif untuk mencoba ide bisnis. Pemuda ini namanya Nick Swinmurn, dan ide bisnisnya kemudian diakusisi Amazon sebesar $1.2 miliar!
- 14. Ketika Apple merilisiTunes, yang memiliki fitur podcast didalamnya, menjadikan sebuah platform podcast, Odeo galau. Mereka akhirnya menyelenggarakan hackathon untuk menentukan langkah selanjutnya dari platform mereka. Lahirlah ide untuk membuat platform berbasis SMS. Ternyata platform ini sangat digandrungi di internal perusahaan dan banyak pegawai mereka rela merogoh kocek pribadi beberapa dollar untuk menggunakan platform SMS ini. Akhirnya platform inipun dirilis ke publik di 2006 dan setahun kemudian menjadi populer dan menjadi salah satu media sosial terpopuler.
- 16. Ide awal hanyalahmenjual buku secara online, yang menjadi pesaing Barnes and Nobles, yang masih sangat tradisional. Fokus utamanya adalah menjual buku dengan harga terjangkau, melalui web yang mudah dinavigasi sebagai MVP.
- 18. Sebelum dirilis, DrewHouston sangat mengerti sudah banyak startup yang mengembangkan cloud-storage. Namun ia bersikukuh membuat MVP dalam format video yang menjelaskan cara penggunaan aplikasinya! Video ini memegang peranan penting dalam menggapai calon pengguna yang tepat dan menerima banyak respon positif. Mereka mampu mengumpulkan 70 ribu alamat email dari pengguna potensial dalam sehari sehingga akhirnya memutuskan membuat produk tersebut.
- 20.
- 21. What is MVP •MVP is not an incomplete product. MVP is a complete product with less features. • To gather data from customers with least effort. • MVP wasn’t necessarily an application prototype; it was a market test.
- 22.
- 23. Make something peoplereally want
- 24. Why Startups Failed? 42%NoMarket NeededRun Out of Cash Not The Right Team 29% 23%
- 26. Focus on BuildingThe Core
- 27. MVP focuses onone idea, and it does not include any other function.
- 28.
- 29. MVP allows theapp to be tested, with minimal risk.
- 30. Less Time toDevelop
- 31. Less development timemeans lower development costs. The faster your app is launched to users, the faster you will receive feedback. This means you can work on the improvement of your app, and release an updated version quickly.
- 32.
- 33.
- 34. Why Build MVP? •Build something people want • Focus to the core of the app • Early testing for feedback • Less time to develop • Less budget to spend
- 35. How to BuildmVP?
- 36.
- 37.
- 38. “Conventional wisdom saysthat to beat your competitors you need to one-up them. If they’re spending x, you need to spend xx. If they have 20 features, you need 30!”
- 39. “The answer isless. Do less than your competitors to beat them. Solve simple problems and leave the hairy, difficult, nasty problems to everyone else.”
- 43.
- 45. “Why I HiredA Girl On Craigslist to Slap Me In The Face — And How It Quadrupled My Productivity” by Maneesh Sethi http://hackthesystem.com/blog/why-i-hired-a-girl-on-craigslist-to-slap-me-in-the-face-and-why-it- quadrupled-my-productivity/
- 46. “We lowered ourcost of change by always building less software. We gave people just enough features to solve their own problems their own way — and then we got out of the way.”
- 47. Fix time, FixBudget, Flex Scope Lesson 3
- 48.
- 49. “There’s always timeto add stuff later — later is eternal, now is fleeting.”
- 50.
- 51. “Take whatever youthink your product should be and cut it in half. Pare features down until you’re left with only the most essential ones. Then do it again.”
- 52. “With Basecamp, westarted with just the messages section. We knew that was the heart of the app so we ignored milestones, to-do lists, and other items for the time being.“
- 53.
- 54. From Idea toImplementation Lesson 6
- 55.
- 56.
- 57.
- 58.
- 59.
- 60. “Smaller tasks andsmaller timelines are more manageable, hide fewer possible requirement misunderstandings, and cost less to change your mind about or re-do”
- 61. “Break large tasksdown into more realistic 6-10 hour chunks. Then proceed one step at a time.”
- 62.
- 63.
- 64. “The most importantthing in software development is motivation. Long, drawn out release cycles are motivation killers.”
- 65. If you’re inthe middle of a months-long release cycle, dedicate a day a week (or every two weeks) for some small victories. Ask yourself “What can we do and release in 4 hours?”
- 66.
- 67. How to buildMVP • Build less • Constraints is blessing in disguise • Break down estimation. Scope down • From idea straight to implementation • Release something everyday
- 68. References • https://basecamp.com/books/getting-real • http://hackthesystem.com/blog/why-i-hired-a-girl-on-craigslist- to-slap-me-in-the-face-and-why-it-quadrupled-my- productivity/ •http://theleanstartup.com • https://basecamp.com/books/rework
- 69.