sprint goal after development team estimates backlogitems for sprint backlog
The most important thing i learned in last couple of years is to have a clear goal before you start doing anything.
Why is it in scrum the other way around?
"after the development team forecasts the productbacklog items it will deliver in the sprint, the scrum team crafts a sprint goal"
Paul, look at what follows that statement in the Scrum guide:
The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
In Scrum, the Sprint Goal is short-term, and based on what is actually possible from the team's perspective. It provides value to the team through identification with organizational value, and promotes team focus.
It is easy to come up with a goal. Scrum works to mitigate "unrealistic" goals.
If the team hasn't made a forecast of work, how can it know what risks are presented, and whether a coherent goal for their mitigation can be framed and will be achievable?
Paul, the Sprint Goal is not a real "goal". It is made "retrospectively" based on which product backlog items being selected into that sprint.