Is it valid to change the Sprint Goal during a Sprint?
We have set the sprint goals for the current sprint.
We are afraid that one of these goals can not be achieved due to dependency of delivery of another company. They send instructions for testing in our system but the tests are delivering negative outcomes. The bug was moved from sprint to sprint.
As we probably won't be able to achieve the goal almost at the end of the current sprint, is it valide to remove that goal from the current sprint which is almost ending?.
Should we move it to the next sprint?
The Scrum Guide makes it clear that the Sprint Goal is the single objective for the Sprint, and that during the Sprint no changes are made that would endanger the Sprint Goal.
Hence the multiple "Sprint Goals" you allude to are just a list of stuff, and no commitment at all.
As we probably won't be able to achieve the goal almost at the end of the current sprint, is it valide to remove that goal from the current sprint which is almost ending?.
This would be like moving the goal post to where you hit the ball. Why not admit that we could not achieve this goal (due to whatever reason) and discuss during the retrospective.
Should we move it to the next sprint?
What does the team think about it in the retrospective. From your explanation, it seems to be a third party dependency and without them working on it this task will never get accomplished. It might be possible that it might not get done in the next sprint as well (I guess).
Unless there are some problems with stakeholders, just cancel the sprint, discuss the problem with a team at retrospective, and focus that this would not happen again. Remember that Sprint goal is not carved on the stone for each upcoming sprint. Team makes it up themselves. Practice to set up better and more realistic sprint goal for upcoming sprints
In Scrum, altering the Sprint Goal during the Sprint is typically discouraged, as it can disrupt the team's focus and alignment. The Sprint Goal serves as a guiding direction, ensuring the team stays aligned with broader objectives. However, in exceptional circumstances, such as major changes, adjusting the Sprint Goal may be necessary.
The Scrum Master should assist in addressing this issue, as it falls within their responsibilities. In my opinion and practically, it is appropriate to adjust or remove the goal if a dependency issue prevents its resolution, rendering the goal obsolete. In such cases, it is the Product Owner’s decision to cancel the Sprint. This should be communicated transparently to stakeholders, ideally after exploring alternative ways to deliver value within the Sprint.
What kind of work management approach is being used where you work Anne?