Delay in Project Deliverables

Why do you feel it is your responsibility as Scrum Master to communicate with the client?   Isn't the Product Owner responsible for setting expectations with customers/end-users?



Why does the client have a 'policy' around deliverable delay at all?   What data/evidence are they using to support their expectation around minimal/no delay in delivery?

To me, this situation just oozes contract game dynamics, which are far from Scrum/Agile.   Why is it insufficient to simply inform the client about the unforeseen circumstances, and allow the team to discuss and identify possible ways to better manage such unforeseen events in the future?

Suppose there is a delay in Project Deliverable due to unforeseen circumstances and we only come to know about it in the last moment. As a Scrum Master, how can I inform the client about the same, considering that the client has a policy of minimal or no delay in deliverables?

Scrum is about learning to build the right thing at the right time by means of empirical feedback. That's the policy, and that's what people ought to expect.

So, what work has been completed this Sprint, to the satisfaction of the Definition of Done, and which is of immediately usable quality?