Velocity measures how many user stories were completed by the team, on average, in previous sprints. It assists in estimating how much work the team is able to accomplish in future sprints.
Reference: https://www.sealights.io/software-development-metrics/11-scrum-metrics-and-their-value-to- scrum-teams/

Reference:
https://www.atlassian.com/agile/teams/remote-teams

The Product Owner is the person responsible for achieving maximum business value for the project. He or she is also responsible for articulating customer requirements and maintaining business justification for the project.
The Product Owner represents the Voice of the Customer.

Because stakeholders have an interest in the project, it is important to communicate with them regarding risks.
Information provided to stakeholders related to risk should include potential impact and the plans for responding to each risk. This communication is on-going and should occur in parallel with the four sequential steps discussed thus far-risk identification, assessment, prioritization and mitigation. The Scrum Team may also discuss specific risks related to their Tasks with the Scrum Master during Daily Standup Meetings. The Product Owner is responsible for the prioritization of risks and for communicating the prioritized list to the Scrum Team. An important tool which can be used for communicating information related to risks is the Risk Burndown Chart.