I can talk for cloud solutions here from my experience. I always prefer to have bug scrubbing every week to ensure they are prioritised properly and slotted for a particular patch or feature release. Bugs which can be fixed by small DB changes or minute front end can go even on a daily basis by quick QA activites. Feature releases can't be compromised for bug fixes if they are having business impact. And bugs should tail along with feature or as a patch release. However, if the bucket of critical bugs is huge then it's time to slow down the feature pushes and stabilise the product to avoid complete meltdown in future

In product engineering, bug fixing and planned development are both equally important. If you are blessed with a team, you can have parallel teams and sprints in this respect. However, such luck does not generally exist for everybody. In such cases, we can create a buffer space for critical bugs to serve, and if no bugs have arisen, we can facilitate the next planned task in the sprint. As another option, we can have tasks with priorities; when a bug comes, we can derive its priority and serve the priorities instead.

Priorize tarefas com base em impacto e urgência, alinhando correções críticas com os objetivos do sprint. Comunique-se com o time para ajustar prazos e redistribuir esforços, mantendo transparência e foco no valor entregue.

I will precisely evaluate the importance of each task. Then allocate resources/time effort accordingly. Prioritize bug fixes that may affect the planned new features.