- All
- Engineering
- Software Testing
Powered by AI and the LinkedIn community
1
Prepare the demo
2
Support the presentation
3
Collect and analyze feedback
4
Improve the process
5
Here’s what else to consider
The Sprint Review is one of the key events in Scrum, where the team demonstrates the working product increment to the stakeholders and collects their feedback. As a tester, you have a vital role to play in ensuring that the Sprint Review is successful and valuable. Here are some ways you can contribute to this event.
Key takeaways from this article
-
Clarify with visuals:
Utilize visual tools like decision-making tables and flow diagrams to make complex features understandable for everyone. This ensures that during the Sprint Review, stakeholders can easily grasp the product's functionality and give more informed feedback.
-
Translate technical details:
As a tester, translate the intricate workings of the product into simple concepts for stakeholders. By using accessible language and metaphors during the Sprint Review, you ensure everyone is on the same page regarding product quality and user experience.
This summary is powered by AI and these experts
- Parita Patel ISTQB certified(Agile ext. and…
- Mohammad Faizan Khan Engineering Manager - QA (Quality…
1 Prepare the demo
Before the Sprint Review, you should work with the developers and the product owner to prepare the demo of the product increment. You should help them select the most relevant and valuable features to showcase, and create a realistic and engaging scenario that highlights the user value and the business benefits. You should also test the demo environment and the product increment thoroughly, and fix any bugs or issues that might affect the presentation or the functionality.
Help others by sharing more (125 characters min.)
- Parita Patel ISTQB certified(Agile ext. and Foundation) | Automation Testing | Manual Testing | Javascript |Typescript | PHP | Cypress | Playwright | Selenium | Behat | Jenkins | Teamcity | API | JMeter |K6 | SAAS | eCommerce
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
As a Tester, we try multiple scenarios to check product quality. We're the best to explain the product with all use cases. In a complex project which had 10 user types, multiple logics. It confused everyone on how to develop it.The team used to develop the product based on the client's explanation. However, the client would then refuse it, causing a waste of effort and money. I created decision-making tables and a flow diagram to clarify the functionality with the client, and after a few changes, they approved it.The team used diagrams and tables to develop features, while QA verified scenarios. I demonstrated the features to the client using the same diagram. So, not only in sprint review we can use such methods in all stages best output
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- 🇮🇳 Sachin Sharma
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testers play a crucial role in contributing to a successful Sprint Review event in Scrum by:1.Test Completion2. Bug Reporting 3. Validation of User Stories 4. Collaboration 5. Demonstrating Features6. Feedback Provision 7. Regression Testing 8. Test Metrics 9. Continuous Improvement 10. Collaborative Problem-SolvingBy actively participating in these activities, testers contribute to the transparency, collaboration, and continuous improvement aspects of the Sprint Review, helping the Scrum Team make informed decisions and ensuring the product meets the desired quality standards.
LikeLike
Celebrate
Support
Love
Insightful
Funny
6
- POOJA MADHURKAR Senior Development Engineer in Test SDET
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Collaborate with developers and product owners to prepare a comprehensive demo of the user stories implemented during the sprint.Ensure that the demo environment is set up correctly and that all features and functionalities are accessible for demonstration.
LikeLike
Celebrate
Support
Love
Insightful
Funny
4
- Harsh*t Sharma SDET | IoT, SAS, CEH, Machine Learning, Generative AI, Azure
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testers play a crucial role in preparing the demo for the Sprint Review event in Scrum.They ensure that the features or user stories completed during the sprint are thoroughly tested and meet the acceptance criteria.During the demo, testers showcase the functionality of the features from a user perspective, highlighting any key interactions or workflows and demonstrating how they meet the user requirements.Testers also address any questions or concerns raised by stakeholders regarding the quality or performance of the features demonstrated, providing insights based on their testing efforts.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Shrey Sharma Software Engineer @ Instant Systems Inc | Empowering Tech Evolution 🌐 | Test Automation
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
In preparing for a Sprint Review, testers play a crucial role in ensuring that the demonstration reflects the product's quality and readiness. By collaborating with developers and the product owner, testers can help prioritize features that best demonstrate the product's value. Moreover, by rigorously testing the demo environment, testers can preemptively address any potential issues, ensuring a smooth and impactful presentation that accurately showcases the product's capabilities and benefits, thereby reinforcing stakeholder confidence. - powered by #evyAI
LikeLike
Celebrate
Support
Love
Insightful
Funny
2
Load more contributions
2 Support the presentation
During the Sprint Review, you should support the presentation of the product increment by providing technical assistance, answering questions, and clarifying details. You should also observe the reactions and responses of the stakeholders, and note any feedback, suggestions, or concerns they might have. You should encourage them to interact with the product increment, and ask for their opinions and preferences. You should also be ready to explain how you tested the product increment, and what quality criteria and standards you followed.
Help others by sharing more (125 characters min.)
- Mohammad Faizan Khan Engineering Manager - QA (Quality Assurance) and Technical Operations at SKIDOS || Ex- UBISOFT
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
In Sprint Reviews, testers can definitely play a vital role. Testers delve deep into the product and can use this understanding to simplify technical complexities for all stakeholders thereby helping the presentation of the product increment during Sprint reviews. By simplifying product functionalities, they can demonstrate how each feature attempts to enhance user experience. Testers can also provide valuable insights to the marketing team by lending them their expertise in product features and Event-based architecture in utilizing Marketing Automation Tools to target potential segments.Testers can also showcase the testing approach using accessible language and metaphors, ensuring everyone understands the quality standards.
LikeLike
Celebrate
Support
Love
Insightful
Funny
8
- POOJA MADHURKAR Senior Development Engineer in Test SDET
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Actively participate in the Sprint Review meeting to provide insights into the quality and readiness of the product increment.Demonstrate how the implemented features meet the acceptance criteria and contribute to the overall value delivered to the stakeholders.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Apeksha Dalvi-Chawan 2 x LinkedIn Top Voice | Certified Scrum Master | Test Lead | Mentor | QTP Certified | ISTQB CTFL®
(edited)
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Having conducted comprehensive testing of the increment, testers possess a deep understanding of its end-to-end functionality. When stakeholders inquire about workflow-related aspects, testers can provide insightful responses and assist them in understanding the quality standards followed during testing.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Yousef Naffa Experienced QA Manager | Expert in Software Testing | Leading High-Performing Teams to Optimize Testing Processes and Elevate Product Quality
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
I would provide a clear overview of the testing progress during the sprint. Communicate the status of test executions, including the number of test cases passed, failed, and any outstanding issues.and I will actively participate in demonstrating the features that have been tested and are ready for review. Showcase not only the functionalities but also the overall quality and reliability of the implemented features.
LikeLike
Celebrate
Support
Love
Insightful
Funny
2
- Shrushrita Sharma Quality Assurance | Agile | Digital Transformation | Biomedical Engineer | Career Mentor | Top Software Testing Voice
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testers can help demonstrate the new features or bug fixes including the product increment by presenting the changes, evolution of the application over the Sprint, making it easier for stakeholders to understand the improvements. Testers can also explain strategies and quality assurance processes that might involve technical details such as testing environments, troubleshooting issues, and prioritization of some issues over others identified during testing. Testers should not only involve in the scrum team communications but with stakeholders as well to collect all methods of communications. By actively collective feedbacks from stakeholders, testers can also participate in fostering continuous improvements in the scrum team.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
Load more contributions
3 Collect and analyze feedback
After the Sprint Review, you should collect and analyze the feedback from the stakeholders, and share it with the team and the product owner. You should help them prioritize and evaluate the feedback, and identify any gaps, risks, or opportunities for improvement. You should also suggest how to incorporate the feedback into the next sprint planning, and how to adjust the testing strategy and activities accordingly. You should also document and communicate the feedback, and follow up on any action items or decisions.
Help others by sharing more (125 characters min.)
- POOJA MADHURKAR Senior Development Engineer in Test SDET
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Engage with stakeholders during the Sprint Review to gather feedback on the product increment.Document feedback received from stakeholders regarding usability, performance, functionality, and any defects identified during the demo.Analyze feedback to identify trends, common issues, and areas for improvement in subsequent sprints
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Md Maruf Rahman ISTQB® Certified Tester | QA Automation Engineer | Cypress | WebdriverIO | Selenium |
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testers play a pivotal role in a successful Sprint Review event in Scrum by actively collecting and analyzing feedback. They engage in thorough testing throughout the sprint, identifying potential issues and areas for improvement. During the Sprint Review, testers present their findings, ensuring that stakeholders have a clear understanding of the product's current state. By addressing concerns and incorporating feedback, testers contribute to the continuous refinement of the product, fostering collaboration and alignment with stakeholders' expectations, ultimately enhancing the success of the Sprint Review in delivering a valuable and high-quality increment.
LikeLike
Celebrate
Support
Love
Insightful
Funny
- Khurram Wali Khan Software Testing | Team Building | Project Management
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
- Pay attention to stakeholders' reactions during the demo, especially product owners and end-users.- Gather feedback actively using surveys, observations, and open-ended questions. Categorize and analyze feedback for actionable insights.- Document feedback for further analysis and consideration in future sprints.- Encourage diverse perspectives! Go beyond happy users and seek feedback from those who encountered challenges or had different expectations.
LikeLike
Celebrate
Support
Love
Insightful
Funny
- Manikandan Srinivasan Automation Test Lead|Appium|Selenium|Mobile Automation|BDD|POM|Web Automation|API-Testing|Perfecto|CICD|Azure|Jenkins|AWS|BFSI|Telecomm|US Housing Mortgage |AI Enthusiast|Top Software Testing Voice 2023
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
- As a tester, always keep an ears open for the feedbacks/ suggestions provided from the business and stackholders on the improvements on the testing activities/ demo.- Try to analyze the feedback with team members and try to mitigate in the upcoming sprints.- Try to improvise the best practices suggested by all other members in the Scrum team as part of Action items from the testing team.
LikeLike
Celebrate
Support
Love
Insightful
Funny
Load more contributions
4 Improve the process
Finally, you should use the Sprint Review as an opportunity to improve the process of delivering and demonstrating value to the stakeholders. You should reflect on what went well and what didn't, and what you learned from the event. You should also participate in the Sprint Retrospective, and share your insights and suggestions on how to improve the quality, efficiency, and effectiveness of the testing and development process. You should also seek feedback from the stakeholders, the team, and the product owner on how to improve the Sprint Review itself, and make it more engaging, informative, and collaborative.
Help others by sharing more (125 characters min.)
- POOJA MADHURKAR Senior Development Engineer in Test SDET
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Use feedback collected during Sprint Reviews to identify opportunities for process improvement within the development and testing workflows.Collaborate with the Scrum team to address any quality-related issues or bottlenecks encountered during the sprint.Continuously refine testing practices, tools, and techniques to enhance the overall efficiency and effectiveness of the development process.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Yousef Naffa Experienced QA Manager | Expert in Software Testing | Leading High-Performing Teams to Optimize Testing Processes and Elevate Product Quality
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
I would engage with stakeholders, including product owners, developers, and other team members, to discuss the overall quality of the product. Actively participate in discussions about trade-offs between features, quality, and delivery timelines.
LikeLike
Celebrate
Support
Love
Insightful
Funny
2
- Jeff F. Driving Excellence in Software Quality Assurance: Streamlining Delivery, Reducing Defects, Innovative Problem Solving with Data Analytics
(edited)
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
During a sprint review, the QA team is crucial in ensuring the quality of development tasks and the Sprint planning process. They provide valuable input on what needs to be done to ensure quality and also give accurate estimates to complete these tasks. It is important to add QA tasks to each story and to your team's definition of "done." This helps in maintaining quality throughout the development cycle.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Khurram Wali Khan Software Testing | Team Building | Project Management
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
- Reflect on the testing process during the sprint, identifying areas for improvement.- Collaborate with the development team in retrospective meetings to discuss testing-related challenges and successes.- Propose and implement improvements to testing strategies, automation, or collaboration.- Challenge assumptions about the review format! Experiment with different approaches to foster participation, engagement, and deeper learning.
LikeLike
Celebrate
Support
Love
Insightful
Funny
Load more contributions
5 Here’s what else to consider
This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?
Help others by sharing more (125 characters min.)
-
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testers offer insights into the results of integration and regression testing, crucial for understanding how new changes interact with existing functionalities. In a complex software suite integration, the regression testing feedback was vital in reassuring stakeholders about the stability of core features amidst significant updates.Testers often focus on usability and accessibility aspects, ensuring the product is user-friendly and compliant with standards. For a public service portal project, the testers' feedback on accessibility led to significant UI adjustments, making the portal more accessible to users with disabilities, which was highly appreciated in the Sprint Review.
LikeLike
Celebrate
Support
Love
Insightful
Funny
5
- Yousef Naffa Experienced QA Manager | Expert in Software Testing | Leading High-Performing Teams to Optimize Testing Processes and Elevate Product Quality
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
I would always celebrate Successes and Acknowledge Challenges because acknowledge successful testing efforts and highlight any challenges that were overcome during the sprint. Celebrate the team's achievements and demonstrate a commitment to ongoing improvement.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- João Pequeno Software QA Engineer @ C. Steinweg Group
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
As a Software QA Engineer, I actively participate in discussions about problems encountered and possible solutions, collaborating with the development team to resolve issues effectively and efficiently and reinforcing the importance of software quality throughout the Sprint Review, encouraging the team to constantly seek excellence in the delivery of the developed software.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Shakil Rahman
(edited)
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
One of the product improvements is to consider infrastructure improvement in your system. This falls under infrastructure enhancement in collaboration and involves a three amigos session with the product owner, architect and test team members. Once stories are created and sized , these then get divied up into regular sprint planning and worked on gradually with other high priority business improvement features.
LikeLike
Celebrate
Support
Love
Insightful
Funny
Software Testing
Software Testing
+ Follow
Rate this article
We created this article with the help of AI. What do you think of it?
It’s great It’s not so great
Thanks for your feedback
Your feedback is private. Like or react to bring the conversation to your network.
Tell us more
Tell us why you didn’t like this article.
If you think something in this article goes against our Professional Community Policies, please let us know.
We appreciate you letting us know. Though we’re unable to respond directly, your feedback helps us improve this experience for everyone.
If you think this goes against our Professional Community Policies, please let us know.
More articles on Software Testing
No more previous content
- You're faced with conflicting feedback on software bugs. How do you determine their severity? 2 contributions
- Here's how you can cultivate a growth mindset for enhanced problem-solving in software testing. 5 contributions
- Here's how you can target top companies for entry-level Software Testing positions.
- Developers are pointing fingers at testers for result discrepancies. Are you prepared to handle the tension? 1 contribution
- Here's how you can identify when to delegate tasks in software testing projects. 9 contributions
- Here's how you can keep up with the latest trends and technologies in software testing. 21 contributions
- You're struggling to streamline your test cases. How can you identify and eliminate redundancies effectively? 1 contribution
- You're struggling to keep up with testing deadlines. How can you track and adjust your progress in real-time?
No more next content
Explore Other Skills
- Programming
- Web Development
- Machine Learning
- Software Development
- Computer Science
- Data Engineering
- Data Analytics
- Data Science
- Artificial Intelligence (AI)
- Cloud Computing
More relevant reading
- Scrum How do you test the definition of done in a sprint?
- Scrum How can you avoid common pitfalls in using the Sprint Review for feedback?
- Scrum How do you manage changing sprint scope or customer expectations?
- Agile Methodologies What is the difference between a Sprint Review and a Sprint Retrospective in Scrum?