What does it mean that a Sprint Goal can be any other coherence? In The Scrum Guide the following is written to describe the Sprint Goal. > The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives. So it seems that something else then the coherent function provided by "Done" selected Product Backlog items, can by a Sprint Goal. I don't get that. What does it mean that a Sprint Goal can be any other coherence?

Usually a Sprint Goal is a short (one- or two-sentence) description of the _objectives of the sprint_ , the _higher purpose (vision) of why it is worthwhile undertaking the sprint_.

Please, note that a team might reach the Sprint Goal even if they can’t finish all stories.

**A Sprint Goal is usually the delivery of a feature (“ _one coherent function_ ”). Anyway, The Scrum Guide underlines that the Sprint Goal can be “ _any other coherence_ ” that allows the Development Team to stay focused and “ _work together rather than on separate initiatives._ ” For example the team and the Product Owner can agree to use the sprint to address a risk ( _Does the architecture provide the desired performance?_ ) instead of creating a product increment.**