Evaluation of: 1)Scrum Team, 2)Scrum Master, 3)Product Owner, 4)Developer

The core metric for evaluating a Scrum Team is the value delivered to the customer. Are they consistently delivering potentially shippable increments at the end of each Sprint?

Why would they be evaluated? What's gone wrong with value delivery which would make such a practice necessary?

Other than value delivery, I don't think that there is a universal evaluation metric or rubric that you can use for teams. I'd also discourage the evaluation of individuals on their own.

Every Sprint, the Scrum Team should be delivering value to the stakeholders. If they are not delivering value or if there are questions about whether the value is sufficient to justify the cost of the team for the Sprint, then additional questions can be asked to understand what is impeding the delivery of value. Some of these questions may focus on the role of the Scrum Master, Product Owner, or Developers on the team and how the people doing these types of activities interact. But the first question should always be about delivering value to stakeholders and if the people funding the effort are satisfied, then there may not be a need to dig deeper.

As Devocht rightly said "the core metric for evaluating a Scrum Team is the value delivered to the customer" which is the goal of every Scrum team to deliver value. In my own opinion, if evaluation is to take place it should be base on the positive reviews and feedback from the customers and stakeholders.

I think I have answered this number of time but please allow me to do it once again

Evidence based management, one of the greatest releases of Scrum org is actual answer

Particularly the "current value" section, where "revenue per employee" can is suggested

Also please avoid dividing Scrum teams responsibilities to PO, SM and developers.

The whole Scrum team is responsible for delivering increment of value, without splitting responsibilities apart.