Does your team also tend to get stuck in the MVP Trap?

You ship a barebones version of a feature. Zero polish. That’ll be done later if it’s successful.

When the stats roll in it seems the feature got a lukewarm reception. A few users liked it, but it wasn’t a hit.

Next sprint starts and everyone asks if we should spend more time on it

The PM argues ”Why would we spend time polishing something no one uses?”

The designer argues ”Well of course no one used it, it looks like shit, we gotta spend some time polishing it!”

It becomes a chicken or the egg scenario.

Your product ends up with a bunch of half assed features. not bad enough to remove, not good enough to spend more time on.

  • 7
    Sounds like you should introduce your PM to the very functional basics of project management. Or just fire them and hire someone competent.

  • 0
    Unfortunately, yes... Alongside with the sentence: "I don't know, it's not my job" when asked for who to refer to for any issue
  • 0
    I think its a miss understanding of MVP.

    Mvp is not necessarily barebones, its minimum viable product.

    That means that if some polish is required for users to accept the feature you should add that polish.

    The important word is viable.

    It can be very hard to know what is required and sometimes the first iteration does not reach the mvp threshold in which case you have to do more work.
  • 1
    Hm. What @SortOfTested posted should be a good starting point.

    But there is another thing that concerns me.

    A demonstration in front of customers should come after a test presentation. Which requires persons who can evaluate the presentation in a neutral way.

    Don't present something to customers that you don't want yourself. It's just wrong.
Add Comment