The Sprint Review
With the sprint review meeting, developers get responses “straight from the horse’s mouth.” Stakeholders can immediately voice their approval or rejection, made official by the product owner. For rejections, developers hear exactly why stakeholders do not approve of the feature. They get direct concerns, as well as changes that the product owner or stakeholders want for the feature.
With this information, developers are better equipped to make exactly what changes would produce a better feature and product.
Even in the case of feature acceptance, developers get a better indication of how much the stakeholders approved.
If the feature was a great success, developers know that they did something right. If, however, a feature barely got accepted, developers realize that they should make changes moving forward. The ultimate goal is to deliver value to customers, and a better approval yields more value.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: