"fixed scope of work" Are you sure about that? Setting deadlines is easy, but fixing the scope would need detailed documentation.

Or maybe this helps, if it's about planning ahead in general: pm.stackexchange.com/q/3246/1264

There are some similar question here, but it depends on how you define completion. Do you mean completing on a deadline or within budget or with predefined scope?

You must add a disclaimer at the beginning when linking or writing about your own products.

Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.

In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.

Can you edit the question with that information? I would have given a different answer knowing that.

If it happens regularly, that's a very different situation. So do you ask about this single occurrence or how to change the common practice?

Could you please clarify if the Scrum Master is employed by your client or your company? Do you assume that your boss will tell you that you cannot talk about it or did he already say it?

@kriscorbus He was explicitly told by his boss that he should not discuss it with the client. If Scrum is more important for you than your career, this answer might not be for you.

@kriscorbus I added a link.