MVP is defined as : "that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."It doesn't say a thing about the product being valuable to the customers or market segment.
MVP is minimum viable product *NOT*  minimally marketable feature set / first release!  MVPs are the experiments we learned from on the way to our first release of the software.
To us the core of the difference between "Minimally Viable Product" and "Minimally Marketable Product" is in the purpose.  An MVP's purpose is to learn, an MMP's purpose is to serve.  Understand the problem vs address the problem.

 
3 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Mix of interactive session using some case studies and presentation. 

Shree and I have presented on the same topic in Scrum Regional  Gathering, Pune (http://scrumgatheringindia.in/program/) 

 

Learning Outcome

1. Understand the difference between "Minimally Viable Product" and "Minimally Marketable Product".

2. Expose the fact that when you are developing a MVP, you don't necessarily have to have stories , Or any real amount of code,  Or database
schemas, Or anything.

3. Understand that the MVP differs from the conventional market testing strategy of investing time and money early to implement a product before testing it in the market.

4. First mover advantage is still applicable

5. Finally look at what could be a set of possible MVPs.

Target Audience

Business Analysts, Product Owners, Project managers, Architects, User Experience Designers

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Interesting topic that always gets the idea owner's attention. As an audience, I would also look forward to know "when" to choose which approach. whether "MVP" or "MMP". I understand that you would cover it under the definition of "MVP", so would like to know if its a possibility for MVP to become MMP down the lane, and would there be any additional overhead of re-factor, test etc.?

    • Unnat Gupta
      By Unnat Gupta  ~  3 years ago
      reply Reply

      Hi Deepak, in our opinion MVP and MMP goes hand-in hand. Once you have your hypothesis (idea) validated you take multiple small incremental steps to deliver the while idea to your target segment. This small increments are MMPs. Minimum Viable Products helps you in figuring out if consuming market see the problem you've spotted, if yes would they be willing to consume your products/service. In order to deliver your products/services to your users to need the Minimum Releasable Product approach. In fact we indent to cover this during the comparison between MVP and MRP. Of course there are added overheads with MVP approach regarding total cost, and other overheads which we would also touch upon.

      • AgileSattva Consulting LLP
        By AgileSattva Consulting LLP  ~  1 year ago
        reply Reply

        It would be good if you could update the proposal as well! Thanks for the response!

  • Doc Norton
    By Doc Norton  ~  3 years ago
    reply Reply

    It would be great to see your slide deck for this presentation, even an earlier version of it. Any examples of you speaking would also be helpful.

    - Doc

     

    • Unnat Gupta
      By Unnat Gupta  ~  3 years ago
      reply Reply

      Here you go

      http://www.slideshare.net/shreedamani/mvp-deck

  • Ram Srinivasan
    By Ram Srinivasan  ~  3 years ago
    reply Reply

    Hi Unnat

    MVP is deployable (but it may be mocks or just landing pages), and is sometimes (or most of the times) targeted towards early adopters.  MVP may be an entire product or a subset of the product. The goal is to not build the wrong product.

    http://en.wikipedia.org/wiki/Minimum_viable_product

    Innovators and early adopters are also Customer Segments - http://en.wikipedia.org/wiki/Early_adopter

    Also, I have not heard Steve Blank/Eric Reis talk about "Minimally Marketable Product". Can you point me to appropriate references?

    Considering that you have presented this session earlier, it would be great to see a copy of your slides.

     

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hello Unnat,
    Could you help me understand what about your presentation would be 'advanced'? It does sound interesting, I just am missing what background attendees would need to have to get value from the session.

    Best,
    Tosi

    • Unnat Gupta
      By Unnat Gupta  ~  3 years ago
      reply Reply

      Hi Joel:
      It's not mandatory but We would like the attendees to have prior knowledge of Minimum Releasable Features for us to effectively drive the concept of MVP and it's role in the delivery cycle.

      Actually this is the feedback we had got from some of the attendees of this talk at the Scrum regional gathering India. Feel free to reach out for additional queries.

      Thanks & Regards,
      Unnat/Shree


  • Liked Tarang Baxi
    keyboard_arrow_down

    A Practical Guide to Setting up Distributed Agile Projects

    45 mins
    Talk
    Beginner

    A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

    • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
    • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
    • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
  • Liked Giovanni Asproni
    keyboard_arrow_down

    Methodology Patterns: a Different Approach to Create a Methodology for Your Project

    Giovanni Asproni
    Giovanni Asproni
    Consultant
    Asprotunity Limited
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Advanced

    In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

    In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

    The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

  • Aman King
    Aman King
    Agile Technologist
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Are you an Agile Practitioner? Or are you responsible for Agile transformation?

    Organizations that have begun their Agile journey welcome the guidance of an experienced Agile Coach. But external guidance cannot continue indefinitely as the only way to scale Agile.

    If you are in an Agile team, are you prepared to take on the coaching role for other teams once your Agile Coach moves on?

    If you are a manager, are you looking at grooming in-house coaches to scale and self-sustain transformation?

    The transitioning of practitioners into coaches can be key to your Agile journey. Individuals get to build on their potential, while the organization becomes more self-reliant.

    This session explores my personal journey from practitioner to coach. It should help you too in taking that first jump into the role of a coach. I will share real-world examples of dealing with on-the-fly situations, and of preparing upfront where possible. I will recommend resources, and mention handy techniques that should be in a coach's toolkit. The session essentially provides a kick-start for first-time coaches.

  • Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    Thoughtworks
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • 45 mins
    Talk
    Intermediate

    A traditional software development project entails specifics around elements in or out of scope, tied up to deliverables, all ensconced within specified estimates and timelines, subjected to legal clauses for everything from acceptance to indemnities. For Agile contracts, the boundaries of legal intervention must stand; merely due to the marriage of parties when a project is executed; the definitions of boundaries must be established be it scope, budget or timeline and all standard deliverables from a traditional project stands; yet, the execution is as diverse as chalk and cheese.

    What are the key criteria to be aware of when we define Agile contracts; as in typical agile projects, should the client be involved in mutually drafting the contract? How much legal intervention can we allow? What happens to deliverables and expenses when delays occur and scope boundaries are reduced? Can blame be apportioned to an extent that each party will have to indemnify themselves?

    An Agile contract needs to reflect the nature of the engagement; no template contract with standard clauses can be coaxed upon a true agile project. In line with the Agile principles and values and targeted to the agile manifesto; Agile contracts should be just that – Agile!

  • Liked Tarang Baxi
    keyboard_arrow_down

    1000 Words - Illustrating Project Challenges with Visuals

    Tarang Baxi
    Tarang Baxi
    Principal Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).

  • Liked Anushya Prasad
    keyboard_arrow_down

    Lean Kitchen

    20 mins
    Case Study
    Beginner

    Ever watched a pair of cooks on Master Chef working in teams, an open kitchen in a restaurant or Gordon Ramsay yelling across the kitchen at his team of chefs?

    Ring a bell? Doesn't it remind you of your project team? Or if you're a foodie like me, of the similarities between a software project, your team and a Gourmet kitchen? Is there something we can learn from them?

    This talk is an attempt to draw such a comparison highlighting how our teams and a bunch of chefs in a restaurant kitchen function to whip up something so delectable that our customers want to come back for seconds. 

  • Liked Tarang Baxi
    keyboard_arrow_down

    The Agile ContraDictionary

    Tarang Baxi
    Tarang Baxi
    Principal Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Inspired by 'The Devil's Dictionary' by Ambrose Bierce, this is a satirical look at common misinterpretations and misunderstandings of Agile principles, processes, behaviours and roles. Precise, clear (re)definitions for Exactimation, Scrumudgeon, Abuser stories, Kanband-aid, Fragile methods, ScrumLord, Rundown chart, and many more!