BONUS: AI Makes Starting Work Easy, But Flow Still Finishes It With Liz Rettig

AI is changing software teams, but Liz Rettig brings the conversation back to flow, strategy, and the discipline of finishing. In this BONUS episode, Vasco and Liz explore how Scrum Masters can use AI to make policies visible, help teams manage WIP, support Product Owners, and keep the organization focused on valuable slices instead of faster output alone.

From Anthropology To Kanban And AI

“As a Scrum Master, you’re an anthropologist because you’re watching people and you’re recording how they are working.”

Liz starts with her path from anthropology to Scrum Mastering, agile coaching, and professional Kanban training. That background matters because her work has always been about observing how people interact with systems. AI did not replace that skill. It made the system easier to see.

In one client engagement, a team adopting an agentic framework also needed agile ways of working around that new capability. Liz saw that AI could help teams reach forecasting, strategy, and board-reading conversations much faster than before, as long as the human system was still designed with intent.

AI Helps Teams See Flow Earlier

“This is a tool that can help me get teams further quicker than ever before.” Continue reading BONUS: AI Makes Starting Work Easy, But Flow Still Finishes It With Liz Rettig

BONUS: AI Is Not Just Typing Faster With Marcus Hammarberg

In this BONUS episode, Vasco Duarte and Marcus Hammarberg explore what changes when AI agents move from writing small functions to creating whole features, running through tickets, and even improving their own instructions. The conversation keeps coming back to a simple but difficult question: if agents make software delivery faster, what should we use that speed for?

When the Agent Writes the Feature

“What I realized was that the agent could now write the code from a prompt that I gave it, and it was good enough that I didn’t have to touch a lot of it.”

Marcus starts with the moment that changed his own practice: in December 2025, he used an AI agent to build a feature for a flow metrics app based on Jira change logs. Before that, AI coding felt like asking for small functions and then cleaning up the result.

This time, the agent could take a feature-level prompt and produce something useful. That shifted the question from “can AI help me type code?” to “what happens to planning, quality, and ownership when implementation becomes dramatically faster?”

Slowing Down Enough To Think

“You end up not only not having seen the code, but not maybe even know what you wrote.” Continue reading BONUS: AI Is Not Just Typing Faster With Marcus Hammarberg

BONUS: The Scrum Master’s AI Prompt Library, with Joshua McDonald

In this BONUS episode, Joshua McDonald shares how he uses AI in the daily work of a Scrum Master, from team summaries and leadership updates to retrospectives and coaching preparation. The conversation is practical and grounded in one clear warning: AI can give Scrum Masters time back, but it cannot replace their judgment.

When AI Stops Being a Toy and Starts Saving Real Time

“It would have to be when it started to save me about one to two hours per day.”

Joshua’s turning point came when AI moved from curiosity to practical assistant. He began using tools like Microsoft Copilot to analyze reports, prepare communication, and package updates for different audiences. The value was not that AI did the thinking for him. The value was that it helped him reach useful coaching conversations faster, especially when working with reports on predictability, volatility, and cycle time.

Turning Flow Data Into Better Coaching Conversations

“It was able to pinpoint where the bottlenecks were, and where I should look.” Continue reading BONUS: The Scrum Master’s AI Prompt Library, with Joshua McDonald

Deborah Colombari: Stable Agile Teams Make Delivery Predictable

“When I have a stable team, I have reliable data.” – Deborah Colombari

For Deborah, success as a Scrum Master comes down to one word: stability. A stable team communicates better, shares knowledge, avoids hero-driven delivery, and becomes predictable enough that the Scrum Master can use historical data instead of wishful thinking.

Deborah connects stability with flow metrics and statistical thinking. When an expedite request appears, a stable team can look at its own history and forecast with a useful level of confidence. An unstable team, by contrast, creates silos, overloads key people, and turns every new request into a crisis.

Vasco connects Deborah’s answer to systems thinking and statistical process control: the team is part of a wider system, and its delivery capability reflects that system. The point is not to force the team to commit beyond what the system can support. The point is to observe the system, improve it, and use real data to forecast what is likely to happen.

Self-reflection Question: Do you know your team’s delivery capability from evidence, or are you still depending on optimistic commitments?

Featured Retrospective Format for the Week: The 4Ls Retrospective

Deborah recommends the 4Ls retrospective: liked, learned, lacked, and longed for. She adds one practical extension: an action-items column. Deborah likes the 4Ls because the quadrants help the team see the same issue from different angles.

Something the team longed for may connect to something they learned. Something they liked may expose what was previously missing. The action-items column matters because complaint is easy, but turning a complaint into a concrete experiment is harder. Deborah uses those actions to create or update team agreements, making the retrospective outcome last beyond the meeting.

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 Deborah Colombari

Deborah ColombariDeborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.

You can link with Deborah Colombari on LinkedIn.

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

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.

 

Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Access three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!