
Advance your scrum mastery with a roadmap to success, updated guidance, and downloadable resources for certification. Delve into empiricism, values, roles, scaling, and exam strategies.
Introduce yourself using the q&a to share your name, where you’re from, your current agile role, and goals, building a community of agile enthusiasts and learners.
Experience premium support with rapid answers in the q&a section, practical tips for playback speed and captions, and step-by-step troubleshooting to optimize your course experience.
Compare waterfall's plan-driven, sequential phases with agile's adaptive, incremental, and iterative approach, emphasizing sprints, product backlog, continuous delivery, and customer feedback in scrum contexts.
Learn how sprint planning defines the sprint goal and selects PBIs for the sprint backlog, while daily scrum, sprint review, and retrospective enable inspection, feedback, and adaptation toward product goal.
Explore how a cross-functional, self-managing scrum team delivers usable increments each sprint, defines the definition of done, and uses feature or component teams to achieve the product goal.
The ultimate advanced training for agile scrum masters shows how the product owner maximizes value, manages the backlog, communicates the product goal, and coordinates with stakeholders for transparent increments.
The scrum master is accountable for scrum effectiveness, coaches the team in self-management, removes impediments, and ensures time-boxed events enable high value increments.
The Scrum Master part 2 clarifies the servant leader role, positions the Master as facilitator of stakeholder collaboration, and coaches the organization to remove impediments and enact Scrum.
The developers define the definition of done, refine backlog items into increments, and plan work to maximize value with a single product backlog.
Explore the scrum master, product owner, and developers as a cross-functional, self-managing team delivering a valuable increment each sprint through backlog management, definition of done, and stakeholder collaboration.
Master five official scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, using time boxing within the sprint container to enforce transparency, inspection, and adaptation as mandatory.
Inspect progress toward the sprint goal through the daily scrum, adapt the sprint backlog, and have developers plan the next day in a time-boxed 15-minute, same time and place meeting.
Present the sprint increment to the scrum team and key stakeholders, gather feedback, and adjust the product backlog to align with the sprint goal and product goal.
Set sprint length within one month, balancing rules and practical needs, avoid mid-sprint changes, and keep events time-boxed and consistent for inspection and adaptation.
Learn how sprints drive value in scrum through planning, daily coordination, reviews, and retrospectives, with focus on the backlog, product goal, increment, and definition of done.
The product backlog is the single source of work, an ordered list maximizing value, with the product owner prioritizing items for developers to pull into sprints and backlog refinement.
Define the product goal and align the backlog to move toward it, ensuring a single Scrum protocol at a time with measurable progress and product owner accountability.
The sprint backlog, created in sprint planning, lists the sprint goal, the PBIs selected, and an actionable plan, remaining flexible as incomplete items move back to the product backlog.
The definition of done is a formal description and commitment that an increment meets quality measures, serving as a usable, transparent checklist for all teams on the same product.
Embrace empiricism as the foundation of scrum, using transparency, inspection, and adaptation to drive sprint and product goals, guided by Kaizen and data-driven decision making.
Explore Scrum values—commitment, courage, focus, openness, and respect—and how these values drive behavior, build trust, and emphasize commitment to the sprint goal over the sprint backlog.
Spot common Scrum Master misunderstandings, such as acting as a schoolmaster, secretary, boss, or superhero, and learn to align with self-management and transparent artifacts rather than reports.
Explore the eight stances of the Scrum master and how servant leadership evolves into true leadership that serves, enabling self-management and value delivery.
Review empiricism through transparency, inspection, and adaptation to guide sprint goals and decisions. Emphasize servant leadership, proactive impediment removal, and values-driven teamwork to empower high-performing scrum teams.
Learn how the Scrum Master serves the organization by fostering environments where Scrum teams thrive, collaborating with stakeholders, removing impediments, and guiding value-driven, empiricism-aligned, self-managed agile practice.
guide the product owner to refine the backlog, clarify the product vision, and foster stakeholder collaboration and empiricism to maximize value through releases.
Coach the Scrum team toward self-management and cross functionality, enable done increments each sprint, and guide clear sprint and product goals through productive events to reinforce empiricism.
Set clear sprint and product goals in business language, with the product owner guiding objectives and the Scrum team committing to the sprint backlog as scope evolves.
Compare feature teams and component teams, showing how feature teams deliver value with cross-functional skills and fewer handoffs. Review forming, knowledge transfer, and self-management concepts for Scrum masters.
Recap #3 highlights delivering a releasable increment each sprint by upholding the definition of done, ensuring transparency, and aligning sprint goals with stakeholders.
Apply the five levels of conflict model by Lisa Atkins to keep scrum team disputes constructive at level one through facilitation, coaching, and self-management.
Learn emergent architecture in Scrum by balancing functional and nonfunctional requirements, delivering business facing functionality each sprint with just enough architecture guided by empiricism.
Velocity measures how much work a scrum team completes in a sprint and is unique to each team, not a direct measure of value.
Facilitate open discussions to de-escalate conflicts and protect team health, without HR or managers deciding removals; embrace emergent architecture and value-driven metrics over velocity.
Learn that scrum is a framework; teams can use tools, practices, charts to support collaboration. Prioritize individuals and interactions over processes and tools; let distributed teams choose communication tools.
Timebox each Scrum activity with a fixed maximum time to limit work in progress and keep events focused. Support velocity planning and inform sprint length with consistent time boxes.
emphasize that individuals and interactions trump processes and tools, and scaling scrum relies on collaboration, self-organization, and shared definitions to manage dependencies and prevent context switching.
Review the exam roadmap and resources, including practice questions, and learn what to do and what not to do during the Agile Scrum Master exam, plus top eight tips.
IMPORTANT - Professional Scrum Master and "PSM" are registered trademarks of Advanced Development Methods (Scrum dot org). This course is not licensed, endorsed, or affiliated with Advanced Development Methods (Scrum dot org) in any way. This course and practice exams are not endorsed by, affiliated with, or in partnership with Scrum dot org or any other organizations.
If you've been desperately looking for Advanced Training For Scrum Masters, then you know that such video courses are extremely rare. You do not need to search anymore. I spent the last several months building a program that will help you level up your Scrum Master knowledge. So, enrolling and completing this program might be one of the best career decisions you've made this year.
Allow me to introduce myself.
Hello,
I am Vladimir from Bulgaria, and I will be leading you through the course. I work in an Agile team, and I am a Project Management Professional (PMP certified) with 5 Scrum certifications, including Scrum Master levels 1 and 2.
Currently, I teach over 140,166 students and have received over 20,533 positive reviews
My courses helped hundreds of students pass Scrum exams. And I'd love to help you too.
Who Is This Course For?
I designed this course for two groups of people.
The first group is those students who are certified Scrum Masters and are determined to level up.
The second group is those students who want to acquire an advanced understanding of the Scrum Framework but passing any exams is not a priority for you
How Is This Course Organized?
Section 1 - Introduction And Exam Details
Roadmap To Success
Immediately Downloadable Resources
Action Items (a PDF file) (Links to Whitepapers, Articles, and Blog Posts)
The 8 Tips To Help You Pass Exams (a PDF file)
Recap Slides - (a 47-page PDF file)
Recaps - Audio Files (9 mp3 files)
60 Educational Images From The Course
Section 2 - Refresh Your Scrum And Agile Knowledge
The Difference between Adaptive and Predictive approaches to development
The Difference Between Product and Project Management (Mental Shifts)
Agile Planning vs Waterfall Planning
What is Scrum and a high-level overview
The 5 Scrum Values and what they mean in the real world
The Agile manifesto and the 12 Agile principles
The concepts of Iterative & Incremental Development
The concepts of Cross-Functionality & Self-Management
Characteristics of the three sets of accountabilities
The Scrum Master
The Developers
The Product Owner
The Sprint and its main purpose
Sprint Planning and answering the three questions - why what and how
Daily Scrum (a key inspect & adapt event for the Developers)
Sprint Review and why feedback is critically important
Sprint Retrospective (the driver of continuous improvement)
The concept of Feedback Loops.
The Product Backlog (the single source of work undertaken by the Scrum Team)
The Sprint Backlog (when does it emerge, who is accountable for it, what happens with the PBIs that are not complete)
The Increment (the relationship between the Increment and the Product Backlog, who decides to release it, in what condition should it be)
The Product Goal (the long-term objective for the Scrum Team)
The Sprint Goal (the objective for the Sprint)
The Definition Of Done (who crafts it and why, is it mandatory, can it change)
Section 3 - Scrum Master - Advanced
Discover How Empiricism Works With Examples
The Most Misunderstood Scrum Value Explained
Misunderstandings Of The Agile Scrum Master (Behaviours To Avoid)
A Deep Understanding Of The Agile Scrum Master
How The Scrum Master Serves The Organization
How The Scrum Master Serves The Scrum Team
How The Scrum Master Serves The Product Owner
Fundamental Scrum Principle 1 - Creating a Done Increment Every Sprint
Fundamental Scrum Principle 2 - Clear Goals On Two Levels
Team Composition - The Difference between Feature Teams and Component Teams.
Conflict Resolution - How The Scrum Master Navigates Internal Conflicts
The Agile Concept Of Emergent Architecture
The Velocity Metric And Its Relation To Value
Critically Important Rules When Multiple Scrum Teams Work On The Same Product
The Agile Concept Timeboxing Explained
Skills Within The Scrum Team (I-Shaped, T-Shaped, Pi-Shaped, and Comb-Shaped Professionals)
Information Radiators - Burnup and Burndown Charts
Section 4 - How To Approach The SM Exam
Discover My Top 8 Tips
Free Resources & Recommendations Outside This Course [Plus More Practice Exam Questions]
Section 5 - Practice Exam
Practice Exam
[HIGHLY RECOMMENDED] You can take the exam multiple times as the questions and answers are randomized
Do I Get A Guarantee?
You can enroll now 100% risk-free because you receive 30 days, unconditional money-back guarantee.
If for any reason you are not satisfied (and that might be something as simple as you don't like my accent) - no problem, you are one click away from a refund
No hassle, no hard feelings!
Go ahead and click the Buy Now button right now and let’s awaken the Scrum Master within almost instantly!
DISCLAIMER STATEMENT
The statements made and opinions expressed herein belong exclusively to the creator of this course and are not shared by or represent the viewpoint of Scrum dot org. This training does not constitute an endorsement of any product, service, or point of view. Scrum dot org makes no representations, warranties, or assurances of any kind, express or implied, as to the completeness, accuracy, reliability, suitability, availability, or currency of the content contained in this presentation or any material related to this presentation. In no event shall Scrum dot org, its agents, officers, employees, licensees, or affiliates be liable for any damages whatsoever (including, without limitation, damages for loss of profits, business information, loss of information) arising out of the information or statements contained in the training. Any reliance you place on such content is strictly at your own risk.
TRADEMARK NOTICE STATEMENT
Scrum dot org, Professional Scrum Master, Professional Scrum Product Owner, PSM, PSM I, PSM II, PSM 1, PSPO, PSPO I, PSPO 1 are trademarks of Scrum dot org and may be registered in the United States Patent and Trademark Office and in other countries.
ATTRIBUTION AND USE FOR THE SCRUM GUIDE, NEXUS GUIDE, AND EVIDENCE-BASED MANAGEMENT GUIDE
This course uses screenshots from the Scrum Guide, Nexus Guide, and Evidence-Based Management Guide to point the attention of the student to important concepts, ideas, 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 collaboratively developed by Scrum .org, the Professional Scrum Trainer Community, Ken Schwaber, and Christina Schwaber
No changes have been made to the content of the Scrum Guide, Nexus Guide, and Evidence-Based Management Guide.
License - Attribution Share-Alike license of Creative Commons
This course contains the use of artificial intelligence.