MVP development from software developer perspective

1. MVP DevelopmentFrom Software Developer’s Perspective

2. Hi, I’m Riza

3. What is MVP?
Why Build MVP?
How to build MVP?

4. What is MVP?

5. “Minimum Viable Product is 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 of people 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. Examples of Successful MVP

9. Saat platform ini dirilis, 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 tahun 1990, 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 kehilangan uang 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 merilis iTunes, 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 hanyalah menjual 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, Drew Houston 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. What is MVP?
Recap

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. Why build MVP?

23. Make something people really want

24. Why Startups Failed?
42%No Market NeededRun Out of Cash Not The Right Team
29% 23%

26. Focus on Building The Core

27. MVP focuses on one idea, and it does not
include any other function.

28. Early Testing Opportunity

29. MVP allows the app to be tested, with minimal
risk.

30. Less Time to Develop

31. Less development time means 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. Budget-friendly

33. Why build MVP?Recap

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 Build mVP?

36. https://basecamp.com/books/getting-real

37. Build less
Lesson 1

38. “Conventional wisdom says that 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 is less. Do less than your competitors to beat
them. Solve simple problems and leave the hairy, difficult,
nasty problems to everyone else.”

43. Constraints force Creativity
Lesson 2

45. “Why I Hired A 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 our cost 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, Fix Budget, Flex Scope
Lesson 3

48. Project Management Triangle

49. “There’s always time to add stuff later — later is
eternal, now is fleeting.”

50. Half, not Half-A$$ed
Lesson 4

51. “Take whatever you think 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, we started 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. Open Doors
Lesson 5

54. From Idea to Implementation
Lesson 6

55. Brainstorm

56. Paper Sketch

57. Create HTML screens

58. Code it

59. Break it Down
Lesson 7

60. “Smaller tasks and smaller timelines are
more manageable, hide fewer possible
requirement misunderstandings, and cost
less to change your mind about or re-do”

61. “Break large tasks down into more realistic
6-10 hour chunks. Then proceed one step
at a time.”

62. Celebrate Small Victories
Lesson 8

63. Release something today

64. “The most important thing in software
development is motivation. Long, drawn out
release cycles are motivation killers.”

65. If you’re in the 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. Recap
How to Build mVP?

67. How to build MVP
• 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. slideshare.net/rizafahmi
twitter.com/rizafahmi22
facebook.com/rizafahmi
riza@hacktiv8.com