Product Owner should collaborate with the team and, in my experience, first and foremost clarify scope for a sprint.
One example of scope creep ( and madness, even for PO!) it's an issue with a huge document attached.
Scrum master should help PO to clarify and organize first sprint's scope, then issues following S.M.A.R.T. requirements and keep documents ...
Barnaby Golden's answer points to the trust associated with a product, which is very interesting and goes hand-in-hand with what Tom Graves writes in Product, service and trust:
A product represents the promise of future delivery of (self)-service,
via use of that product.
When we obtain a product, we trust that that product will deliver ...
I like to think of a product as having a distinct set of end users who derive value from its use.
end users -> People that derive final value from the product, not people that will use the thing to make another thing (i.e. it is not a component)
distinct set -> Identifyable group of people get value from it, not 'the company' or some other ambiguous entity
The Product is the thing that you are building, or the service that you offer, or the need that you want to satisfy, or the vision that you have. The Product is first and foremost an idea "to do something". Only then you can you make it happen. And only then you can decide how you will make it happen.
Like putting together a Scrum team, for example. You ...
This is what retrospectives are for.
Inspect how the last Sprint went with regards to people, relationships, process, and tools;
Identify and order the major items that went well and potential improvements; and,
Create a plan for implementing improvements to the way the Scrum Team does its work.
You have a process problem here. ...
According to this source, we can read the following
What is Net Promoter Score® (NPS)?
Net Promoter Score (NPS) is defined as a metric for determining the
state of a customer’s loyalty and satisfaction with a brand or
Classification of customers based on NPS survey response:
The data pulled from this response is an indicator of their ...
It seems as your scrum master both sees the problem and is suggesting a solution on how you can handle it. If the scrum master knows about this concern and what problems it can cause, he/she should bring it up to the product owner immediately. Especially if you as a team member are not comfortable or you need help talking about this with the product owner, ...