Maintaining Stakeholder Involvement in Scrum
One of the benefits of adopting any Agile framework is the acknowledgement that stakeholders are an integral part of product development. This is common sense; if customers are involved throughout the journey towards a finished product, their confidence level will rise as the project progresses, and they will also be able to intervene where the product is diverging from their original vision.
The need to change requirements once development has started is also recognised and expected in agile development; there is also no blame or recrimination attached. This is because it is understood by all involved that product development is complex and incorporates many uncertainties and unknowns when the project starts, which will require resolution along the way as product understanding grows. The part that stakeholders play in a typical Scrum development is clearly defined, from concept through to finished product, and their participation is non-negotiable if a successful product is to be delivered.
Key Stakeholder Interactions in the Product Journey
Stakeholder management in Scrum is not complex; stakeholders are defined as sponsors, customers and/or users. Apart from this, the Scrum framework does not differentiate between types of stakeholders, just as there is no differentiation of members of the scrum development team; however, there are distinct roles and activities filled by stakeholders before and during the scrum.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: