Scrum works great for small teams, but what happens when a company has hundreds of developers? Alex explains popular scaling frameworks like SAFe, LeSS, and Scrum@Scale, while Erin questions whether adding more process really keeps things Agile—or just turns it into bureaucracy with extra meeting.

Estimating work in Agile isn’t about perfect accuracy—it’s about making informed guesses using techniques like Story Points, Planning Poker, and T-shirt sizing. Alex explains why teams estimate effort instead of time, while Erin wonders if Story Points are just a way to avoid real deadlines.

Scrum teams rely on three key artifacts—the Product Backlog, Sprint Backlog, and Increment—to keep work transparent and focused. Alex explains how these artifacts help teams prioritize and deliver value, while Erin questions if the backlog ever truly gets shorter and whether "increment" is just a fancy word for progress.

Scrum runs on a set of structured events—Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective—designed to keep teams aligned and productive. Alex breaks down how each event serves a purpose, while Erin questions whether daily meetings are really necessary and if retrospectives ever go beyond just complaining.

Scrum has three key roles: Product Owner, Scrum Master, and Developers—but what do they actually do? By the end, you'll know who’s responsible for what—and why Scrum teams don’t need micromanagement to thrive.

What is Agile? What is Scrum? And why does everyone keep using these terms like they’re common knowledge? In this episode, Alex breaks down the origins of Agile and how Scrum helps teams work smarter, not harder. Erin, the curious newbie, asks the big questions (and a few skeptical ones) to get to the bottom of why Scrum became the go-to framework for modern teams. If you’ve ever felt confused by Agile jargon, this is the perfect place to start.