Sprint Review Without Developers
The best way to appreciate what developers do for the sprint review meeting is to imagine the meeting without developers. If no developers were present, the sprint review meeting might go well until technical concerns come up. Without developer expertise, other roles rarely know the intricate details of how the software works. Analysts know how the software should behave, but not how it was created. Quality assurance technicians know whether there are problems, but not how they might work. Only the developers know how the features were created, and have an understanding of how they work.
Beyond technical concerns, someone on the team would have to forward acceptance or rejection to the developers. Even if someone records minutes for the meeting, will it have all of the necessary details? Developers may have the intuition to ask about details that other roles may not have considered. This means that developers would have to talk with stakeholders later to clarify details before they can go about fixing rejected issues or moving forward with accepted features.
Developers are important in the Agile process even into the sprint review meeting. A meeting that is normally attributed to the product owner and scrum master benefit greatly from developer presence. Plus, developers get access to information that would otherwise be passed around and lose meaning before reaching the recipient.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: