Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on


  1. 1. Tathagat Varma
  2. 2. Tathagat Varma •  Career: Tathagat started career in 1991 as a Computer Scien6st with Defense (DRDO, India) and has worked with Siemens Telecom, Philips, Huawei, McAfee, NetScout, Yahoo! and [24]7 Innova6on Labs in senior leadership and technical roles. He has developed products across Telecom, Datacom, Healthcare, Networking and Consumer Internet. In Oct 2014, he started “Thought Leadership” which offers high-end consul6ng and coaching for large organiza6onal transforma6ons. •  Experience: 24+ years of soZware product development; 17+ years with Incremental and Itera6ve Development, Agile and Lean •  Companies trained: can’t disclose due to client NDAs, but mostly Fortune100-500 companies •  Prior Roles: SoZware Architect, Project Manager, Engineering Manager, General Manager, VP, Agile Coach •  Educa:on: MS Computer Science, Exec MBA in HR •  Cer:fica:ons: SPC, CSP, CSPO, CSM, M3.0, PMP, PRINCE2 •  Author: Agile Product Development (2015)
  3. 3. Let’s do the checklist… •  Cool idea ✔ •  Prototype ✔ •  Funding...yay! ✔ •  (aBer many quarters and several $$$s later) •  Product 1.0...yay! ✔ •  Launch...we will all be rich very soon! ✔ •  ...wait......wait.........wait............ •  where are my customers...are the servers up? •  ...
  4. 4. But…NPD Failures abound!!!
  5. 5. Growth Stages of a Startup
  6. 6. Story #1: Zappos hSp://
  7. 7. Story #2: iPod, 2003 hSp://
  8. 8. hSp://[on-apple-special-event-2003/
  9. 9. Story #3: Obama, 2008 hSps://blog.op[
  10. 10. Analy[cs of 24 combina[ons…
  11. 11. Sign-up rates…
  12. 12. The winner…and $60m+!
  13. 13. What were they doing… differently ???
  14. 14. Business Model Canvas
  15. 15. Business Model Canvas on Day 1? ? ? ? ? ? ? ? ? ?
  16. 16. So, how to validate, especially the key ac[vi[es? OBVIOUSLY… build’em all?
  17. 17. Minimum Feature Set •  Steve Blank: – The reality is that minimum feature set is •  a tac[c to reduce wasted engineering hours (code leB on the floor) and •  to get the product in the hands of early visionary customers as soon as possible. – You’re selling the vision and delivering the minimum feature set to visionaries not everyone.
  18. 18. Minimum Viable Product (MVP) •  Eric Ries in The Lean Startup: –  An MVP helps entrepreneurs start the process of learning as quickly as possible. –  It is not necessarily the smallest product imaginable, though; it is simply the fastest way to get through the Build-Measure- Learn loop with the minimum amount of effort –  Contrary to tradi[onal product development, which usually involves a long, thoughmul incuba[on period and strives for product perfec[on, the goal of the MVP is to begin the process of learning, not end it. –  Unlike a prototype or concept test, an MVP is designed not just to answer product design or technical ques[ons. Its goal is to test fundamental business hypotheses.
  19. 19. Build-Measure-Learn Loop
  20. 20. hSp://star[
  21. 21. Coffee Shop MVP •  Good MVP: You have a menu with only a few selec[on of coffee, but all of them taste great. Your shop is clean and [dy with white painted walls and decent looking coffee tables with comfortable seats. Your cashier is polite and you take Visa and Mastercard. No American Express though (we're cool with that). •  Bad MVP: You have a menu with a few selec[on of coffee, but most of them taste horrible. Your shop is below par and your seats are uncomfortable. Also, your store only takes cash and your cashiers are flir[ng with each other. •  Horrible MVP: You have 40 items on your menu - Coffee, frappuccino, espresso, cakes, croissants, biscuits, tea, fried rise, chicken nuggets, etc (you get the idea). You gold plate your store front and your store interior is pimped out with the most expensive furniture and coffee mugs. You put Samsung LCD TVs at every table and the chairs are massage chairs. You take Visa, Mastercard, American Express, and Home Depot giB cards. hSp://star[
  22. 22. hSp://
  23. 23. “Diffusion of Innova[on” EvereS Rogers, 1962 hSp://authen[[onal-change.html Who is the customer for your “New Product MVP 1.0”?
  24. 24. “Earlyvangelists” hSp://[on-by-subtrac[on-the-minimum-feature-set/
  25. 25. Selling to Earlyvangelists… •  Minimum feature set (“minimum viable product”) is a Customer Development tac[c to reduce engineering waste and to get product in the hands of Earlyvangelists soonest. •  Earlyvangelists require a 18 – 36 month product vision past the minimum feature set. •  You’re selling the vision and delivering the minimum feature set.
  26. 26. So, just one MVP, right? hSp://
  27. 27. MMP, MVP, MMF and Stories MMP: Minimum Marketable Product MVP: Minimum Viable Product MMF: Minimum Marketable Features User Stories
  28. 28. Release Planning in Scrum hSp://[cles/ar[cle.aspx?p=1928232&seqNum=3
  29. 29. However… •  A tradi[onal one-direc[onal product backlog might not help build a “ver[cal product slice” that (eventually) leads to a good MVP •  It might not help uncover the key risks regarding integrity of the product •  It might not help demonstrate the en[re tech stack un[l it is perhaps too late
  30. 30. User Story Mapping
  31. 31. Backbone and the Skeleton hSp://
  32. 32. Building the soBware incrementally
  33. 33. What is (SoBware) Architecture? •  The soBware architecture of a program or compu[ng system is a depic[on of the system that aids in the understanding of how the system will behave. •  SoBware architecture serves as the blueprint for both the system and the project developing it, defining the work assignments that must be carried out by design and implementa[on teams. •  The architecture is the primary carrier of system quali[es such as performance, modifiability, and security, none of which can be achieved without a unifying architectural vision. •  Architecture is an ar[fact for early analysis to make sure that a design approach will yield an acceptable system. •  By building effec[ve architecture, you can iden[fy design risks and mi[gate them early in the development process. hSps://
  34. 34. Goals of Architecture •  Expose the structure of the system but hide the implementa[on details. •  Realize all of the use cases and scenarios. •  Try to address the requirements of various stakeholders. •  Handle both func[onal and quality requirements. hSps://
  35. 35. Architectural Levels of Scope hSp://
  36. 36. Spectrums of Design hSp://
  37. 37. Tradi[onal Approach hSps://
  38. 38. Waterfall and Architecture hSp://[cles/towards-agile-soBware-architecture
  39. 39. Principles of Agile Architecture (SAFe) •  Design emerges. Architecture is a collabora[on. •  The bigger the system, the longer the runway. •  Build the simplest architecture that can possible work. •  When in doubt, code or model it out. •  They build it, they test it. •  There is no monopoly on innova[on. •  Implement architectural flow.
  40. 40. Inten[onal Architecture & Emergent Design in SAFe hSp://
  41. 41. Architectural Runways in SAFe hSp://
  42. 42. Minimum Viable Architecture (MVA) Speed Architecture Too slow, costly, and risky Too adhoc and tech debt M V A
  43. 43. Minimum Viable Architecture? •  Addresses the “inten[onal architecture” to help validate the MVP •  Solves the “here and now” •  “Just enough” •  Supports fast development of high-quality working soBware •  Modular and open to changes •  Adequate instrumenta[on to help answer A/ B tes[ng •  Always deploy-ready
  44. 44. Examples hSp://
  45. 45. Recap Solving “unknown-unknown” problems requires addressing mul[ple hypotheses at technology, product and business levels You could test by building-out the en[re solu[on but it entails significant risks, apart from long lead-[me and huge upfront costs Or, build a Minimum Viable Product that allows to incrementally validate the key hypotheses around product vision Building an MVP is a mindset that requires Minimum Viable Architecture to validate major interac[on points of the system with its environment MVA addresses “here and now” by incorpora[ng emergent design into high-quality deploy-ready code
  46. 46. References •  An Introduc[on to Minimum Viable Architecture, hSp:// •  Towards an Agile SoBware Architecture, hSp://[cles/towards-agile-soBware-architecture •  The Minimum Viable Product and the Minimal Marketable Product, hSp:// •  Good Enough is Good Enough, hSp:// enough-in-a-startup •  Crea[ng a highly available minimum viable architecture on AWS, hSp://[ng-a-highly-available-minimum-viable-architecture/ •  In Search of Agile Architecture, hSp:// •  Minimum Viable Architecture, hSp:// •  A Proven Methodology to Maximize Return on Risk, hSp://