
Product Owner should cocreate the Product Vision and should be responsible for communicating it and and connect teams with the main purpose of the product. Also make sure to set how Value means for that product. At the same time Product Goals should be derived from that Vision.

I believe we should be weary about too many additions to the Scrum Guide. I think the product vision is vital. But do we really want to set in stone how it relates to the Product Goal and who should determine it?

This is a “how-to” for a product vision (artefact). The Scrum Guide is not intended to describe any how-to’s, because these are rather up to the specific emering process. Hence I’d strongly recommend to drop this idea.

It’s an interesting idea but I recommend to drop it. I agree this too specific (“how-to”).

Not every product have a long term vision. Some product have temporary existence. Yeah, leave this one out of the Scrum Guide.

It makes sense. However, I would ask whether having a product vision as a mandatory SG component (in addition to/instead of the product goal) would make a difference for the scrum team or bring any added value to the work done.

Very rarely have I seen a PO also own the product Vision? A PO is an operational role, not a strategic or financial one. A product can also strecth over multiple systems that each have their own strategic plan mapped against company goals and strategies.
I agree that product goals should be aligned towards a product vision based on an overall strategic plan for the whole company.