This is just a new name for practices that have been in place for at least twenty years on decent projects. See fail fast, test early, small features, frequent early feedback, anti-pipeline pattern...
The new generation inevitably reinvents practices and sometimes resurfaces them through independent archaeology, and so there’s a lot of cyclical repetition of both successes and failures. There’s also sometimes lucky innovations when old ideas get aired out in a new context and yield different results than in the past.
If you’ve been around for a while, it’s easy to call out these repetitions and it can be satisfying to do so. But at the same time, it often means that the new generation is finally catching up on things that nobody’s been around to teach them. That’s something worth celebrating, not diminishing.
I was puzzled why it seemed we were learning the same lessons in an industry over and over again, and why we kept giving new names to things that we're already existing. Then I received enlightenment when I realized that consultants that were selling agile previously were now selling DevOps. The reason they keep changing the name is because it allows consultants to come in and charge you more money to tell you to do the same things management bungled the last 3 times, because the problem isn't with the business processes it's with the idiots running the company.
Or to quote Scott Adams "If you notice a lot of focus on process improvement at your business that's a sign all the smart people have left and management is trying to figure out a process simple enough for the idiots left."