"Minor Issues"??? A multi-million dollar rocket crashing is NOT a "Minor Issue"! 😀 Neither is using a space vehicle for a planetary drill because of a difference in measuring systems nor is something as "simple" as passing parameters backwards.
This is why that, before QA, we put our code through Unit Testing, a peer review AND a DBA review. Is it going to slow you down??? It will seem so at the beginning but the amount of rework necessary to discover where the problem is, fix it, and retest it will actually save huge amounts of time, not to mention your code giving your company a serious black eye if it makes it to the customer.
If you want to prevent such a waste of time and total embarrassment (possible costing you current and future customers), you only need to "Do it right the first time" with no exceptions. Simple peer reviews and DBA reviews can prevent a whole lot of that and so can "Unit Testing". It takes a little extra time on the front to do it but saves huge amounts of time in the release cycle.
Slowdown a bit and "Do it right the first time all the time". The payback will be absolutely incredible.
I know what you're getting ready to do... you're getting ready to make some excuses based on schedule. Stop making such ridiculous excuses. It doesn't take much extra time to ensure you're doing it right but just a couple of "oops" will cost you shedloads of time and possibly cause you to miss the schedule by a whole lot. "If it's worth doing, it's worth doing right".
And, yeah... that also means you have to "Do it by the book". Most companies have no such book and need to document just exactly what needs to be done during the SDLC and then it has to be ENFORCED!