In a Scrum team, what do you do with stories that require work to be done by another team?
The work required of the other team could be well defined and in parallel: "We'll do this, and we want you to do that." Or it could be that we're asking the other team to engage with us in the development process - discovering requirements and impacts, planning, validating, and then delivering.
The team being autonomous requires that the team is trusted to deliver its stories within the sprint. So the team sizes its stories to the size it can deliver within one sprint, and then takes responsibility for delivering it. But when the team depends on another team, the other team may not start work at the same time, and even if it works efficiently, its work may end up crossing the boundary of a single sprint. If they are not efficient, their work, even though appropriately sized for a sprint, may not be delivered within the time of one sprint, for example if they have competing priorities and other work in progress.
It seems that by depending on another team, our team has lost its autonomy, and can't be trusted to, or held responsible for, delivering the stories. Can it still be called a Scrum team then? But surely Scrum teams do depend on other parties all the time? How should the team manage these dependencies?