What you'll learn:
- Scrum Fundamentals
- The Difference Between Adaptive and Predictive Approach To Development
- Key Characteristics Of The Scrum Team
- The Concepts of Iterative and Incremental Development
- Characteristics Of The Scrum Events
- Characteristics Of The Scrum Artifacts & Commitments
This course and its practice activities are not endorsed by, affiliated with, or in partnership with Scrum dot org or any other organization.
Many teams say they use Scrum, but they still miss the rules that make it work. Sprints run without a clear goal, the Daily Scrum turns into a status meeting, and nobody is sure who owns the Product Backlog. This course teaches you the basics of Scrum in plain language, based on the 2020 Scrum Guide.
Learn The Scrum Framework From The Ground Up
The subject of this course is the Scrum framework itself.
Scrum is a lightweight framework for solving complex problems. Teams use it to build software, hardware, and products of many other kinds. It gives you a small set of accountabilities, events, artifacts, and commitments, and nothing more. That small set is the reason Scrum looks simple and still confuses people at work. Once you see the purpose behind each rule, the framework starts to make sense as one system instead of a list of meetings. Scrum skills also open the door to roles such as Scrum Master and Product Owner.
Please note one thing before you enroll. This course does not prepare you for a Scrum certification exam. The content is accurate and useful, but it is not exam preparation. The goal is to teach you the rules, the events, the accountabilities, the artifacts, and the commitments.
You start with an overview of Agile and Scrum. You will see the difference between a predictive approach and an adaptive approach, and why that difference matters for your work.
Next, you meet the Scrum Team. You will learn the key characteristics of the Scrum Master, the Developers, and the Product Owner, and how the three work together.
Then you move to the Scrum events. You will study the Sprint and its purpose, the topics that Sprint Planning covers, the Daily Scrum as an inspect-and-adapt event for the Developers, the Sprint Review and the value of early feedback, and the Sprint Retrospective as the driver of continuous improvement.
The last part covers the Scrum artifacts. You will look at the Product Backlog and the Product Goal, the Sprint Backlog and the Sprint Goal, and the Increment. You will learn when the Sprint Goal appears, who owns each artifact, what happens to work that is not finished, and who decides to release the Increment.
By the end of this course, you will be able to explain how Scrum works, use the right term for the right thing, and take part in Scrum events with confidence.
My name is Vladimir Raykov. I am a certified Scrum Master and Product Owner, and I have taught Agile and Scrum on Udemy for more than ten years.
Thank you to Renato Barbieri for contributing the Portuguese subtitles for this course.
Attribution and use for the Scrum Guide and the Nexus Guide
This course uses screenshots from the Scrum Guide, the Nexus Guide, and the Evidence-Based Management Guide to draw your attention to important concepts, rules, and practices. The authors of the Scrum Guide are Ken Schwaber and Jeff Sutherland. The Nexus Guide is developed and sustained by Ken Schwaber and Scrum dot org. Evidence-Based Management was developed by Scrum dot org, the Professional Scrum Trainer Community, Ken Schwaber, and Christina Schwaber. No changes have been made to the content of these guides. Licence: Attribution Share-Alike license of Creative Commons.
