BONUS: Why AI Is Agile's Best Use Case With Melissa Reeve   AI is often framed as a technology rollout, but Melissa Reeve makes a different case: organizations that already know how to learn, adapt, and improve are better prepared for AI. In this BONUS episode, we connect Lean, Agile, DevOps, and AI-native work, and explore why Scrum Masters may be closer to the center of AI adoption than they think.

  From Toyota Production System to AI-Native Work   "I didn't really have words for what would later be my career. I didn't know about systems thinking. I didn't know about this thing called Agile."

 

  Melissa traces the through-line from studying the  Toyota Production System  in Tokyo, to early  Agile marketing, to developing intellectual property at  Scaled Agile, and finally to AI. Her point is that Lean, Agile, and AI-native work are not separate conversations. They all depend on sensing what is happening, shortening feedback loops, learning from reality, and improving the system instead of only optimizing individual tasks.

  The DevOps Lesson for AI Adoption   "People go from doing the task to building, monitoring, and maintaining the automations that do the task."

 

  Melissa's AI turning point came after  ChatGPT  arrived in November 2022. At first she was skeptical, then she started seeing end-to-end marketing workflows that could be changed with AI. That reminded her of the  DevOps  shift, where software teams moved away from throwing work over the wall and toward automated testing, deployment, and delivery pipelines. For Scrum Masters, the lesson is practical: AI is not only about automating Jira tasks or writing user stories faster. It changes the workflow, the roles around the workflow, and the learning loops that keep the work useful.

  Scrum Masters as AI Change Leaders   "What are Scrum Masters really good at? They're good at helping teams adopt new ways of working."

 

  Melissa sees a positive opening for Scrum Masters and Agile coaches. Organizations have bought AI licenses and told people to experiment, but many leaders are still unclear about how AI should change real work. Scrum Masters already work with flow, bottlenecks, experiments, psychological safety, and improvement backlogs. That gives them a useful place to start: map one or two workflows with the team, clarify decision rights, identify where AI can remove or improve steps, and surface concrete wins that others can learn from.

  From Linear Organizations to Hyperadaptive Work   "A hyperadaptive organization compresses both of those dimensions."

 

  In  Hyperadaptive, Melissa contrasts linear organizations with hyperadaptive ones. Linear organizations move through strategy, execution, concept, and delivery with many handoffs and delays. Hyperadaptive organizations compress those delays by organizing around value, distributed decisions, and continuous learning. She points to  Tomorrow.io  as an example of an AI-native company that could run a much smaller marketing team because workflows were designed differently from the start. She also uses  Moderna  to show the other side: a large pharmaceutical company using AI to pursue a goal that would be impossible under normal industry timelines.

  Learning Loops, Communities of Practice, and the Retrospective Backlog   "We surface our backlog of improvement items and there they sit."

 

  For Scrum Masters, Melissa brings the conversation back to familiar territory: communities of practice, retrospectives, and improvement backlogs. Moderna's AI rollout included ways to identify power users and spread learning through a community. Scrum teams already have the bones of that system, but the weak point is often follow-through. Teams identify improvements, then lose track of them. Melissa's challenge is to use AI to manage those learning loops better: keep improvement items visible, help prioritize them, watch capacity, and make sure learning from retrospectives turns into action.

  The FOCUS Framework for Choosing AI Use Cases   "Is it organizational? Does it fit with your organizational goals or your team goals? Or is it just a random act of AI?"

 

  Melissa uses the FOCUS framework to help teams choose high-value AI work instead of chasing every new possibility. Fit asks whether the idea connects to team or organizational goals. Organizational pull asks whether others will use it, or whether it is a one-person tool. Capability checks whether the team can actually build it. Underlying data asks whether the data is good enough. Success metrics ask how the team will know the AI initiative made a difference. This is a natural fit for Scrum Masters because it connects AI adoption to value, capacity, and inspect-and-adapt thinking.

  The Five Stages of AI Adoption   "AI learning is social learning, and we need to harvest the learning from each other and spread it."

 

  Melissa outlines five stages of AI...