The document provides a sample agenda for a Sprint Review meeting in an Agile Scrum software development process. The agenda includes: introducing participants, assessing progress against sprint goals, demoing completed features from the user perspective, discussing goals not met and prioritization for the next sprint, and allocating time for Q&A. The purpose is to deliver working software in increments at the end of each sprint and gather feedback through informal demos and discussions.
The document provides a sample agenda for a Sprint Review meeting in an Agile Scrum software development process. The agenda includes: introducing participants, assessing progress against sprint goals, demoing completed features from the user perspective, discussing goals not met and prioritization for the next sprint, and allocating time for Q&A. The purpose is to deliver working software in increments at the end of each sprint and gather feedback through informal demos and discussions.
The document provides a sample agenda for a Sprint Review meeting in an Agile Scrum software development process. The agenda includes: introducing participants, assessing progress against sprint goals, demoing completed features from the user perspective, discussing goals not met and prioritization for the next sprint, and allocating time for Q&A. The purpose is to deliver working software in increments at the end of each sprint and gather feedback through informal demos and discussions.
In Agile Scrum software development, the team is required to deliver a shippable product in increments. At the end of each sprint, the team has coded and tested a set of usable features. At the end of each sprint, a sprint review meeting is held. Oftentimes, this takes the form of a demo.
The following is a sample agenda for your Sprint Review Meetings.
I. Introductions o In many organizations, the Sprint Review Meeting is the only time that certain team members interact with one another. Remember to introduce everyone in the room.
II. Sprint Assessment o Recap the goals of the sprint. o Recap the product backlog items included in the sprint. o Explain the business value of each feature and why it was prioritized.
III. Demo Each Feature o Demo should be informal yet thorough. o When demoing, explain new features from the user’s point of view.
IV. Goals vs. Progress o If certain goals were not met during the sprint, explain why. o Will those goals be prioritized in the next sprint? Explain why or why not.
V. Question & Answers o Budget at least 15 minutes for question and answers. o Keep an open mind, and remember that not everyone who attends the Sprint Review Meeting has been as closely involved with the product as you have.