NashTech Blog

Table of Contents
demo

Image from Copilot

I’m sure you’ve heard that the Agile Development team is usually responsible for the demonstration; and, we can proactively step up to take charge of this task as a chance to show off the knowledge.

Hence, if you are newbie and feeling nervous for the first time doing the demonstration, what should we have in mind to present? I’ll give you some advice on how to run a fantastic demo session in this blog article.

What is the Sprint review? What is the demonstration?

In the software development circle, a “demo” typically refers to a software demonstration.

Sprint review is an event within the Scrum framework of Agile project management that occurs at the end of a Sprint.

In the context of an Agile sprint, a demo is an activity in the Sprint review where the development team presents the work they have completed during the sprint to stakeholders. This typically includes new features, bug fixes, and other improvements. The purpose of the sprint demo is to:

  • Showcase progress: Demonstrate the functionality of new features or improvements.
  • Gather feedback: Receive immediate feedback from stakeholders on the work done.

The demo in Sprint review is a crucial part of this process to ensure that the development is on track and aligned with stakeholder expectations.

Before the demo

Here are some tips for conducting an effective sprint review demo:

  • Prepare a clear agenda: Outline the features and improvements that will be showcased. This helps keep the demo focused and ensures that all relevant topics are covered.
  • Involve the collaboration team: we may only perform (coding or testing) on a part of the system, not the whole system. So, this activity helps us to get knowledge from other the team members.
  • Have a rehearsal: who’s making a demo for the first time should rehear with team members to make sure they’re delivering correct information within the timeboxed. Usually, an effective demo should not take place over 10 minutes per team. This is also a chance for other members to give feedback on the pronunciation, delivery, and speaking speed,… Even a professional presenter needs to remember these factors in the meeting.
During the demo
  • Engage your stakeholders: Encourage stakeholders to interact with the product during the demo. This can provide valuable insights into the user experience and gather immediate feedback.
  • Show real progress: Demonstrate how the work completed contributes to the overall product goal. This helps stakeholders see the value of the work done during the sprint.
    • Tip for doing a demo for multiple functions in a screen: showcase from top to bottom, left to right
  • Collect feedback: Actively seek out feedback from stakeholders on the demonstrated features. This can help adjust priorities and improve future sprints. This should be done after each feature is presented, no need to wait until the end of the demonstration.
  • Keep it informal: A relaxed atmosphere can encourage more open and honest feedback. It can also make the demo more engaging and less stressful for the team.
  • Use metrics wisely: Present useful metrics that provide insights into the team’s performance and the product’s progress. Avoid overwhelming stakeholders with too much data.
  • Mix up facilitation: Change the way you facilitate the review to keep it fresh and engaging.
After the demo

Ask for feedback from your development team so that you can know which areas you need to improve for the next time presentation. This activity can happen during Sprint Retrospective where the team gathers around and discusses any improvement.

Conclusion

The newbie’s approach to the demo is methodical and focused on quality assurance. It ensures that the product increment not only works technically but also meets the business needs and value expectations set. This collaboration between development team is crucial for the iterative improvement of the product and for maintaining a high standard of quality throughout the development process. Other than that, you can improve communication skills with client as well as feel more responsible for their work.

Ref: How to Create Perfect Software Demos? [With Examples] (demoboost.com)

What Is a Sprint Demo and Is It Part of a Scrum Team’s Meetings? (scrumalliance.org)

Sprint Demo: What it is & How to Conduct One | Atlassian

Picture of Quynh Pham Thi Thuy

Quynh Pham Thi Thuy

Quynh Pham - a Test Engineer with a passion for ensuring the highest quality in software development. With a background in computer science and several years of experience in the IT industry, I specialize in creating comprehensive test plans, executing rigorous test cases, and automating testing processes to deliver reliable and efficient software products. My goal is to collaborate closely with development teams to identify and resolve issues early, ensuring a smooth and seamless user experience for our customers.

Leave a Comment

Your email address will not be published. Required fields are marked *

Suggested Article

Scroll to Top