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.
Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at
Always leaning on the Scrum values and Agile principles (even before he knew about them), Fred has guided numerous teams through their Agile Journeys over his 20-year career in Technology leadership. Driven by a passion for continual improvement and finding a balance between people, process, and tools. And Fred knows his own journey is just as important.
Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy 
As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? 