We have weekly sprints and during sprint we have 2 deploys. When we run tests for deploy we get some bugs which needs to be fixed immediately. However, it effects our sprint goal and performance.
We reduced the velocity and opened some space for bug fixes but they sometimes take more time than expected resulted in incomplete sprint tasks. I know that we have to solve a lot of other tech/process problems for a healthy solution but do you have any suggestions for the short term?
> I know that we have to solve a lot of other
> tech/process problems for a healthy solution
> but do you have any suggestions for the short term?
How short term do you mean, given that the team has an inspect-and-adapt Sprint cycle of one week, and can apparently deliver twice within it?
What is stopping the team from changing things each and every sprint? That's what sprints are for. It sounds as though sprinting is faked, and that's what needs to be looked at right now.
Thank you Ian and yes you are right. Because of the management, it is not possible to apply it correctly. I am trying to show them what works and what does not work to convince them about changing the working style.