Sprint Goal for a very diverse backlog?
We work in different features for different projects, in which more teams apart from mine are involved not always necessarily related. Apart from that, the stories worked within each sprint are in a lot of cases related to very specific developments that do not necessarily relate to a big feature change, which makes also difficult to clearly see a general "improvement", since we are mainly speaking about SW developments.
How would you create a Sprint goal here, when the backlog is "exotic" or very diverse and not related to a single project?
Thanks so much!
How would you create a Sprint goal here
Why would you even try to? You've mentioned project twice and product not even once.
Isn't this situation exposing the fact that there is no coherence to the work the team is doing, and that this is the problem which really ought to be solved?
+1 for @Ian.
You seem to miss that fact that the Scrum framework is Product based not project based. The Product Backlog contains
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
You stated that
We work in different features for different projects, in which more teams apart from mine are involved not always necessarily related.
That doesn't sound like Product alignment to me. It sounds like your teams owns certain parts of the code base related to features of a Product. What you describe is not the Scrum framework. It is some kind of home grown process that uses some of the terms from Scrum. So for you to find answers to your question, you will have to look internally. As the Scrum Guide states in the End Note:
Scrum is free and offered in this Guide. The Scrum framework, as outlined herein, is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.