Getting Started with Scrum - Step 15: Hold the Sprint Review Meeting

The video tutorial explains the Sprint Review meeting in Scrum, highlighting its purpose, structure, and participants. It covers the discussion of completed items, the demonstration of work, and handling incomplete tasks. The importance of the Product Increment as a measure of progress is emphasized. The video also outlines the scheduling of the Sprint Review and its role in the overall Sprint cycle.

What is the primary focus of a Sprint Review meeting?

• To evaluate team performance

• To plan the next Sprint

• To discuss completed items and their current state

• To assign new tasks to developers

What happens if a task is not completed by the end of the Sprint?

• It is automatically marked as done

• It is moved to the Product Backlog or next Sprint Backlog

• It is completed by the Scrum Master

• It is discarded and not considered again

What is a Product Increment?

• A list of tasks for the next Sprint

• A report on team performance

• A new feature implemented in the current Sprint

• A summary of the Sprint Retrospective

Who must be present at the Sprint Review meeting?

• Only the Product Owner

• The entire team, including Product Owner, Scrum Master, and developers

• Only the Scrum Master

• Only the developers

When is the Sprint Review meeting typically held?

• On the last day of the Sprint, usually in the morning

• At the end of each month

• On the first day of the Sprint

• In the middle of the Sprint