That is a massive oversimplification. In fact, a key job of a product manager is differentiating between critical bugs that must be fixed, bugs that should be fixed but can wait and bugs that don't need fixing in the near term. Otherwise, for any mature piece of software (particular enterprise software), you will be fixing almost an infinite number of bugs that add little value at the expense of critical features that make the needle move.
This is one of the biggest lessons I got when working on a decade old enterprise software. At first, I was shocked that our VP of Product put certain bugs in the "won't fix any time soon" category. But now, I see how much more value we'be been able to drive because we decided to ignore certain category of bugs for new feature or other feature improvements.
Insisting on blindly prioritizing bug fixes over any thing else does nothing more than satisfy our engineering ego. Don't assume it automatically making the product more useful for the user or driving more value to the company or its customers
What this misses is that a buggy code base with a lot of technical debt makes it very hard to get anything new done. Worse, because you've spent years teaching people that being sloppy is the way to go, even when they rewrite something or build something new, it won't be very good and will still have a high maintenance cost.
Whereas if you follow a quality-first approach from the beginning, you never build up those mountains of technical debt. You can have a sustained pace of innovation that's much higher because you aren't working on top of a garbage heap. And you have people with excellent habits and a good working environment, meaning high productivity and low turnover.
One easy place to start is her 7 principles: https://nzdunic.info/2015/05/12/mary-and-tom-poppendieck-on-...
Also good are her 7 wastes of software development, created to parallel the Lean Manufacturing wastes:
* Partially Done Work
* Extra Features
* Relearning
* Handoffs
* Delays
* Task Switching
* Defects
0 hits for "shit early, shit often" development.: https://www.google.com/?#q=shit+early+shit+often+development
Were you mocking "ship early, ship often"?https://en.wikipedia.org/wiki/Release_early,_release_often
That's about when you ship, not what you work on. It's not the opposite of fixing bugs.
But then again, business incentives are usually against software that works well and is useful - what matters is whether software works just enough to look sellable.
One form of limiting work in progress is this: if you want reliable software, insist that no new features go in until all the reported bugs have been fixed. A weaker form of this is to have a master branch, which gets bug fixes only, and a development branch, into which new features go. Merging can happen only when there are no open issues in the master branch.
This is the opposite of "shit early, shit often" development.