3 ms·
I was just pontif- er...talking about this, yesterday. I am not a fan of the "MVP" concept, as it is defined in the software startup industry. I feel that it d
by ChrisMarshallNY 5y ago
I was just pontif- er...talking about this, yesterday.
I am not a fan of the "MVP" concept, as it is defined in the software startup industry. I feel that it delivers time-delay disasters.
Mostly, because of the deliberate, and premeditated, willingness to ablate Quality, in a drive for deliverable.
We get bad stuff, fast. All too often, that bad stuff forms the nucleus of the product, for the rest of its lifetime. Basically, a foundation of sand.
It's hard to argue against the "dollars and cents" rationale for it. People make money, this way; lots of money.
As long as money and profit are the main measure of success (and it can be argued that they are the only ones that matter), we will have this drive to deprecate Quality, in favor of profit.
Quality is expensive. Real expensive. I've talked about this before.
But I've worked for hardware companies, for most of my life, and it's fairly rare, when hardware companies can get away with it; often, because laws and regulations. Also, tooling up a product line is a major commitment. You really don't want to cheap out on that. Distribution channels are also some heavy-duty overhead.
For whatever reason, software shops believe that we are exempt from the restrictions that have governed all engineering; throughout history.
In a way, this is true. Software is not hardware, and requires a drastically different approach. I always had a devil of a time, convincing hardware people of this.
On the other hand, I don't like the idea that we are also exempt from the requirement to deliver a baseline level of Quality.
Personal gripe. I'm an old curmudgeon.
- kqr 5y agoThis is an all too common misunderstanding of what an MVP is. A bad MVP is a bunch of features thrown together badly in the hopes that parts of it will match market demand and that the market is willing to look past the quality problems. What follows after moderate success with this approach is a long journey to try to build back in some of the quality that was avoided at the start. The end is predictable: sprawling, mediocre software. With some luck it makes money. Often it does not. A good MVP delivers a single, deliberately chosen feature to a well-researched segment of the market. This single feature has excellent quality characteristics and blows any competition out of the water. On that success follows continued incremental, high-speed development, always with quality as a primary driver. But it takes discipline. In order to economically deliver quality, you must do the research, and you must be willing to deliver in really small, very well chosen increments. And that is hard. That takes excellent developers. It's easier to just throw something together and hope to get lucky.
- ChrisMarshallNY 5y agoWell, I'm not sure that I "misunderstand" "MVP," because, after the dust has settled, and the smoke has cleared, a significant percentage of what is out there, and carries the label "MVP," is duct-tape-and-baling-wire-last-checkin-five-seconds-before-ship dross. I know what I consider "MVP" to be, ideally, and that pretty much jives with your description. It's just that I don't think most folks actually do it. It's like "Agile," in that respect. As someone that practices high-Quality development, I am regularly laughed at and told that I'm "wasting my time," doing Quality coding. Words come to mean whatever their most common usage implies, so I think that both of these wonderful words now mean something other than what they used to mean. https://www.youtube.com/watch?v=G2y8Sx4B2Sk https://www.youtube.com/watch?v=G2y8Sx4B2Sk
- alexchamberlain 5y agoTo echo the peer comment, I personally don't think an MVP should be poor quality, rather have fewer features. For example, it may present the end user a good experience, with well tested code. On the other hand, it may connect to a database without a cluster setup, or setting up a new enterprise account may require someone to run some SQL. Features are missing, but the features that exist are executed well.