
Welcome to the How do Scrum Events Work in practice Course. Upon completion you will be able to:
Understand how Sprint Planning is done
Understand the Agile practice of Daily Scrum.
Explain Sprint Review Meetings and what is part of Sprint Review Meetings.
Explain the concept of user studies and how they can subjectively and objectively provide feedback.
Define retrospectives and exercises used in retrospectives.
Apply retrospectives at the end of a sprint to improve the overall product or future products.
How am I going to run this course?
The instructional methods used to create this course will guide students' transformation of words and pictures effectively through the working memory, so that information and learning are incorporated into existing knowledge in long-term memory.
By the end of the course, you will have gained a set of techniques and exercises to help you conduct effective Scrum events. This course will focus on what happens once development has begun, to keep things Agile and on target.
All this knowledge can be used to identify what needs to improve in product implementation and what needs to be adjusted for the product to achieve its desired quality.
Also, all this information can be used to coordinate the team and the work the team produces. It can also be used to identify work that needs improvement to become more efficient and less wasteful.
There are many other methods and they all perform well with Scrum as well as with other frameworks, methodologies, or in real life. But in this course, you will see how I conduct Scrum events.
Are you ready? Let's dive in!!!
In this dynamic lecture, we're kicking things off with a bang! Join us as we dive deep into the world of Scrum and reveal powerful learning strategies to supercharge your educational experience.
What You'll Learn in This Lecture:
The importance of FOCUS in your learning journey.
How handwritten notes can enhance your understanding?
The Two-Column Method for optimized note-taking.
The art of visualizing your goals for motivation.
Applying Scrum concepts in real-world scenarios.
The science of spaced repetition for long-term retention.
Scrum is executed in what are called sprints, or short iterations of work lasting usually no more than 4 weeks.
A sprint employs four official scrum events also known as Scrum Ceremonies to ensure proper execution:
Sprint planning,
Daily scrum,
Sprint review, and
Sprint retrospective.
And we have The Sprint.
The Sprint is an event in itself that contains all the work and all the other events that happen during the timeboxed period of development. In this picture, we also have project retrospectives which we will cover later on in this course.
Let's deep dive into official Scrum Events.
Some students asked me to recommend Scrum books.
So, I don't want to overwhelm you with too many books.
Here is just one Scrum Book review.
I started with this book, and I learned WHAT AND WHY.
So if it's possible, get this book, read it and then continue with the course. Of course, you can continue without it...
The sprint planning meeting is an important ceremony for teams to conduct to create good work. This is the first official scrum event.
I am going to unpack this particular meeting and offer up some helpful tips to make your next sprint planning meeting more efficient, effective, and less miserable. Are you ready? Let's go...
Before we get into the steps of this meeting, some preliminary work needs to get done. Probably the most important part of a sprint planning meeting is the preparation that must be done before the meeting starts.
Let's deep dive into it...
This lesson will cover the daily scrum, and how it is used to manage your project. If you have read the scrum guide, you have probably heard of the daily scrum. The daily scrum is a meeting that occurs each workday with developers. This is a short meeting that is intended to get the day started on the right track.
Are you ready, let's go...
What if your daily scrum isn't working? Maybe you're constantly exceeding the time box, maybe no one is sharing, maybe it's passive. Let's go over some common problems that arise with daily scrums and how you can fix them.
One very important way to determine if you are delivering the right product is the Sprint Review Meeting. A Sprint Review Meeting is a meeting that is held at the end of a sprint. It is an opportunity for the developers to demonstrate their products. Two distinct scrum events occur at the end of a sprint, the sprint review meeting, and the spring retrospective meeting.
Now it is time for deep dive into Sprint Review Meeting...
Now we are going to cover how to make sure that your product is done right. Let's start by going over review techniques that examine the work products made while creating software.
These review techniques will help you to do things like finding defects earlier rather than later when they will be more expensive to fix.
The least formal peer reviews are SOFTWARE WALKTHROUGHS. Software walkthroughs simply consist of a software developer showing how the code works. Let's get into it...
THE SOFTWARE TECHNICAL REVIEW is different from the walkthrough. A software technical review is more formal, and its purpose is to address technical aspects of the product. Let's get into details...
SOFTWARE INSPECTIONS are also known as a formal technical reviews. A software inspection is more formal than the previous two review types. A software inspection, like a software technical review, contains multiple roles and follows a rigid structure.
Learn more about SOFTWARE INSPECTIONS in this lesson...
Let's talk about a very popular software inspection technique, the requirements technical review.
The requirements technical review is a two-stage process:
· The first stage is the review and
· the second stage is a discussion meeting.
Are you ready, let's get started...
The retrospective is a term used in the software development community, to describe the act of reflecting on work that was done and not done in the product development. There are two essential types of retrospectives. By the Scrum Guide 2020, we only have Sprint retrospectives and I want to add one more which is the Product or project retrospectives.
In this lesson, I'm going to talk more about issues that surround retrospectives, some of which are the reason why some teams don't use retrospectives at all.
I'm also going to explain how to get over these issues so that you can successfully put retrospectives to work in your Scrum team.
Let's start with how to create a safe environment...
Another key to encouraging a safe environment is positive leadership. As a product owner, that leadership usually starts with you. Be a role model within your team by showing your appreciation for others, and keeping a positive attitude.
Having a retrospective meeting is one of the most valuable processes when applying Agile or Scrum. That is why we must define desirable properties of retrospectives.
Learn more about the desirable properties of retrospectives in this lesson...
In this lesson, we're going to examine the sprint retrospective meeting and how to carry out a successful Sprint Retrospective?
Let's refine retrospectives, and blend the best wisdom and techniques you can use to improve your Retrospectives...
First, we'll start with the reading course exercises. I will present to you several techniques you can use...
Now it is time for the main or the past course exercises. I will present you several techniques you can use...
This course is focused on looking to the future and identifying ways to improve things for your next product. I will present to you several techniques you can use...
Welcome to the new section of this course where I will introduce you to some very important terms so you can run better scrum events. Let’s start with 2 words that I want you to be familiar with...
Let's now introduce some more key terms to help you understand software measurement. I will also provide you some real-life examples so you can better understand all this.
And now, we will talk about User Studies, why they are so important and how to conduct User Studies...
In this video, we will discuss what a safe and open workplace is and how you can build one. A safe and open workplace is one where employees feel physically and psychologically secure, are free to express themselves, and can work collaboratively with their colleagues. Building such a workplace requires a commitment from both employers and employees to foster a culture of respect, inclusivity, and trust.
In this video, we delve into the creation and timing of the Product Backlog in Scrum.
The Product Backlog is a crucial element in the Scrum framework, representing a prioritized list of features and tasks that need to be completed to fulfill the project's goals. But who is responsible for creating it, and when does it typically occur in the development cycle?
Join us as we explore these questions and provide insights into the Product Backlog creation process. Whether you're new to Scrum or looking to deepen your understanding, this video has something for you.
All right, I am so proud of you. Congratulations. Your hard work and determination have paid off.
I have provided you with relevant material so you can run your effective Scrum Events. Lectures were organized into a coherent structure, integrating new information with existing knowledge.
We cover a lot of things here related to how to conduct successful scrum events, and now you have the knowledge and tools you need to Plan and Execute your Scrum Events properly.
If you want to remind yourself, take a look at some lessons again, after all, you have lifetime access to this toolset.
I hope you enjoyed it and I hope you did get some value out of it and if you did I would be very pleased and grateful knowing that you improved your Scrum and Agile knowledge.
Thank you and goodbye.
Ever sat in a sprint planning meeting that dragged on for hours without clarity?
Or daily scrums that felt like question sessions?
Or retrospectives where the same problems come up every two weeks without any real solutions?
I was...
And here's the truth. It's not Scrum's fault. Your events just aren't being run the way they should be.
Most companies treat Scrum events as boxes to check rather than powerful tools for getting results. Teams go through the motions, sprint planning, daily scrums, retrospectives. Yet their speed doesn't improve, delivery stays unpredictable, and executives question whether "going Agile" is worth it.
There's a better way. And I'll show you exactly how to make every Scrum event drive real business results.
I'm Dejan Majkic, Chief Information Officer and Certified Scrum Master and Product Owner. I've trained 133,126+ students. I also lead Agile changes that delivered 30% better efficiency and 20% lower costs in complex government work. I don't teach Scrum from a textbook, I teach the proven methods I use every day managing 500+ employees under tight budgets, government rules, and people who resist change.
If these methods work in government IT projects (where politics, old systems, and red tape make "textbook Scrum" impossible), they'll work in your environment.
What makes this course different:
Instead of just explaining what happens in each Scrum event, you'll learn how to run them in ways that improve the four Key Value Areas that companies actually measure:
Current Value – Run sprint reviews that clearly show the business value you delivered to stakeholders who doubt you
Time-to-Market – Run sprint planning that cuts waste and speeds up delivery
Ability-to-Innovate – Lead retrospectives that find real improvements, not just surface problems
Unrealized Value – Find new opportunities through well-run events
This isn't just about running better meetings. It's about connecting Scrum events to the business results executives care about, customer happiness, money earned, beating competitors, and long-term growth.
Here's the change you'll experience:
Sprint Planning Mastery
Turn vague goals into clear promises that teams actually keep. You'll learn the real-world methods I use to get stakeholder support, manage added work, and set sprint goals that balance big dreams with what's really possible. No more promising too much and delivering too little.
Daily Scrums That Take 15 Minutes (Not 45)
Stop the status-report trap that wastes everyone's time. You'll learn the simple structure that keeps standups focused, finds problems right away, and keeps your team aligned, without turning into mini-planning sessions or complaint time.
Sprint Reviews That Stakeholders Actually Enjoy
Stop boring executives with technical words they don't understand. Learn to show completed work in business terms that prove ROI, show value, and justify continued money. Your stakeholders will start looking forward to sprint reviews instead of dreading them.
Sprint Retrospectives That Drive Real Change
Move past the same complaints meeting after meeting with no improvement. You'll get exercises with step-by-step guides that find root causes, expose system problems, and create real action items. Build retrospectives where teams actually want to join in.
Plus advanced quality methods:
Software walkthroughs for design alignment
Technical reviews for code quality and knowledge sharing
Requirements checks for preventing defects before they're built
Real examples from real changes
Every lesson includes practical examples from complex government IT projects where I've used these exact methods. You'll see how to handle difficult stakeholders, work within limits, overcome people who resist change, and deliver results even when everything isn't perfect.
Perfect if you're:
New to Scrum and want to learn from someone who's doing this work daily, not just consulting
A Scrum Master struggling to make events productive and prove value to leadership
A Product Owner who wants better stakeholder involvement and clearer priorities
A team member tired of wasting time in meetings that don't accomplish anything
An executive checking out Agile adoption and need to understand what good looks like
Preparing for certifications (PSM, PSPO) and want real-world context beyond theory
What you get:
2.5 hours of focused, action-ready video content (no fluff, no filler)
25 practical lessons you can use in your very next sprint
Retrospective exercises with guides
Templates and checklists you can download for each event type
Lifetime access with free updates as Scrum evolves
30-day money-back guarantee. Take the course, use the methods in your next sprint, and see the difference. If you don't find immediate value, get a full refund—no questions asked.
Join 5,390+ students who have changed their Scrum events from time-wasting checkbox ceremonies into value-delivery engines that stakeholders trust and teams actually enjoy.
Your Scrum events can either be the best part of your sprint or the most frustrating. The difference is knowing how to run them properly.
Enroll now and start running Scrum events that drive real results.