Speaker A
Hi. In this video, we will have a deep dive into the Scrum events. As explained in a previous video, Scrum is a set of ceremonies, roles, and artifacts. The main event in Scrum is the sprints. Sprint is at the heart of Scrum. It's a
Explore Scrum events beyond meetings, including sprints, planning, daily scrums, reviews, retrospectives, and backlog refinement.
Key Takeaways
- Scrum events are structured to enable collaboration, inspection, and adaptation rather than just meetings.
- Sprints provide a consistent rhythm and focus for delivering value incrementally.
- Effective sprint planning and backlog refinement are critical to successful sprint execution.
- Daily scrums enhance communication and quick decision-making within the development team.
- Retrospectives drive continuous improvement in team processes and collaboration.
Summary
- Scrum centers around time-boxed sprints lasting 1-4 weeks with consistent duration across iterations.
- Only the product owner can cancel a sprint, typically if the sprint goal becomes obsolete due to changing conditions.
- Sprint planning defines what will be delivered and how, involving the product owner and development team in two parts: the what and the how.
- Daily scrums are 15-minute daily meetings for the development team to synchronize, inspect progress, and plan the next 24 hours.
- Sprint reviews involve stakeholders to gather feedback on the increment and update the product backlog accordingly.
- Sprint retrospectives allow the Scrum team to inspect the last sprint's process and create actionable improvement plans.
- Backlog refinement is an ongoing, informal activity to clarify, estimate, and prioritize product backlog items, consuming about 10% of development capacity.
- The Scrum Master facilitates events but the development team and product owner are essential participants.
- Time-boxing is emphasized for all events to maintain efficiency and focus.
- Well-maintained backlog refinement reduces time needed in sprint planning.
Chapters
- 00:00Introduction to Scrum and Sprints
- 01:00Sprint Cancellation and Duration
- 02:02Sprint Planning Overview
- 02:51Sprint Planning Details and Roles
- 03:46Daily Scrum Purpose and Execution
- 05:27Sprint Review and Stakeholder Feedback
- 07:17Sprint Retrospective Process and Steps
- 08:25Backlog Refinement and Its Importance
Full Transcript — Download SRT & Markdown
Speaker A
time-boxed iteration, and its duration varies from one to four weeks maximum. Within a sprint, the team sets their target with the product owner as a sprint goal and plans their work in the sprint backlog. As soon as the sprint starts, the team
Speaker A
works together to complete the planned work effectively and make it ready for review by the end of that period. The duration of a sprint is defined by the Scrum team. Once the team reaches an agreement for how many days a sprint should last,
Speaker A
all future sprints should be the same. A sprint can be cancelled before the sprint time box is over. Only the product owner has the authority to cancel this sprint, and of course, the product owner can decide to cancel the sprint
Speaker A
based on recommendations from stakeholders, development team, or the Scrum Master. A sprint would be cancelled if the sprint goal becomes obsolete. This might happen if the company changes direction or if market or technology conditions change. In general, a sprint should be cancelled
Speaker A
if it no longer makes sense given the circumstances. But due to the short duration of a sprint, cancellation rarely makes sense. Sprints consist of different other events: the sprint planning, daily scrums, the sprint review, and the sprint retrospective.
Speaker A
Sprint planning is the first event in Scrum that kicks off the sprints. The purpose of this ceremony is to define what can be delivered in the sprint and how the work needed to realize the sprint goal will be done.
Speaker A
A great starting point for the sprint planning is the product backlog, as it provides a list of ready user stories that could potentially be part of the sprint. The team should also look at the previous work done in the increment to
Speaker A
have a view on their capacity. The sprint planning is split into two parts. The first part is related to the what. Based on the product backlog, the product owner describes the goal of the sprint, what backlog items contribute to that
Speaker A
goal, and clarifies any final details. Based on the capacity, the development team decides what can be done in the coming sprint and picks user stories from the product backlog. In the second part, the development team decides how the work will be done,
Speaker A
what they will do during the sprint to deliver the sprint goal, break up the work into smaller pieces, and perform some high-level design. You cannot do the sprint planning without the product owner or the development team. The product owner defines the goal based
Speaker A
on the business value he wants to achieve. The development team needs to understand how they can or cannot deliver on that goal. If an item is missing from this event, it makes planning the sprint almost impossible. The Scrum Master can help in the
Speaker A
facilitation of the sprint planning. The most important outcome for the sprint planning meeting is that the team can describe the goal of the sprint and how they will start working toward that goal. This is made visible in the sprint
Speaker A
backlog. The duration of a sprint planning should be no more than two hours for each week of the sprint. So, for example, the sprint planning meeting for a two-week sprint would be no longer than four hours. Once the Scrum team has defined their
Speaker A
sprint goal and their sprint backlog, the sprint can start. The team will meet every day in the daily scrum. The purpose of the daily scrum is for the development team to synchronize its activities, inspect progress towards the sprint goal,
Speaker A
and create a plan for the next 24 hours. The daily scrum is a 15-minute time-boxed event held every day of the sprint at the same time and same place. In the daily scrum, only the development team is mandatory.
Speaker A
The product owner is welcome to join as an observer, and the Scrum Master as a facilitator to ensure that the development team has the meeting. But the development team is responsible for conducting the daily scrum, and it is mainly for them to answer
Speaker A
these three questions: What did I do yesterday that helped the development team meet the sprint goal? What will I do today to help the development team meet the sprint goal? Do I see any impediments that prevent me or the development team from meeting the
Speaker A
sprint goal? If some of the team members need to have an extended discussion, then they can meet immediately after the daily scrum. The daily scrum helps to improve communication and eliminate other meetings. It's the best opportunity for the team to
Speaker A
share their impediments, to highlight and promote quick decision-making. This is a key inspect and adapt meeting. The sprint review is held at the end of the sprint. It is designed to gather actionable feedback on what the team has completed.
Speaker A
The Scrum team would invite the stakeholders to the sprint review. The increment is assessed against the sprint goal defined by the Scrum team. The team will showcase their work in product to the stakeholders and then ask them for feedback on how to
Speaker A
make the product better. The product owner incorporates the lessons learned during the conversation into the product backlog. This meeting is time-boxed to no more than an hour per week of sprint. So, a two-week sprint would have a two-
Speaker A
hour sprint review, and a one-week sprint a one-hour sprint review. The sprint retrospective is the final event of the sprints. This event is time-boxed to three hours maximum for a four-week sprint, which means 45 minutes per sprint week.
Speaker A
The sprint retrospective is an opportunity for the Scrum team to inspect and adapt the process and identify opportunities for improvement. The purpose of the sprint retrospective is to inspect what went well in the last sprint with regards to
Speaker A
people, relationships, process, and tools, identify what didn't go so well in the sprint, and then create a plan for improvements to the way the Scrum team does its work. Usually, most retrospectives follow these five steps: one, set the stage by defining a common
Speaker A
goal for the retrospective and have everyone in the right mood; two, gather data. As everyone sees the world differently, we need to create a shared pool of information; three, generate insights. Discuss why did things happen the way they did and identify
Speaker A
patterns; four, decide what to do by choosing a few issues to work on and create concrete action plans; five, close the retrospective by clarifying how to follow up on these actions. The last meeting we would like to discuss in this video
Speaker A
is the backlog refinement. The backlog refinement is not an official ceremony in Scrum but rather an ongoing activity that the Scrum team can hold during the sprints in which the product owner and the development team collaborate on the
Speaker A
details of product backlog items. Product backlog refinement is the act of clarifying items, adding details, splitting bigger items into smaller ones, adding and discussing new items, estimating or re-estimating items, and ordering these items in the product backlog. The Scrum team decides how and when
Speaker A
refinement is done. Refinement usually consumes no more than 10% of the capacity of the development team. However, product backlog items can be updated at any time by the product owner or by the team after discussing it with the product owner.
Speaker A
The backlog refinement helps to ensure that the product backlog remains populated with items that are relevant, detailed, estimated, and prioritized. This is the main activity in the Scrum cycle. A lot of time will be saved in sprint planning meetings
Speaker A
if the backlog is well maintained. Thank you for following this video. I hope it gave you a good understanding of the Scrum events. Please leave us a comment if there is any topic you would like us to discuss,
Speaker A
and subscribe to our channel for more content. You.
Topics:ScrumScrum eventsSprintSprint planningDaily scrumSprint reviewSprint retrospectiveBacklog refinementAgileScrum Master
