3 ms·
It's all in how you phrase it. "Mgr, I've got some concerns about our code quality. We seem to be prioritizing velocity over quality, and paying for it - X% of
by pavel_lishin 5mo ago
It's all in how you phrase it.
"Mgr, I've got some concerns about our code quality. We seem to be prioritizing velocity over quality, and paying for it - X% of our sprints are spent fixing bugs introduced by what we shipped the previous sprint, instead of adding new features. Slowing down will actually increase the speed at which we can ship features, and make us look better to the higher ups as well."
- GamingAtWork 5mo agoyes I actually tried doing that in the last retrospective. Immediately got attacked by the scrum master and my manager literally couldn't figure out what to say (super indian guy). literally a few days later the entire jira board is full of defects lol.
- pavel_lishin 5mo agoThen it sounds like option #2 is probably your way out. Remember when interviewing, don't just shit all over your current job - phrase that well, too. "I'm looking for a place with a more mature software development philosophy, with a higher focus on QA than my team currently has."