8.2.4. Sprint Review (Demo)

● Validate features before demo ● Assist Product Owner in showing test coverage ● Share defects discovered during testing

In the Sprint Review, Quality Assurance (QA) team members play a crucial role in ensuring that the developed features are of high quality and ready for demonstration. Firstly, they validate the features, which means checking if the new functionalities work as intended and meet the acceptance criteria established during sprint planning. Next, the QA team assists the Product Owner in demonstrating test coverage, which involves showing what has been tested and ensuring that all critical aspects of the features were covered. Finally, they share any defects found during testing, giving the team insights into potential issues that need addressing before the product can be considered complete.

Imagine preparing for a big school presentation. Before the presenter stands in front of the class (the demo), their team (QA) needs to ensure everything is ready. They practice the presentation (validate features), check if all the topics are included (show test coverage), and point out any mistakes they made in their practice sessions (share defects). This preparation helps present their best work.

QA validates features before demo.

The act of validating features before the demo is essential because it ensures that everything works correctly. It involves checking that the software performs its intended tasks and functions as required. This step is crucial as it helps catch any last-minute issues that could detract from the quality and reliability of the product. This validation gives all stakeholders confidence that the product being demonstrated is up to standard and is ready for feedback from users and other team members.

Think about a chef preparing a dish before serving it to guests. The chef tastes the food (validates the features) to ensure it is seasoned properly and cooked well. By doing this, they prevent guests from having a disappointing experience due to a poorly prepared meal.

Assist Product Owner in showing test coverage.

During the Sprint Review, QA's assistance to the Product Owner in showcasing test coverage is vital. This support involves providing evidence of the testing performed and demonstrating that critical features were evaluated thoroughly. It assures stakeholders that the development process has not only focused on building new features but has also included checking quality through extensive testing. This collaborative effort between QA and the Product Owner ensures that everyone understands the product’s current state and what remains to be done.

Imagine a teacher who has a stack of quizzes to review after a big exam. The teacher (Product Owner) asks a teaching assistant (QA) to help go through the quizzes and highlight which questions were answered correctly. This collaborative review allows them to provide an overview of the class's performance (test coverage) and establishes where students may need more help.

Share defects discovered during testing.

Finally, sharing defects that were discovered during testing is a critical aspect of the Sprint Review. By communicating any identified issues clearly, the QA team provides the entire team with insights that can directly influence future development and testing efforts. This transparency helps prevent similar issues from arising in future sprints and encourages a culture of continuous improvement within the team. The QA team’s role here is to ensure that everyone is aware of potential risks and challenges faced during the sprint.

Consider a group of friends planning a road trip who discover that the car has a flat tire before they depart. One friend (QA) shares this important information (defect), allowing the group to fix the tire before they hit the road. This early warning prevents delays and ensures that the trip goes smoothly.

--