[swagtricker]

Scrum is training wheels. The time boxes are supposed to make you reflect and improve. Ditch Scrum. Go to Kanban, scope your stories smaller and prioritize bug fixes over all new work until you're not writing bugs. Can't ship code without writing bugs? Improve your skills as a team. Start pair or mob programming. Do TDD to improve your design, testability & maintainability of your code. Start moving towards trunk based development and use feature flags to do REAL CI/CD (hint: using a build server doesn't mean you're doing CI). Code deployment != feature deployment! Strive to "roll forward" your code as much as possible and disable/enable features if you run into problems - learn to not "rollback".

Now of course, since this is HN somebody's going to sneer divisively at everything I just said and tell me it's not possible (despite the fact that I've done this, repeatedly in different organizations in a developer and coaching capacity for almost two decades now). Here's my preemptive caveat/STFU for detractors: the above method only works if you, as developers, have full control & ownership over your application code data, and do your own deployments or are partnered strongly with an OPS team that gives you full monitoring & Read Only access. If your team is working in an environment where you don't actually get ownership over your code and data, this won't work. If management, architects, or egotistical prima donna staff/senior developers "won't let you" pair/mob, do TDD, do trunk based development, or do proper CI/CD, this won't work.

P.S. If you're in an environment where "this won't work" - QUIT! Life's too short to put up with being expected to build software with one hand tied behind your back. These things are often easier to do in medium to small sized companies. These things are often easier to do on greenfield (or at least recent) projects.