Mid Sprint Demo
In every project, each story goes to the product owner or stakeholder for completion after the testing cycle. When the story is ready for PO(Product Owner) review, we can record a 2-3 mins functionality demo and present it to the product owner. If the product owner feels that story is completed as per acceptance criteria, he/she can mark the story as completed. If PO or stakeholder finds any scenario missing, we can cover within the sprint itself. The benefit of doing this practice is that we can avoid carrying the story forward to the next sprint and can deliver a 100% sprint.
When we do only one demo at the end of the sprint and if PO or stakeholders finds any scenario missing, we have to carry forward the story to the next sprint to cover that scenario. By following the above practice, we can avoid such scenarios.
In most of the sprints, few stories could be ready for PO review by 5th or 7th day. We can have a 30 mins call on 5th or 7th day to show demo for those stories. We can have a final demo on Demo day(10th day). This would really help to deliver a 100% sprint.
How sprint demos impact QA
Key aspects of the Sprint Demo
Work on the Feedback: A member from the development team should take notes on the feedback provided by the customer. After the demo these notes should be circulated within the team and assigned action item owners (if required) for the feedbacks to add value.