I agree, every project is different. I don't believe that my experiences and advice should be a catch-all for all projects and teams everywhere, there are too many permutations.
Without defining the variable X (for X amount of weeks) that you should take for an MVP, the general advice for MVP is to build as little as possible, launch fast, fail fast, and reiterate.
There are industries where the barriers of building an MVP are much higher. For example, in ML you need to train your algo huge amounts of data. In the automotive industry, you need to meet a lot of minimum requirements to even enter the market.
I agree, every project is different. I don't believe that my experiences and advice should be a catch-all for all projects and teams everywhere, there are too many permutations.
Without defining the variable X (for X amount of weeks) that you should take for an MVP, the general advice for MVP is to build as little as possible, launch fast, fail fast, and reiterate.
There are industries where the barriers of building an MVP are much higher. For example, in ML you need to train your algo huge amounts of data. In the automotive industry, you need to meet a lot of minimum requirements to even enter the market.