Part of this is a symptom of support demands from users. There has been an expectation in software development historically, back from when software was always hideously expensive and limited to companies as users, that errors would be fixed by someone on demand ASAP. We're all familiar with the IT guy "file a ticket first" signs on offices, or the idiot executive's demands for a new computer because they filled theirs with malware somehow.

But now a lot of what software did is web-based and frequently free/freemium. But the customer's expectations of having their issue fixed ASAP remains. Despite the internet being far from a standardised system of completely intercompatible components. So updates and fixes need to continually be deployed.

And that's great for most people, until that expectation extends to the creation of new features, from management and end users alike. Then things start getting pumped out half-finished-at-best because you can just fix the MVP later, right?

We're going to get to the backlog sometime... right? We don't need to keep launching new features every quarter... right?