
We organize the course in three iterations to maximize your chances of passing the PSM I on the first attempt, revisiting Scrum's three accountabilities, three artifacts, and five events.
Scrum is a mechanism to optimize value delivery in complex environments, not just a process. It guides continuous adaptation, balancing what to deliver with how to work within a framework.
Scrum is a framework, not a fixed process, guiding teams to define methods for complex problems. Complement it with practices like product backlog and product goal to fit your domain.
Compare waterfall and agile, including Scrum as an agile framework, to show how rapid releases, feedback, and learning guide iterations toward the correct product vision.
Trace the origins of the agile manifesto from the 2001 Snowbird meeting and its role in shaping Scrum for software development.
Explore the four agile values: individuals and interactions over processes and tools, working software over documentation, customer collaboration over contracts, and responding to change.
Explore the 12 agile principles, classified into project, product, people, and process, to apply agile practices in project management with clearer, sustainable guidance.
Agile Principle #1: Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
Agile Principle #2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Agile Principle #3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Agile Principle #8: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Agile Principle #7: Working software is the primary measure of progress.
Agile Principle #10: Simplicity--the art of maximizing the amount of work not done--is essential.
Agile Principle #9: Continuous attention to technical excellence and good design enhances agility.
Agile Principle #6: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Agile Principle #4: Business people and developers must work together daily throughout the project.
Agile Principle #11: The best architectures, requirements, and designs emerge from self-organizing teams.
Agile Principle #5: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Agile Principle #12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Explore how Scrum implements agility as a flexible framework built on the Agile Manifesto, addressing complex problems and delivering high-value results across software, hardware, schools, government, marketing, and operations management.
Explore the cone of uncertainty and how variability in estimates evolves over time. Link VUCA factors to agile practices, comparing software and chemical projects, and highlight short delivery cycles.
Apply five test-taking tips — read questions fully, mark key words, use elimination, and guess when unsure — while reviewing Scrum's five events, three accountabilities, and three artifacts from the Agile Manifesto.
Explore key concepts from the PSM I fundamentals: the cone of uncertainty, sustainable pace, and Scrum as a framework for iterative, incremental product delivery.
Explore how scrum's artifacts and events connect through the product backlog, product owner, sprint planning, sprint backlog, daily scrums, and increment to deliver value in an iterative, incremental cycle.
Transform ideas stored in the product backlog into value through sprints, with the product owner accountable for backlog quality and alignment with stakeholders.
Discover how the product owner drives a high-quality backlog, while sprints convert backlog items into working products through planning, daily scrums, reviews, retrospectives, and ongoing backlog refinement.
The sprint backlog, the output of sprint planning, defines the sprint scope by turning the sprint plan into actionable work, guiding execution toward delivering the increment.
Learn how the increment, a vertical delivery across all architecture layers, becomes the usable product each sprint, ensuring early, valuable software and actionable stakeholder feedback.
Explore how Scrum teams achieve continuous improvement and balance through developers, product owner, and a guiding scrum master, with sprint retrospectives and a clear definition of done.
Learn how Scrum rests on empirical process control—transparency, inspection, and adaptation—driven by short, timeboxed sprints to one month, with events and artifacts that enable inspect and adapt learning.
Discover the five Scrum values—commitment, courage, focus, openness, and respect—and how they build trust, transparency, and true agility in Scrum practices.
Master Scrum theory and values by reviewing the pillars of empiricism, transparency, inspection, and adaptation, and identifying the five Scrum values: commitment, courage, focus, openness, and respect.
Maximizing value delivered by the scrum team by managing the product backlog and defining the product goal. Translating business ideas into prioritized backlog items for developers.
A story shows how a weak product owner without authority breaks feedback loops in Scrum, causing rework, and how authority and availability enable timely inspection and adaptation.
Recaps the Product Owner’s sole accountability to maximize value and manage the Product Backlog, ensuring visibility, clarity of Product Backlog items, the Product Goal, and alignment with business needs.
Guides both the organization and the Scrum Team as the Scrum Master. Removes impediments, coaches the team to self-manage, and maximizes value by guiding backlog management and Scrum adoption.
Discover how the scrum master, product owner, and developers contribute across technical, contentual, and managerial dimensions, with examples like backlog maintenance, refinement, and sprint events.
Recap the Scrum Team, detailing the three accountabilities: Product Owner, Scrum Master, and Developers, and highlight Product Backlog ordering and Scrum Master support per the Scrum Guide.
Explore the scrum workflow from product backlog to increment, including sprint planning, sprint backlog, daily scrums, sprint review, and retrospective, with a focus on passing the PSM 1 assessment.
Explore how Scrum works by detailing events and artifacts through a real-world case study of a web app, and learn to apply Scrum to your own projects.
Analyze how konyu acts as a proxy for Yahoo Auctions Japan, featuring a content management system, language and currency settings, search, bidding, wallet funds, watch lists, and post-auction shipping.
Explore Scrum artifacts—the Product Backlog, Sprint Backlog, and Increment—and how their commitments and goals maximize transparency, alignment, and progress measurement through Product Goal, Sprint Goal, and Definition of Done.
Discover how the product goal, backed by the product backlog, aligns the Scrum team with the product vision and strategy, using increments and sprint goals to validate progress.
Explore planning poker, a consensus-based agile estimation technique using story points and card decks to estimate backlog items, discuss work, and reach shared estimates.
Product backlog refinement is an emergent, ongoing activity by the Scrum team to break down backlog items into smaller, well-defined units with description, order, and size for the upcoming sprint.
Discover how to monitor progress toward goals by summing remaining work and applying burn-down, burn-up, and community flow techniques as described in the Scrum Guide.
Explore burn-up charts to visualize work completed and scope changes, showing total work and work done rising from bottom to top with backlog refinements and sprint burn.
Explore the cumulative flow diagram and how it tracks product backlog items across states over time, including done, not done, and in progress, with points burned and added.
Learn how the Product Backlog is ordered by the Product Owner to best achieve goals, following the Scrum Guide; examine readiness, size, value, risk, dependencies, Epics, and User Stories.
Define the definition of done as a formal set of criteria that ensures quality measures, transparency, and visibility for the increment, so a backlog item meeting it can be released.
Define the definition of done as a continuous, evolving set of criteria that can become more stringent, revealing more work in increments and signaling technical debt through static code analyzers.
Understand technical debt as a practical cost of change in software, managed by Scrum through the Definition of Done and sprint retrospectives to maintain quality.
Analyze how the increment becomes usable on meeting the definition of done and who creates the definition of done—organization or Scrum team—while release timing remains context dependent.
Explore scrum events and the sprint backlog, and see how timeboxing with sprint planning, daily scrum, sprint review, and sprint retrospective promotes transparency and inspection.
Sprint planning defines the sprint goal and selects product backlog items for the sprint, while the team assesses capacity, velocity, and the definition of done, inviting specialists as needed.
The sprint backlog offers a real-time, highly visible plan that commits to the sprint goal, lists selected product backlog items, and allows flexible changes after negotiating with the product owner.
Discover when a sprint should be cancelled if the sprint goal becomes obsolete, and how the product owner holds the authority to cancel despite stakeholder input.
This course and practice exams are not endorsed by, in partnership with, or affiliated with Scrum. org.
This course prepares you for taking Scrum .org's Professional Scrum Master level 1 (PSM I) assessment.
Imagine yourself being prepared to lay a job in one of the highest-promising and highest-paying areas, skyrocketing your career, and improving your life quality.
Have you pictured it?
An opportunity that is right there, waiting for you to grab, is becoming a Scrum Master!
Check out some data that shows that becoming a Scrum Master is a great opportunity for you:
Glassdoor includes Scrum Master in its list of highest-paying jobs, with an average of $97,000+, per year.
A study performed by Scrum. org in 2019 showed that the average salary of a Scrum Master is $98,000+, ranging up to $150,000+, per year.
LinkedIn included Scrum Master in its 2019 Most Promising Jobs list.
--
IMPORTANT TIP: instead of purchasing only this course, consider Udemy’s subscription plan. This way, you gain access not only to this training, but also to all of my courses available on the platform, in addition to thousands of other high-quality contents. It’s the smartest way to boost your learning with an even more cost-effective investment.
--
However, what does Scrum Master mean?
Scrum Master is a Scrum accountability. Scrum is an agile framework for developing, delivering, and sustaining complex products.
If you already know about Scrum Master and Scrum, great! You might be some steps closer to the goal of laying a job as a Scrum Master!
If you don't, great too! Just by being here, you are already moving in the right direction!
In both cases, one factor that has been demonstrated to highly influence your chances of getting hired as a Scrum Master, and getting paid higher, is getting certified!
There are many certifications available, but the best cost-benefit for you is, unquestionably, getting the Professional Scrum Master level 1, by Scrum. org!
However, it costs 200 dollars per attempt, which is not cheap.
Therefore, a smart move is to make a small investment in this course.
Why?
Let me give you 7 reasons.
1) Because it will boost your chances of getting certified as a Professional Scrum Master!
2) Because it is eye-opening, clearly explaining Scrum with examples, proper learning curve, and visual explanations!
3) Because it contains exclusive practice exams for you to simulate the experience of taking the PSM I assessment and test your knowledge, totaling over 300 questions for you to sharpen your saw!
4) Because it contains PSM I Sniper lectures, in which you will learn special tips and shortcuts to triumph by passing the Professional Scrum Master (PSM I) assessment on your first attempt.
5) Because this course was strategically built to maximize your learning potential by using scientifically demonstrated techniques to optimize your brain's capabilities of constructing the necessary neural paths to learn its content.
6) Because this course offers extra content to help you to study (and learn) faster by using scientifically proven techniques.
7) The instructor, Mirko Perkusich, has both industry and academic experience. He has over 10 years of experience working with big players in the software industry, such as Nokia, Asus, and Sony; additionally, he has also worked with startups. Further, he has a Ph.D. in Computer Science. His research focuses mostly on Agile Software Development (and Scrum) with over 50 published scientific articles in worldwide, state-of-the-art journals and conferences.
If you still have any doubts, check below real testimonials from students that purchased courses from Mirko Perkusich!
What if you, for whatever reason, want a refund?
This course has a 30-day money-back guarantee policy!
No questions asked!
There is no risk for you!
What are you waiting for?
Join now and take a step further into becoming a Professional Scrum Master™ and uplift your career!
Students Testimonials (What are students saying about Mirko's courses?):
"Great training. Passed PSM I immediately after the end of the course. I recommend", Jacek Laskowski
"Dear Mirko, Thanks to your wonderful course, I cleared my PSM 1 exam in the first attempt with 95%." (private message) Mahesh Iyer, Project/Program Management Professional
"Undoubtedly the Best Course! Thanks a Million, Mirko!!!" - Mirza Mehdi, Business Analyst
"So far excellent, Mirko is able to deliver this unfamiliar matter (to me) in a very understandable way. Probably to put it in practice it will take some cycles making some experience, but if you like its logic it will come almost natural." Gian Luca Anselmi, Project Manager
"I like the course content! I will definitely recommend taking the course if you want to gain the full guide on Agile and specifically on Scrum. The Instructor explains each detail very clearly. Before this, I took another good course, but it gave basic knowledge. This one was the best match for me. It gave me complete and enough knowledge about Scrum." - Anna Kirakosyan, Project Coordinator
"This course is one of the best I’ve taken in Udemy. I like its progressive style along with helpful quizzes and tips, which has helped me to assimilate and consolidate a solid knowledge about agile management with Scrum. Not to mention the insights that Dr Mirko brings to the table with a perfect alignment between theory and practice, which also helped me a lot to connect with the concepts covered in the course. Dr Mirko has great teaching skills. I couldn't recommend it more." - João Nunes, Software Engineer
"The course not only conveys knowledge and skills, but also teaches the right approach that significantly increases the efficiency of using this framework. All in an accessible and friendly, but also professional, form." - Bagu Bagu
"Informative, comprehensive and good consolidated training...absorbed and enjoyed the learning curve. Thanks to Mirko and team!" - Narayan Ragothma Rao, Executive Director
"Dr. Mirko has a good didactic and strong skills both academic and Industry study cases. So, I recommend this course to you get the knowledge, practice and if you so get the Scrum Certification, this course is really complete." - Leonardo Melo de Medeiros, College Professor and Research Scientist
"I like how you get straight to the point but also make things very clear to understand!" - Nina Paleracio
"All concepts clearly explained. Great examples and case studies provided to reinforce the theory." - Crystal Glassford, General Manager
"So far so good. I like the way the content is explained using lots of examples and visuals, helps me understand better and the learning pace is good for me too." - Jonathan Nathan, IT Project Manager
"He's actually doing a great job of making what I was presuming to be a boring, tired class, into something I want to learn. Not lying about the subject matter is the best start. Promises kept are promises earned." - Jeremy D Shorter, Financial Analyst
Legal Information and Disclaimer
Professional Scrum™, Professional Scrum Master™, PSM™, PSM I™, PSM 1™, Scrum Guide™ and Nexus Guide™ are protected brands of Scrum. org, the organization responsible for developing and sustaining both, the Scrum Guide™ and the Nexus Guide™.
This course, including the practice exams, are neither endorsed by nor affiliated with Scrum. org.
Attribution and Use for the Scrum Guide™ and Nexus™Guide:
This course uses content from the Scrum Guide™ and the Nexus™ Guide only for educational purposes.
The Scrum Guide™ and Nexus Guide™ are made available as is.