I can see the point of such models in certain areas, like military, aerospace, naval, or, to stay on topic, Horizon, where dev is outsourced, somewhat critical, specs rather set in stone, and non experts need to measure how capable an organization is to deliver, but for anything else it just feels like unnecessary meta-management that brings significant organisational and development overhead.
The single biggest issue with software development, is that it is incredibly dynamic.
Static solutions don't work, and CMMI is a very static solution. Sadly, a lot of quality practices are static.
Dynamic solutions are really difficult to get right, and tend to depend on a lot of hard-to-quantify variables, like the experience and talents of individuals on a team.
For example, I am quite good at designing fairly complex systems, as long as I am doing it alone. I can hold some fairly ambitious designs in my head; which allows me a great deal of flexibility. I can start with a fairly "fuzzy" architectural model (I call it my "napkin sketch"), and begin a project fairly quickly. As the project progresses, I can apply some massive structural changes, and pivot fairly easily.
However, the minute I need to communicate this plan, the whole shooting match comes to a screeching halt.
Team overhead is a really big deal, and I believe it is seldom factored into our plans, in any kind of realistic manner.
AI is gonna pour rocket fuel on this stuff. There's already a great deal of talk about replacing lawyers with AI.
We have some marvelous CI/D tools at hand, but the execs are the ones that push to release before ripe, and they won't let things like auto-test failures get in the way of MVP.
There was a comment here, some time ago, that was made by someone that proclaimed themselves to have started and successfully exited a number of companies. It went something like "If you do not get physically sick, looking at the code in your MVP, you are spending too much time, worried about code quality."
I think that's a pretty good summary of today's startup zeitgeist.
I think that as soon as we say "zeitgeist" we're abandoning all attempts at understanding the full picture. There are huge numbers of tests being written all over the place, particularly with modern software tooling. It's the older stuff (e.g. Oracle Forms) or low code stuff (e.g. Bubble, Dynamics) that are hard to test where the biggest issues crop up, IME, as those technologies will be picked by people who don't value testing.
The one thing I miss are ICEs (In-Circuit Emulators). Those were badass, but processors are so massive, and so fast, that a real ICE would probably cost a couple of million dollars, and be out of date by the time it hit the market.
Tech can't fix bad managers, and money is like Miracle-Gro™ for bad management, if it incentivizes rotten quality.
Obligatory MonkeyUser: https://www.monkeyuser.com/2021/introduction/
The most important bug is that the software doesn't solve the problem that you have. It doesn't matter how reliably it doesn't solve your problem
And we should add:
Unless we can't do so without introducing any additional problems, while solving that problem in a manner that truly solves it; as opposed to making it appear solved.
We really are often best off, with the problem, if the cure is worse than the disease.
When I was younger, we had a saying:
To err is human, but it takes a computer to really fuck things up.
Damn straight. I'm really big on software Quality. It's kind of my driving passion.
It has been my experience, that an attitude of Quality is actively discouraged in today's "rush to a crappy, lashed-together-with-baling-wire-and-bandaids MVP" SV culture.
We glorify and make heroes of those that deliberately publish garbage, but make money doing so.
When we look to an industry to police itself; it never does. But the rules and regulations applied from non-domain-expert politicians are often ineffective, burdensome, and really only apply to a bygone era (See ISO 9001/CMMI).