The Sprint Demo (often part of the Sprint Review ceremony in Agile/Scrum methodology) is a critical step in completing a sprint, an opportunity to excite stakeholders, and a chance for developers to show off their work.
What is the purpose of a demo in agile?
Effective sprint demos are a core part of every successful agile team’s process. They provide a chance for the team to celebrate their accomplishments and get feedback about their work. They also spur critical conversation that provides the spark for future sprint work.
What is the difference between sprint review and demo?
Sprint Review is about inspecting the current Sprint, the Product Backlog. It is also about adapting Product Backlog and the new release plan. Sprint Demos is the best way to ensure QA of the product because there is an exchange of ideas on how to better the product. … Sprint Reviews are good for a healthy Scrum Team.
Who will give demo in agile?
The sprint demo takes place at the end of the sprint and is attended by the whole Scrum team, including Product Owner and ScrumMaster, as well as relevant stakeholders, management and developers from other teams.
Who is responsible for demo?
Product Managers and Product Owners, who are usually responsible for running the demo. One or more members of the System Team, who are often responsible for setting up the demo in the staging environment. Business Owners, executive sponsors, customers, and customer proxies.
What is the purpose of a demo?
A product demo is a presentation of the value of your product or service to a current or prospective customer. It typically involves a demonstration of core features and capabilities. The primary purpose of the demo is to close a deal.
How do I prepare for a sprint demo?
Here are a few tips:
- Focus on acceptance criteria. You’ve defined what done means for the story (right?), so focus your demo around proving that you’re actually done.
- Start with the demo in mind. Don’t wait to think about the demo until you’re done with the story. …
- Prepare. …
- Practice. …
- Tell a story. …
- Keep it short.
How long should a sprint demo be?
Before giving the demo for real, it’s best to practice it at least three times. This may sound like a lot, but keep in mind that a good demo is less than 15-20 minutes long, so this shouldn’t take too much time. The amount of practice you put in may also vary depending on your audience and organization.
How do you do a demo feature?
How to give a demonstration that helps convince a customer to actually buy the product.
- Customize your demo. Every customer is unique, so every demo should be uniquely matched to that customer. …
- Tell the customer’s story. …
- Rehearse, rehearse, rehearse. …
- Test everything beforehand. …
- After the demo, close the deal.
What is sprint Backlog in Agile?
The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. … During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.
When can a sprint be Cancelled?
A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete.