Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: AI Changes Management, Not Leadership
In this BONUS episode, we explore what AI changes for software leaders, and what it leaves firmly in human hands. Mateo Bervejillo, CEO of Xseed Solutions and author of Back to Basics, brings the view of a manager of managers: AI can help us process information faster, but leadership still happens through clarity, judgment, and relationships.
From Attorney to Software CEO: Clarity as a Leadership Skill
"What are we building? Why are we building it? What's the benefit for the client? What's the business value?"
 
Mateo started his career as an attorney, then moved through operations, vendor management, business development, and finally into software company leadership. That path gave him an unusual advantage in technology: an obsession with clear definitions. In law, unclear scope creates risk. In software, unclear scope creates waste, frustration, and products that miss the point. For Mateo, leadership starts before execution, with crisp answers to simple questions: what problem are we solving, why does it matter, and what would success look like?
AI Removes Busywork, But It Does Not Replace Leadership
"There's a part about management that is moving information around, up and down, sideways. That is changing drastically because of AI."
 
Mateo sees AI transforming the administrative side of management: gathering data, processing updates, preparing reports, and helping managers stay on top of follow-ups. But he draws a firm line between management mechanics and leadership. AI can make managers faster at moving information, but it cannot choose the right people, create trust, provide meaningful feedback, or understand what motivates each person. The danger is that organizations may conclude they need fewer leaders because the reporting work became easier, while the human work actually becomes more important.
The One-on-One Cannot Become a Slack Check-In
"If you have one manager leading 50 people, that one-on-one that was so important now becomes a Slack message."
 
One of the risks Mateo calls out is the pressure to flatten organizations and stretch managers across too many people. On paper, AI makes that look possible. In practice, it can turn leadership into status collection. Mateo described his own weekly rhythm: face-to-face conversations, walking meetings, and one-hour one-on-ones where the work is to listen, ask questions, understand what is happening in the person's life and work, and keep the company aligned around its North Star. That is not overhead. It is the work that keeps teams healthy before problems become escalations.
Use AI as a Sparring Partner, Not as the Thinker
"The problem of the blank page goes away with AI. You can have a conversation."
 
Mateo uses AI as an assistant for podcast preparation, idea generation, research, outreach, and even book writing. When drafting Back to Basics, he used AI to challenge the structure and ask what was missing, which led to several chapters he had not planned. The point is not to outsource judgment. It is to remove the fear of starting, create better first drafts, and pressure-test thinking. For Scrum Masters and agile coaches, that means AI can help design workshops, prepare questions, and explore options, but the leader still has to understand the context and make the call.
Outcomes Keep Leaders Away From Micromanagement
"Too much focus on the inputs can be misleading and you forget about the outcome, which is where the client sits."
 
AI gives managers more visibility into activity, and that can quickly become control. Mateo's antidote is to keep the organization focused on outputs and outcomes instead of inputs. Story points, process steps, and activity metrics can be useful, but they can also pull leaders into managing the wrong thing. Clients care about outcomes. Teams need clarity about the result, then room to decide how to get there. When leaders become obsessed with the how of every input, they move from creating clarity into micromanagement.
Managing Up With AI, Managing People With Care
"Today we are going through a time where we need to stay close to people more than ever and make it personal."
 
In Mateo's book, leadership is framed across four dimensions: managing up, managing yourself, managing teams, and managing sideways. Through the AI lens, he sees the biggest immediate gain in managing up: clearer communication, faster delivery, better follow-up, and fewer things falling through the cracks. But when it comes to managing teams, the basic human work becomes more important. People are anxious about AI and jobs, even when they are not saying it openly. Leaders need to stay close, make the relationship personal, and create the conditions where people can thrive.
About Mateo Bervejillo
Mateo Bervejillo is CEO of Xseed Solutions, a Montevideo-based software development and staff augmentation company helping US firms build high-performing LATAM engineering teams. An attorney by background, he brings a results-first view to tech leadership. He wrote Back to Basics, a practical leadership guide for new managers in technology. LinkedIn.
 
You can link with Mateo Bervejillo on LinkedIn, learn more about Xseed Solutions, and listen to Mateo's podcast, The Future Of The Future.

Oluyomi Emmanuel: Product Owners Who Turn Feedback Into Agile Team Learning
The Great Product Owner: Listening, Investing, and Learning With the Team
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"A great product owner is not the person with all the answers. It is the person who creates access to the right evidence." - Oluyomi Emmanuel
 
Oluyomi shares the example of a Product Owner whose strongest habit was asking the team for feedback, listening without defending himself, and then acting on what he heard. In one sprint review, the team looked at internal metrics and raised a difficult concern: they were completing work, but it did not always seem closely connected to what customers needed. The Product Owner could have defended the roadmap or blamed incomplete metrics. Instead, he treated the feedback as evidence worth investigating. He secured a training budget and enrolled both himself and the whole team in behavior-driven development training. More importantly, the training did not remain a certificate exercise. The Product Owner joined the learning and helped bring BDD practices into refinement, stakeholder conversations, and interviews. The team's conversations moved from abstract requirements to specific situations and expected outcomes. Hidden assumptions became visible earlier, and the team could challenge unclear requirements constructively before implementation began.
 
Self-reflection Question: How does your Product Owner show the team that feedback changes real behavior?
The Bad Product Owner: The Absent Product Owner as a Role Design Problem
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"An absent product owner is often not an individual time management problem. It is usually a role design problem." - Oluyomi Emmanuel
 
Oluyomi also describes the absent Product Owner anti-pattern. In his example, the Product Owner was not careless or uninterested. The structural problem was that the same person was both Product Owner and line manager, so the Product Owner role kept being squeezed into whatever time remained. Epics existed, but the team lacked enough context to refine them. Questions accumulated, refinement became a place to discover missing information, and important decisions waited for someone who was rarely available. Oluyomi first asked for more Product Owner availability, but that did not change the system because the competing responsibilities remained. He then created a stakeholder map for the major areas of work: who had the business problem, who owned the desired outcome, who had specialist knowledge, and who would be affected by the change. Inviting relevant stakeholders into refinement gave developers direct access to context. The lesson was not to remove product ownership, but to stop making the Product Owner the only messenger between the team and every stakeholder.
 
In this segment, we refer to behavior-driven development, product ownership, and stakeholder collaboration.
 
Self-reflection Question: Are you compensating for an unavailable Product Owner in a way that keeps the real organizational design problem hidden?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Oluyomi Emmanuel
 
Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.
 
You can link with Oluyomi Emmanuel on LinkedIn.

Oluyomi Emmanuel: Constructive Independence as a Scrum Master Success Metric
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Success is when the team increases its capacity to notice, discuss, and solve the problems that stand between them and meaningful outcomes." - Oluyomi Emmanuel
 
Oluyomi's definition of Scrum Master success has changed over time. Today, he measures success by the team's growing ability to notice, discuss, and solve the problems that stand between them and meaningful outcomes. One practical signal is when someone in the team says or does something he would previously have needed to prompt: a developer challenges an unclear requirement, a tester raises a risk before anyone asks, or a team member names a problem directly. Oluyomi calls the strongest indicator "constructive independence." That does not mean the team no longer needs support. It means the team's mental model has matured enough that people act earlier, with more ownership and less dependency. To keep himself accountable, Oluyomi runs a small personal retrospective at the end of each workday. He starts the day with a few things he wants to measure himself by, then later uses Copilot as a reflection partner to compare intention with action. Vasco notes that this is one useful way AI tools can help Scrum Masters maintain the discipline of reflection without relying only on memory.
 
Self-reflection Question: What would tell you that your team is becoming constructively independent?
Featured Retrospective Format for the Week: True or False Statements
Oluyomi does not pick a retrospective format before understanding the sprint. He watches patterns during the iteration: how work waits, how conflict is handled, whether decisions are revisited, and whether people ask for help early. One format he often uses is a set of true-or-false statements about the sprint and collaboration. For example: "We finished work before starting more work" or "We asked for help early enough during the sprint." Team members vote silently first, either on a Miro board or with physical cards. The value is not the majority answer. The value appears when different people interpret the same sprint differently. Instead of asking who is right, Oluyomi asks what each group observed that led to its answer.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Oluyomi Emmanuel
 
Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.
 
You can link with Oluyomi Emmanuel on LinkedIn.

Oluyomi Emmanuel: Creating Agile Value Stream Visibility Without More Administration
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Transparency is not created by displaying more information. Transparency is created when people share enough meaning to interpret that information in the same way." - Oluyomi Emmanuel
 
Oluyomi's current challenge is helping an organization create end-to-end visibility and ownership across several value streams without turning the solution into another layer of administration. At first, the problem looked like a Jira hierarchy issue: initiatives, epics, stories, and tasks needed shared definitions. But the conversations exposed something deeper. Different groups used the same work item names to mean different things, and those differences made prioritization, dependency management, coordination, and reporting harder. Together with a colleague, Oluyomi framed the work as alignment experiments instead of a large rollout. One workshop asked what makes an initiative different from an epic, what information must exist before work moves forward, and when the next level of work should be created. The biggest tension was ownership, not terminology. A second experiment, a cross-value-stream visibility session, used real initiatives to expose overlapping work, unclear ownership, and weak links to outcomes. Vasco then pushed the conversation toward intake: perhaps the problem was not only shared meaning, but the absence of a single view of what the organization needs to do. Oluyomi's next experiment is linking initiatives to quarterly goals and OKRs to see what really deserves attention.
 
In this episode, we refer to value streams, OKRs, and portfolio management.
 
Self-reflection Question: Does your organization have one visible list of important work, or many competing lists with unclear ownership?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Oluyomi Emmanuel
 
Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.
 
You can link with Oluyomi Emmanuel on LinkedIn.

Oluyomi Emmanuel: From My Task to Our Work in Agile Teams
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"We shifted their thinking from my task to our work." - Oluyomi Emmanuel
 
Oluyomi describes a destructive pattern many Scrum Masters will recognize: local responsibility inside a supposedly shared team. The team looked collaborative during Scrum events, but once the meetings ended, developers, testers, and reviewers behaved like separate specialists. Developers finished coding and moved on. Testers waited for the right context or environment. Pull requests sat in review. Everyone looked busy, and everyone could explain their own behavior, but work was not reaching Done. The board already showed the queues, yet visibility alone did not change behavior because the team still spoke in individual language: "my development is finished," "testing belongs to QA," and "my task is done." The change started in a retrospective, where the team stopped asking who caused the delay and began asking where work stopped flowing. They tested small experiments: swarming around items waiting in testing, reviewing aging work together, and avoiding new starts when existing work needed help. The daily standup became a place to ask a better question: what does this item still need before value can be delivered?
 
In this segment, we talk about flow, team ownership, and work in progress.
 
Self-reflection Question: What language in your daily standup reinforces "my task" instead of "our work"?
Featured Book of the Week: Handbook of Facilitative Leadership by Pepe Nummi
Oluyomi recommends Handbook of Facilitative Leadership: Concrete Ways to Boost Performance by Pepe Nummi. The book helped him see that leadership is not always about having the strongest opinion or offering the solution. Sometimes leadership means designing the process through which a group can think, contribute, decide, and take ownership together. For Scrum Masters, that distinction matters because the people in the room often already have the knowledge needed to solve the problem. The knowledge is just distributed across the team. Facilitative leadership helps bring that knowledge into the open.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Oluyomi Emmanuel
 
Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.
 
You can link with Oluyomi Emmanuel on LinkedIn.