Am I a cowboy?

About a year ago I was hired on at a new company after being laid off and unemployed for nearly six months. I'm extremely grateful for the position. That said, I've been a software developer for a bit over ten years now and have never encountered a culture like this. I've worked in quite a few environments due to my previous employer being a contract based work force. I jumped around different companies working for them, but there was usually consistency in processes, even if loosely.

Where I work now, there are zero processes that I've observed. I've never heard the term "cowboy coding" before, but after I looked it up, that's undeniably what we are doing. There are nearly no processes whatsoever. There is no waterfall or agile. It'd be a wild stretch to even consider it Kanban, which it's closest to I suppose.

My question is, if we are successful (which so far, we are) at completing this project, does that mean that all of the agile processes I've learned, all of the retrospectives, sprint planing, backlog grooming, testing framework knowledge, QA/QC roles, scrum master roles, and about every structure in development that I've encountered so far in my career, was worthless?

This place has me questioning why all of those things exist in the first place if devs can just come together with a super loose definition of what they want and nearly zero customer engagement and still accomplish the goal in nearly every metric.

Does the industry actually need all of those burn up, burn down, charts, cards, processes, and exercises? Or is it all a superfluous invention padded out by managers and executives to feel important?