These are some good metrics.

But why the focus on Scrum? Many of these are Lean or DevOps metrics. A Scrum cadence actually perverts some of these.

For example, the author wrote,

"Undone work remains on the Product Backlog, where it can be re-ordered by the Product Owner so as to maximize the delivery of product value."

But that bizarre situation is the result of the artificial Scrum "stop work" rule at the end of a sprint.

A much better approach is to continuously evaluate how things are going: the PO should be able to pivot at any time: "Let's give up on that story, and do this other one instead".

The Scrum cadence is very problematic for Behavior-Driven Development as well - it really gets in the way. A continuous flow is much better.

You don't need Scrum for any of this - there are better alternatives to the few Scrum-specific metrics such as burn-down - measure throughput. And there are important DevOps delivery-centric and quality-centric metrics that are not listed here.