A well-managed Product Backlog is only the starting point. To plan a Sprint, the Scrum Team needs a sense of how big the work is and how much the Developers can take on. In Scrum, the Developers do the sizing, and Sprint Planning is where they use that understanding to forecast what can be done and agree how to do it.
You'll start with a tutorial on estimation in Scrum, including the different approaches and techniques teams use. Then you'll look at relative estimation, where work is sized against other work. After that you'll see how Sprint Planning opens the Sprint, and finish with what makes an effective Sprint Goal, the single objective that gives the Sprint its focus.
With planning in place, you'll be ready for the next module, Facilitation & Retrospectives, where you look at how a Scrum Master helps the team run its events well and keep improving.
A tutorial on estimating in Scrum: the main categories of estimation, guidelines for thinking about it, several techniques, and a walkthrough of Planning Poker.
How teams estimate work by comparing it with other work, using analogies to explain the reasoning behind relative estimation and tips for using it.
An introduction to Sprint Planning as the event that opens the Sprint, and how it sets the Sprint Goal and lays out the work for the Sprint.
What to consider when writing a Sprint Goal, and why a clear, meaningful goal matters for focus during the Sprint.