Scrum Roles: Product Owner, Scrum Master, and Developers

Scrum defines only three accountabilities—Product Owner, Scrum Master, and Developers—but these roles shape everything about how a Scrum team works. In this Scrum Foundations lesson, Mike Cohn explains what each role is responsible for, how they collaborate, and why great teams look very different from groups of individuals working side-by-side. You’ll learn: • What it actually means to be a Product Owner—and why there must always be just one • How Developers collaborate across disciplines (and why “developer” doesn’t only mean programmer) • What makes the Scrum Master a neutral facilitator, change agent, and productivity amplifier • Why the best Scrum teams show unity, healthy debate, pride in their work, and shared ownership • How great teams avoid the “us vs. them” mindset that plagues traditional projects Mike also shares real-world examples—from thrill-your-users Product Ownership to teamwork that feels like family—to illustrate what effective Scrum roles look like in action. If you’re learning Scrum for the first time (or teaching it to others), this video lays the foundation for understanding how high-performing Scrum teams truly operate. Continue your agile learning: Explore deeper training inside the Agile Skills Video Library: 👉 https://www.mountaingoatsoftware.com/training/courses/agile-skills-video-library?utm_source=YouTube Chapters 00:00 Introduction 00:37 What Scrum Product Owners Really Do 02:39 What Developers in Scrum Really Do 04:25 What Awesome Scrum Teams Have In Common 05:11 What Scrum Masters Really Do