Feature priority - MVP, Parity or something else?

Testing Thoughts
#1

When building a new feature, what is usually your priority?

• Getting that shiz out as quickly as possible as an MVP to get feedback
• Getting parity across multiple platform (web, mobile, Android, iOS, whatever)
• Something else?

Do you often release on one platform without the other having the new feature?

1 Like
#2

Getting that shiz out as quickly as possible as an MVP to get feedback

1 Like
#3

I am not building features alone usually - but the teams I work with do it.
I am assuming we’re talking about marketable products and not internal by-products.
Priorities could differ from that of devs or product managers or stakeholders.

The level of silo and non-coordination is quite high so generally the teams will:

  • release on one platform/app/service without having the new feature on the other;
  • get stuff out as MVP;
  • all MVP stuff might be improved if new features or requests are popping up in that area;