Different meaning of stakeholders in Scrum Is a dev team a stakeholder

Question

Generally, I have learned that stakeholders (in general) are parties interested in the project - development team, testing team, QA team, management, customer (of course) etc. But now in Scrum, it says that the stakeholders are the ones who validate the product and the product is done for them, based on their needs. That would imply it means just the customer. Is it right or I misunderstood, is a development team really a stakeholder?

http://www.scrumalliance.org/articles/21-contracts-for-implementing-scrum

Stakeholders are parties with an interest in the product being developed and/or the Scrum process. They might include suppliers, customers, the business owner, subject matter experts, or product support.

http://thescrumblog.blogspot.cz/2011/04/stakeholders-and-feedback-in-scrum.html

The Scrum Team:
A lot of people forget that the Scrum team is a major stakeholder for the project

Answer 1

To be honest, I think you're misunderstood because you've jumbled many Scrum roles into your concept of "stakeholder."

Stakeholders are those who have legitimate interests in the project, according to the traditional definition. Stakeholders are not always product owners, and their function in Scrum should not be mistaken with that of a Product Owner.

The product owner assists in defining the scrum team's backlog, assigning priorities to work units and communicating progress to "stake holders." These units of work are "verified" with the Product Owner first, and then with "stakeholders" in a sprint-ending demo / wrap-up of the iterations work.

This Scrum Master certification can help you become a certified expert.