Scrum gives a team a steady rhythm. Work happens inside the Sprint, a fixed-length container, and four events inside it give the team regular chances to plan, check progress, show results, and improve. Each event is a formal opportunity to inspect and adapt, and each has a purpose and a time-box.
You'll start with an overview of all five events. Then you'll look at Sprint Planning, where the team agrees why the Sprint is valuable, what can be done, and how the work will get done. Next comes the Daily Scrum, a short event for the Developers to inspect progress toward the Sprint Goal, and finally the Sprint Retrospective, where the Scrum Team plans ways to increase quality and effectiveness.
With the events clear, you'll be ready for the next module, Artifacts & Commitments, where you look at the Product Backlog, Sprint Backlog, and Increment that these events inspect.
An overview of the Scrum events as the Scrum Guide describes them: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective.
Sprint Planning as defined in the 2020 Scrum Guide: its three topics, the Sprint Goal, and the time-box.
The purpose of the Daily Scrum as described in the 2020 Scrum Guide, and how the Developers use it to inspect progress toward the Sprint Goal.
The Sprint Retrospective as defined in the 2020 Scrum Guide, where the Scrum Team plans ways to improve how it works.