During the Project: Stakeholders as Change Agents
Stakeholders are encouraged to keep track of progress, both as part of the Scrum processes and on an ad-hoc basis. The Scrum maintains a Burn-down chart, which maps progress and is available for inspection at any time. Towards the end of each Sprint (iteration), a Sprint Review meeting is held, which is a “show-and-tell” for the benefit of stakeholders, where the team describes, and, if possible, demonstrates what was achieved during the Sprint.
This is an opportunity for the stakeholders to request changes before the start of the next Sprint, although changes can be motivated at any time when necessary. The changes will be noted and then evaluated for criticality and priority for inclusion (or not) in the Product Backlog. No changes are introduced during the Sprint in progress. The changes required by stakeholders generally arise as a result of the uncertainty of what the product will be like at the start of the project.
Project Completion: Accepting the Release
There may be one or several releases during a project. On each release, stakeholders accept the release if they are satisfied with what has been delivered (the Product Owner has been instrumental in determining whether each component meets its acceptance criteria during the Sprint).
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: