What is the usual approach taken when you start a Sprint and halfway through realize one of your stories is not achievable until another team completes work to allow it to pass UAT?
We've started a story and are halfway done with it but cannot finish it until work is completed in 2-3 Sprints from another team.
We don't want to close it but we don't want to "carry" it over for 2 sprints.
On
The usual approach would be to take the story out of the sprint.
However, it is worth considering:
I would also expect this issue to be raised and discussed at the team's retrospective.
Many of the guides on story writing (such as INVEST) suggest that stories are made independent, i.e. they do not depend on other work to be completed outside of the story. It would be worth considering adopting this approach in the future to reduce the risk of this kind of disruption.
If this is already your approach, but a mistake was made to miss the dependency, then it is still worth discussing this in your retrospective. Can this problem be avoided in the future?
Work with the PO to move this story to the product backlog and request for your team (a member) to represent your team in the dependent team's daily stand-up and possibly include a story in their impacted Sprint(s) in order to highlight/communicate your dependency. It's all about building the information 'radiation'.