Yeah a friend of mine got a new job last year and they finish off every sprint by creating a new release and pushing it to prod on Friday afternoon. She was shocked when she found out about that.

The company doesn't have a definition of done for the devs and doesn't include QA in the release cycle. So the devs just push broken unfinished shit into releases. Then when QA points out all of the issues, the devs go crying to management about how they can't keep to the schedule for the new sprint if QA makes them work "endlessly" on tasks that were "finished" long ago. Basically blaming QA for the issues the devs themselves caused. Management and sales over promise to customers, so they want the devs to work on the new stuff, as they promised it was already in place when development wasn't even planned let alone started. QA and support need to deal with the fallout, trying to handle customers that got non-working broken shit and are pissed about it. Management just tells support to forward any "troubled" customers to them, as they will "handle" it. But what management does is just over promise again, till the customer is happy, setting up an endless loop of failure and disappointment.