scrum master Archives - Page 2 of 173 - Scrum Master Toolbox Podcast

BONUS: How Scrum Masters Can Use AI Without Becoming the Human API, With Fred Deichler

AI is already changing the practical, everyday work of Scrum Masters and Agile Coaches. In this BONUS episode, Vasco talks with Fred Deichler about moving from curiosity to real AI-supported workflows: finding team signals faster, preparing better conversations, keeping documentation in sync, and staying focused on outcomes instead of just producing more output.

From Automation to an AI Sparring Partner

“I have this partner I can work with to help me ideate things.”

Fred’s journey into AI started before the current AI wave, with automation in Jira and the practical need to surface bottlenecks without manually watching every board. The turning point came when ChatGPT stopped feeling like a search box and started acting like a thinking partner.

Faced with a team being pushed toward multiple sprint goals, Fred dumped the context into AI and asked for three to five options instead of one “right answer.” That shift helped him move from a deterministic mindset into a problem-solving mindset, using AI to explore options, challenge his own assumptions, and prepare a better conversation with the team.

The Monday Morning AI Context Builder

“It instantly sets that context for me. It sets that tone for the whole week.”

Fred describes his weekly workflow as a very practical use of AI: on Monday morning, he opens Cursor and works with his own AI harness, Atlas. Atlas is built from markdown files containing persona, skills, history, meeting transcripts, notes, and Jira data. When Fred says “good morning,” the system pulls the most relevant signals forward: aging work items, backlog health, sprint goals, and where the next team conversation should focus. Instead of starting the week by hunting for data, Fred starts with questions he can bring into the first stand-up: what is stuck, what needs refinement, and what risk is already visible?

Making Flow Metrics Visible Inside Jira

“If you’re on a page, what do you hope you could learn without asking?”

Beyond using AI as a thinking partner, Fred used AI to build a Chrome extension that surfaces useful Jira insights directly where the team already works. On the active sprint board, it shows work in progress, aging items, sprint goals, and sprint changes. In the backlog, it exposes backlog health and epic health. On the sprint report page, it adds cycle time per item so the retrospective can move from generic discussion to concrete learning. The point is not to shame the team with metrics. The point is to make the right conversation easier to start: what caused this item to take seven days, what blocked it, and what do we want to learn from that?

AI as Extra Eyes and Ears for Team Conversations

“It helps make sure that we don’t lose sight of these things I can bring back to the team.”

Fred also uses AI agents to review meeting transcripts and look for patterns that are easy to miss in the flow of daily work. The system can notice hesitation, unresolved topics, or a requirement problem that was mentioned once and never followed up. For retrospectives, Fred’s Atlas setup can review sprint transcripts around day nine of the sprint and suggest themes for the next retro. It can even generate prompts for a visual retrospective board in Copilot or a Miro board from a prompt. This helps Fred avoid relying only on recency bias and creates a better starting point for the conversation the team actually needs.

Keep the Human in the Loop, Especially for Outcomes

“It’s not about building a faster hammer. It’s about identifying the outcome you’re going for.”

A major warning in the episode is that AI can make Scrum Masters faster at producing more of the same: more notes, more summaries, more documents, more reports. Fred argues that the useful question is not “can we automate this exact process?” but “what outcome are we trying to achieve?” In a Jira-to-Azure DevOps migration, for example, the goal was not to reproduce the current time-tracking process perfectly. The goal was to provide the information accounting needed. That outcome focus keeps the human accountable for direction, judgment, and value, while AI helps explore better ways to get there.

The SPOT Framework for Finding AI Opportunities

“If it meets three or four of those, this is a great opportunity for an automation to free me up to do that more human-centric work.”

Fred uses a simple filter, the SPOT framework, to decide what AI should help with and what should remain human-led. A task is a good candidate when it is simple, predictable, observable, and tedious. Simple means it requires low human judgment and could be explained on an index card. Predictable means it happens repeatedly, either on a schedule or triggered by an event. Observable means the needed data is available to the agent and not locked away in someone’s head or behind policy. Tedious means it consumes energy without adding much human value. When a task matches most of those criteria, Fred looks for ways AI can handle the toil while he stays focused on facilitation, coaching, and decision-making.

A Small Experiment Scrum Masters Can Try Tomorrow

“If a Scrum Master finds himself operating as, like, I’m moving data from point A to point B, that is a great opportunity to say, how might we do this?”

Fred’s concrete advice is to start by noticing where you have become the “human API”: moving data between tools, updating spreadsheets, copying information into reports, or keeping documents manually aligned with reality. Write down one tedious workflow and ask your approved work AI, “How might we automatically populate this, while keeping me in the loop?” Vasco adds a useful ideation tip: if the first five ideas are not good enough, ask for five more without repetition, then five more again. The goal is not to hand over accountability. The goal is to discover what might be possible and choose one safe, small experiment.

Resources for Scrum Masters Exploring AI

“It’s all about building up your own idea of what’s possible to start those how-might-we conversations.”

For listeners who want to keep learning, Fred recommends The AI Daily Brief as a way to stay current with what is happening in AI, and Jack Roberts’ YouTube channel for practical ideas around personal AI and agent-based workflows.

About Fred Deichler

For over two decades, Fred has been a technology leader, who has been intuitively following the Scrum values and Agile principles even before discovering them. He has successfully led multiple teams on their Agile journeys, emphasizing the importance of a harmonious balance between people, processes, and tools, and continuously striving for improvement. For Fred, personal growth is as crucial as professional development.

You can link with Fred Deichler on LinkedIn and connect with Fred Deichler at Triforce Agility.

Arun Parameswaran: Success for Scrum Masters Means Teams Ask Better Questions Without You

“My goal isn’t to become indispensable. My goal is to create a team that doesn’t depend on me.” – Arun Parameswaran

For Arun, Scrum Master success is not measured by how many meetings he runs or how often the team asks him for help. It is measured by the team’s ability to solve problems without depending on him. If he has to remind everyone to update Jira, facilitate every difficult conversation, or resolve every obstacle, he is creating dependency.

A healthier signal is when team members talk directly to each other: “This is blocked. Who can help me?” or “Let’s finish this before starting something else.” Arun compares the Scrum Master to a football coach watching the match from the side.

The team needs space to play, make decisions, and learn. The Scrum Master still observes and coaches, but the goal is to intervene less often and more intentionally. As Vasco summarizes, this requires learning to wait before stepping in.

Self-reflection Question: What would your team do differently if you waited one more minute before intervening?

Featured Retrospective Format for the Week: What? So What? Now What?

Arun’s favorite retrospective format is “What? So What? Now What?” because it moves the team from facts to meaning to action. “What happened?” helps the team describe reality. “So what?” asks why it matters. “Now what?” turns the discussion into a small experiment for the next sprint. Arun also avoids using the same format every time.

He often shares the board two or three days before the retrospective so people can reflect before the meeting, add observations, and appreciate teammates. That preparation saves time in the session and makes space for a short fun activity before the team works through the real topics. His goal is simple: every retrospective should produce learning and at least one concrete experiment.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Arun Parameswaran

Arun is an Agile delivery leader at Bosch Global Software Technologies who builds high-performing, data-driven ecosystems. He blends flow metrics, Jira analytics, Power BI, and applied AI to turn delivery into a transparent, predictable system.

You can link with Arun Parameswaran on LinkedIn.

Arun Parameswaran: The Scrum Master Mistake of Fixing Trust With Process

“Don’t confuse activity with progress.” – Arun Parameswaran

When Arun Parameswaran stepped into one of his first Scrum Master assignments, he joined a distributed team where everything looked normal from the outside. Meetings were happening, Jira was updated, and work appeared to be moving. Underneath that surface, knowledge was unevenly shared, communication between locations was weak, and trust was not yet strong enough for people to speak openly.

Arun’s first instinct was to add more structure: more meetings, more activities, more process. Looking back, he saw the real mistake. He was creating activity, not progress. The shift came when he stopped trying to provide answers and started listening through one-on-one conversations.

He learned where people were struggling, what they expected from him, and what the team needed to own for itself. In this episode, Arun shares why Scrum Masters must understand people before changing the process, and why the best coaching often starts by asking better questions.

Self-reflection Question: Where are you adding process today because the real issue feels harder to talk about?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Arun Parameswaran

You can link with Arun Parameswaran on LinkedIn.

BONUS: When Burnout Looks Like Productivity—The Hidden Risk to Your Team’s Innovation Capacity

In this BONUS episode, Alison Campbell, CEO of unBurnt, and researcher at Bentley University shares the research that reframes burnout as a measurable threat to a team’s ability to innovate. We learn why your most productive people may be your biggest innovation risk, how to spot capacity draining out of a team before the output drops, and where Scrum Masters have the leverage to protect the one thing that keeps teams building: the space to think.

From the ER to the Research

“I kept normalizing the stress, the exhaustion, eventually the stomach aches as, well, this is just the price of entry. This is part of being a busy, full-time executive and working mom.”

Alison spent nearly twenty years in corporate roles—moving from finance to e-commerce to HR tech, with analytics as the through line and a love for the building phase inside companies. The pandemic was the turning point. With two young kids at home and a global team to hold together, she pushed through eighteen months of warning signs she had normalized, until severe stomach pain landed her in the emergency room needing surgery.

That was the stop moment.

What started as private shame—the feeling that she alone had failed while everyone else “had it all figured out”—became a research question the moment she started talking about it and heard the same story mirrored back from colleague after colleague. This wasn’t one exhausted mom at a hard moment. It was a design and systems problem worth studying.

When Burnout Looks Like Productivity

“Even when that innovative work behavior was high, when burnout was high, that segment of our sample had the lowest innovation capacity of the entire group we surveyed.” Continue reading BONUS: When Burnout Looks Like Productivity—The Hidden Risk to Your Team’s Innovation Capacity

Joshua McDonald: Scrum Master Success Means People Feel Heard, Respected, And Safe To Speak Up

“I hope you can feel heard and respected at the end of the day.” – Joshua McDonald

Joshua defines Scrum Master success through the team’s comfort with self-organization, respectful pushback, and asking for help when they do not know what they do not know. For him, a successful team is not drama-free because nothing hard happens.

It is low-drama because people can raise problems without fear, communicate openly, and keep moving forward even on bumpy roads. Joshua keeps himself honest by reviewing retrospective notes, one-on-one notes, and the commitments he made to follow up. He keeps a running to-do list from Slack messages, meetings, and team conversations so feedback does not disappear after someone shares it.

Periodically, he brings past retrospectives back to the team and asks what they accomplished, what changed, and whether anything fell through. That ledger matters because Scrum Masters work through people. If people feel heard and respected, they are more likely to keep working with you, regardless of your title.

Self-reflection Question: What system do you use to make sure team feedback turns into visible follow-up?

Featured Retrospective Format for the Week: Personalized AI-Themed Retrospectives

Joshua’s favorite retrospective format is never using the same format twice. He noticed teams getting bored and agitated when the same sailboat or standard board appeared every sprint. His answer was to personalize retrospectives around team members’ interests: a BMW theme for a developer who liked cars, a beach theme after someone’s vacation, or a TV-show theme tied to a person’s hobby.

He uses tools like Mural, Zoom whiteboards, Microsoft Teams, and AI-generated visual themes to make each retro feel like it was designed for someone in the team. The point is not decoration. The point is listening. When people recognize their interests in the retro, they feel seen as people before they reflect on the work.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Joshua McDonald

Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he’s already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.

You can link with Joshua McDonald on LinkedIn.