The Importance of Stakeholders in Scrum
A core tenet of Scrum is that the Scrum Team receives rapid and frequent feedback from stakeholders in order to inspect and adapt its work. The entire Scrum Team is responsible for stakeholder collaboration, it is not just the Product Owner's responsibility. Scrum provides many elements that support the Scrum Team’s collaboration with key stakeholders:
- Sprint Review - this Scrum event is a working meeting for the Scrum Team to ask for feedback and guidance from their stakeholders
- Product Goal - this concrete, measurable objective helps the Scrum Team and stakeholders understand if they are making progress toward fulfilling the product vision
- Product Backlog - this Scrum artifact provides a means for the the Scrum Team and stakeholders to drive to a common understanding of what must be done to achieve the Product Goal and deliver the product
- Increment - the Scrum Team works to provide a product Increment for review by the stakeholders at the Sprint Review
These elements are built into the framework to provide formal opportunities for stakeholder interaction during the Sprint. However, these should not be considered the only opportunities to interact with stakeholders. Scrum Teams are encouraged to interact frequently with their stakeholders.