During a demonstration, the product owner asked the team to add new scope to the backlog. Which of the following should the Scrum master do NEXT?

Agile methodologies typically do not use a formal 'change request for the change advisory board' in the same way as traditional waterfall projects for backlog additions.

When new scope is identified by the product owner in an agile environment, the Scrum Master's role is to facilitate the process of capturing and documenting this new requirement. Working with a business analyst (or product owner if BA is not present) to define the new epic or user story ensures it is clearly understood and ready for refinement and prioritization in the product backlog.

The Scrum Master should not reject new scope from the product owner; instead, they should facilitate its proper capture and addition to the backlog for prioritization by the product owner.

Updating the risk register and mitigation plan might be a subsequent step if the new epic introduces significant risks, but the immediate next step is to document the new scope itself.