You will learn how to:

• Define Scrum including the Scrum Team, Scrum Artifacts and Commitments, and Scrum Events and Activities
• Define Agile values and principles and relate these to Scrum
• Define empiricism
• Understand the drawbacks of only partially implementing Scrum

You will learn about: 

• The three Scrum Accountabilities: ScrumMaster, Product Owner, and Developers and how they work collaboratively to deliver valuable Increments each Sprint 
• What each of the three Scrum Accountabilities is responsible for

You will learn about:

• The five Scrum Events, including Sprint Planning, the Daily Scrum, the Sprint Reviews the Sprint Retrospective, and the Sprint itself
• How the Scrum Events support Empiricism
• How and when a Sprint might be terminated
• Effective techniques for Refining the Product Backlog

You will learn about:

• The three Scrum Artifacts, the Product Backlog, the Sprint Backlog and the Increment
• The Commitment for each Artifact, the Product Goal, the Sprint Goal and the Definition of Done
• Why it is important that there is only 1 Product Goal and 1 Sprint Goal
• The importance of a strong Definition of Done and how to create one
• Why multiple Scrum Teams working on the same product have a common Product Goal and Definition of Done

You will learn: 

• The differences between facilitating, coaching, teaching and mentoring
• How to facilitate group decision making 
• When to and when not to facilitate 
• How a ScrumMaster provides effective leadership for their Scrum Team and the wider organisation 
• Effective development practices that will enable the Developers to create releasable and usable Increments each Sprint 
• How the ScrumMaster provides service to the Scrum Team
• How the ScrumMaster provides service to the Product Owner
• How the ScrumMaster provides service to the wider organisation
• Why there is no Project Manager in a Scrum Team