
the path to reaching the full promise and potential of Scrum is rarely smooth. Scrum Teams, Developers, Product Owners, and Scrum Masters, uncover new situations every day, all with the general theme, “How do we make this work in our real world?”.
In this course, we will cover the most typical situations you can expect to encounter when working with Agile teams and organizations, and the students will be able to understand how to deal with them.
In this 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.
In this lecture, we dive into one of the most compelling real-world comparisons of Waterfall vs. Agile methodologies: the FBI Sentinel project.
We explore how the FBI, after wasting $170 million on a failed software project, attempted a second large-scale initiative using the same waterfall playbook. By 2010, this second attempt had cost $421 million, yet only 1.5 of 4 phases were complete. The turning point came when a small team of just 40 developers, utilizing Scrum, managed to finish the software in a little over a year for approximately $30 million.
What You Will Learn:
The Cost of Failure: A breakdown of the Automated Case Support (ACS) system and the failed Virtual Case File project—a fixed-bid, spec-first contract that resulted in scrapped code.
The Waterfall Trap: How the Sentinel project under Lockheed Martin, a $450M, 4-phase, 6-year plan, stalled due to rigid planning.
The Agile Turnaround: How bringing development in-house and establishing a "Scrum Studio" in the Hoover Building basement allowed 40 developers to succeed where 400 had struggled, getting Sentinel into production by 2012.
Practical Application: Key takeaways on how to apply these lessons to your own projects to stop planning for years and start shipping value.
Let’s meet Daniel, he is our Product Owner. If you thought product owners simply had to deliver an app or some other digital product, think again.
First, let’s see what are Daniel's responsibilities.
Now that we know what are the responsibilities of any Product Owner, let’s see one business day in the life of our Product Owner...
Let’s meet our Scrum Master Gordon.
Now, let’s look at what daily life looks like for Gordon, the Scrum Master...
Now let’s look at what the first 2-week sprint looks like in real life. Preparation for the first Sprint. Every Sprint starts with...
In the morning, the whole team gets together for their Daily Scrum Meeting. Everyone gives a brief and concise statement about...
In the morning, the whole team gets together for their Daily Scrum Meeting. After that, a member of the Scrum Team has uncertainty about the expected outcome of one of the user stories and its relation to acceptance criteria, he calls the PO...
On day 6 something unusually happened. Let’s see what happened.
Finally, that's the last day of this first Sprint. Gordon, the Scrum Master, invites the Scrum Team to the Sprint Review Meeting.
Activities of the first day - Sprint 2...
In Scrum, in the case of an established product with an established Product Backlog, there should not be the need for any special or extensive release planning for the next release. Why?
Example...
Tips and Best Practices for Scrum at Work - 1 and 2
Tips and Best Practices for Scrum at Work - 3 and 4
Tips and Best Practices for Scrum at Work - 5 and 6
Tips and Best Practices for Scrum at Work - 7 and 8
In this lecture, 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 course, we reflected on common problems encountered with Scrum and we offer multiple suggestions based on real, practical solutions that have worked in different environments...
Have you ever learned Scrum in a class, then gone back to work and not known what to do next?
Do you want Scrum to actually work for your team, not just look good on paper?
This course will show you Scrum in action, simple, clear, and real.
You'll follow real-life style examples and see how Scrum works in projects with real people and real problems.
By the end of this course, you will:
See how Scrum really works at work — not just in theory.
Feel more confident as a Scrum Master, Product Owner, or Developer.
Know how to handle common problems most Scrum teams face.
Walk through a "Day in the Life" of a Scrum Master & Product Owner.
Follow a 2-week Sprint story with real challenges and wins.
Learn 10+ simple strategies you can use in your next Sprint to reduce stress and get better results.
This course makes Scrum easy to understand and simple to use. No guessing. No confusion. Just clear steps you can follow.
Who is this course for?
Beginners who want to see how Scrum works in real life
New Scrum Masters & Product Owners who want to do their jobs well
Developers who want to understand the full Scrum process
Teams who feel Scrum is "not working" and need real solutions
Inside the course, you'll find:
A real-life style story of Scrum in action
A look into the daily work of Scrum Masters & Product Owners
A full 2-week Sprint journey with ups and downs
Step-by-step breakdown of common problems and how to fix them
Over a dozen simple tips and best practices for Scrum at work
A real-world case study included: The FBI Agile Story
You'll also see Scrum proven at scale with a real government case study:
After throwing away $170 million on a failed software project, the FBI tried again with the same waterfall playbook — and by 2010 had spent $421 million with only 1.5 of 4 phases done. Then a team of just 40 developers working in Scrum finished the software in a little over a year for about $30 million.
This is the story of the FBI Sentinel project — one of the clearest real-world comparisons of Waterfall vs. Agile:
Automated Case Support (ACS) — a 1990s system built on 1970s-era technology
Virtual Case File — a fixed-bid, spec-first contract that ended with all code scrapped
Sentinel under Lockheed Martin — a $450M, 4-phase, 6-year waterfall plan that stalled
The turnaround — development brought in-house, a Scrum Studio in the Hoover Building basement, 40 developers instead of 400, and Sentinel in production by 2012
This case study shows you exactly why Scrum works — and what happens when teams stick with waterfall too long.
What students say
"This is the course I wish I had when I first became a Scrum Master. The 'Day in the Life' lesson alone was worth the price. Dejan doesn't just teach theory; he shows you what to do when things go wrong. Highly recommended." — A.M., Scrum Master
Meet your instructor
Hi, I'm Dejan.
I've worked in IT for more than 15 years, and I hold over 60 international certificates. I've been a Scrum Master, Product Owner, and Agile Coach.
I created this course because I was tired of seeing teams struggle with Scrum theory that didn't match their daily work. I'll show you what really works, how to solve problems fast, and how to make Scrum help your team succeed.
Ready to make Scrum work for you?
Remember: Udemy gives you a 30-day money-back guarantee. There is no risk in trying this course.
Enroll now and start your first real Sprint today.