Summary
Highlights
The video begins by explaining that Scrum is built around a set of ceremonies, roles, and artifacts, with the sprint being the central event. A sprint is a time-boxed iteration, lasting between one and four weeks, during which the team sets its sprint goal, plans work in the sprint backlog, and works to complete the planned tasks.
A sprint can be canceled before its timebox is over, but only by the product owner, potentially based on recommendations from stakeholders, the development team, or the Scrum Master. Cancellation occurs if the sprint goal becomes obsolete due to changes in company direction, market, or technology conditions. However, due to the short duration of sprints, cancellations are rare.
Sprints comprise several other events: sprint planning, daily scrums, sprint reviews, and sprint retrospectives. These events are integral to the Scrum process.
Sprint planning is the kick-off event for each sprint, aimed at defining what can be delivered and how the work will be done to achieve the sprint goal. It starts with the product backlog and considers previous work to assess capacity. The planning is divided into two parts: 'what' (product owner defines the goal and items, development team selects items based on capacity) and 'how' (development team plans the work, breaks it down, and performs high-level design). Both the product owner and development team are essential for effective planning. The Scrum Master facilitates the meeting, which should not exceed two hours per week of sprint duration.
The daily scrum is a 15-minute time-boxed event held daily at the same time and place. Its purpose is for the development team to synchronize activities, inspect progress toward the sprint goal, and plan for the next 24 hours. Only the development team is mandatory; the product owner observes and the Scrum Master facilitates. Team members answer three questions: what did I do yesterday, what will I do today, and what impediments do I face? This meeting improves communication and quick decision-making.
The sprint review occurs at the end of the sprint to gather feedback on completed work. The Scrum team invites stakeholders to assess the increment against the sprint goal and showcase their work. Feedback from stakeholders helps the product owner update the product backlog. This meeting is time-boxed to one hour per week of sprint duration (e.g., a two-week sprint has a two-hour review).
The sprint retrospective is the final event of the sprint, time-boxed to a maximum of three hours for a four-week sprint (45 minutes per sprint week). It's an opportunity for the Scrum team to inspect and adapt their process, identifying what went well (people, relationships, process, tools), what didn't go well, and creating a plan for improvements. It typically involves five steps: setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective.
Backlog refinement is an ongoing activity rather than an official Scrum ceremony. It involves the product owner and development team collaborating to clarify, detail, split, add, estimate, and order product backlog items. It usually consumes no more than 10% of the development team's capacity and ensures the backlog remains relevant, detailed, estimated, and prioritized. A well-maintained backlog saves time during sprint planning meetings.