Demo

In Scrum, a "demo" refers to a specific event or ceremony that takes place at the end of each sprint, which is a time-boxed period for completing a set of work in the Scrum framework. The primary purpose of the demo is to showcase the work completed during the sprint to stakeholders, including the product owner, team members, and potentially other interested parties. The demo is sometimes also referred to as the "Sprint Review."

Here are the key aspects of a Scrum demo:

1. Showcasing the Increment: The main focus of the demo is to demonstrate the product increment that the development team has produced during the sprint. This typically includes the features, user stories, or other work items that were part of the sprint backlog.

2. Stakeholder Involvement: The demo is an opportunity for stakeholders, including the product owner and potentially customers or end-users, to see and interact with the working product. This involvement helps ensure that the product meets the desired requirements and expectations.

3. Feedback Gathering: Stakeholders can provide feedback on the increment presented during the demo. This feedback can help guide the product's future development, and the product owner can use it to adjust the product backlog for upcoming sprints.

4. Transparency: The demo promotes transparency within the Scrum team and with stakeholders. It allows everyone to have a clear view of what has been accomplished and what is still in progress.

5. Inspect and Adapt: The demo is a part of the Scrum inspect-and-adapt cycle. The team inspects the product increment, gathers feedback, and adapts their plans and priorities for the next sprint.

6. Time-Boxed Event: The demo is typically time-boxed, meaning it has a predefined duration. The duration can vary based on the sprint length, but it is usually a few hours, allowing the team to showcase the work and engage in meaningful discussions without making the event too lengthy.

7. Collaboration: The demo encourages collaboration and communication within the team and with stakeholders. It's an opportunity for discussions, questions, and clarifications.

8. Done Criteria: The work items demonstrated during the demo should meet the team's "Definition of Done" to ensure that they are complete and of high quality.

In summary, the Scrum demo is a critical ceremony that promotes transparency, collaboration, and feedback in the Scrum framework. It serves as a key step in the Scrum framework's empirical process control, helping teams continuously improve their product and development process.