How do I mention concerns in retrospective without getting fired?
Just for clarification, I'm not a scrum master. I'm just a grunt.
The last few months have been pretty rough for my team. The issues have been stacking and the releases have been more last minute and stressful. Everyone seems on edge all the time now.
With this, the last few retrospectives have all started with "guys, why are we getting so many defects?" from management and leads.
To combat the defects, they introduced more planning and even more meetings, but frankly I think all of it wastes more time, makes processes more convoluted, and completely misses why we might be having issues.
I could blame a lot of things for the defects, like introducing more testing, including other metrics in defect counts, or the push for AI usage, but overall, I believe that we're trying to move too fast and get too many things in before deadlines.
Because we're crunching constantly, we don't have enough time to test or check what AIs doing, so we get more defects. It always rolls over into the next sprint. All of this is adding technical debt and makes it worse for us going forward.
The problem is, I'm worried about not being able to articulate this, others not feeling the same, and getting fired because all of this goes against what management wants.
Additionally, I don't even know how to fix this. Re-do priorities? Switch to Moscow method? Get rid of the stupid weights and estimates? I have no ideas.
I was wondering if anyone here knows how I can bring this up or if I should just shut up and do my work. Any advice is appreciated. Thanks in advance.