This is ironically good advice because its bad advice.
These kind of general statements about how an mvp should take x weeks are pointless because each project is different. Which is an obvious statement. So is the suggestion that you should launch as fast as possible.
Launching quickly, failing, is a really good way of understanding time management on a macro scale for an entire software project/startup.
And its not just about pacing or knowing how long a feature should take to develop, but many many things like which feature to develop at which point because it might be much more difficult later on.
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.
These kind of general statements about how an mvp should take x weeks are pointless because each project is different. Which is an obvious statement. So is the suggestion that you should launch as fast as possible.
Launching quickly, failing, is a really good way of understanding time management on a macro scale for an entire software project/startup.
And its not just about pacing or knowing how long a feature should take to develop, but many many things like which feature to develop at which point because it might be much more difficult later on.