Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: AI in the SDLC Puts Customer Feedback Before Faster Typing

AI is already changing software development, but David Mantica argues that the real shift is not only in code generation. In this BONUS episode, Vasco and David talk about what happens when AI enters the whole software development life cycle: executive decision-making, Scrum Master work, product feedback, data quality, agentic systems, and the human skill of learning to adapt.

From Executive Curiosity to Real AI Use Cases

"You have two directions you can go with AI. One is productivity. The other part of AI that organizations haven't quite tapped into yet is how do you make money with it?"

David describes AI adoption as something that, like agile and AWS before it, often starts in the middle of the organization before executives fully understand what is happening. Early conversations were about policy, regulation, and tool choices. Now, the conversation has moved toward use cases: where GenAI helps personal productivity, where agentic systems fit, and how organizations turn the tools into actual business value. David also points out a gap that matters for leaders: many executives know their people are using AI, but they are not using it deeply themselves, which makes it harder for them to see what is possible inside their own business model.

AI Should Move Teams Closer to the Business

"If a team does this right, they're going to keep getting closer and closer to the business. They're going to keep spending more time on what it is that we should be building, not on just building it."

For David, faster coding is only one part of the SDLC change. Scrum Masters can use AI to improve backlog work, user story mapping, retrospective follow-up, and team data, but the point is not better administrative output. The point is to free time for coaching, communication, and helping teams return to the agile way of working instead of being trapped by artifacts and process. If developers become faster while product discovery, testing, security, and customer feedback stay unchanged, the organization has only accelerated part of the system.

The Bottleneck Is Value, Not Typing Speed

"Can I test more before I go to production? And can I talk to the client more before I actually lock in?"

David and Vasco connect AI in the SDLC to product discovery. Coding tools such as Factory may help teams produce software faster, but David argues that the bigger opportunity is to test more ideas, prototypes, classes, webinars, or internal tools with real customers. This links directly to The Black Swan by Nassim Nicholas Taleb: only the market can tell us what is valuable. In practical terms, AI should help teams bring product thinking closer to the coder and bring customer feedback into the SDLC instead of treating it as something that happens after delivery.

Governance Has To Catch Up With AI Productivity

"Organization uses AI, they see the productivity increases, they hire 10-20% less staff because they're getting that productivity increase, and then they create no real new value."

David is blunt that many organizations are not yet changing governance, portfolio decisions, budgeting, or success metrics fast enough. Measuring more pull requests per developer is not the same as measuring more value for customers. Vasco and David explore the need for internal product marketing, lightweight feedback loops, and ways for internal and external customers to touch, test, and react to what is being built. Without that, companies risk using AI to reduce cost while missing the larger opportunity: learning faster than competitors.

Agentic Systems Are Only As Good As Their Data

"The agent is only as good as the pool of information by which it's pulling from to answer the questions by which you're asking it to answer."

Data quality becomes much more concrete when agents move from answering questions to taking action. David frames agentic systems as coded agents: they behave like a person using GenAI, but they still depend on the information they can access. That means teams need to think carefully about grounding, retrieval, trusted documentation, and the boundaries around what an agent is allowed to use. A weak data pool creates weak action, and a poorly grounded customer service agent will act like a poorly trained human agent.

Lightweight Testing Beats Big AI Programs

"What is your lightweight way of testing your agents without boiling the ocean?"

David warns against treating AI adoption as a top-down program that must be perfect before anyone uses it. Agentic systems will make mistakes, just like people do, so teams need controlled environments, visible feedback, and repeated adjustment. Vasco connects this to startup odds: most new initiatives fail, so the answer is not to plan harder, but to test more ideas and learn faster. David's advice is to keep the experiments lightweight, fund learning, and build the capability to test agents without trying to build an entire AI universe first.

The Human Skill Is Adaptation

"The human skill needs to be teaching people to change and adapt, and be comfortable with getting rid of skills that they thought made them hundreds of thousands of dollars that are totally unnecessary now."

David closes with the human side of AI in software organizations. He connects AI adoption to adaptive leadership and the fear people feel when skills that once made them valuable may no longer be enough. For Scrum Masters, leaders, and product people, the work is to help teams learn, test, and adapt without pretending that the future is already clear. The customer remains the final judge of value, and AI makes that truth more urgent, not less.

About David Mantica

David Mantica is Managing Director at SoftEd, where he helps organizations build practical skills for AI, agile, leadership, and business analysis. With 30+ years of experience and 700+ speaking engagements, he makes emerging technology accessible for working teams. LinkedIn

You can link with David Mantica on LinkedIn and find role-specific AI resources at SoftEd.

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."

One of Joshua's first high-value AI workflows combined screenshots of team metrics with exported Jira stories. Instead of spending half a day scanning acceptance criteria, transitions, and bottlenecks, he used AI to identify patterns and suggest where to look next. From there, he would ask follow-up questions from the perspective of a Scrum Master, using AI as a sparring partner to prepare coaching talking points before speaking with the team.

AI as a Communication Coach, Not a Replacement for Judgment

"I like to use AI as my coach to help me in my communication style."

Joshua is careful with sensitive communication. When he needs to bring data, feedback, or a difficult pattern to an individual or team, he asks AI to help him test the wording. He might ask how a message could land with someone who has reacted defensively before, or request phrases to avoid. In that sense, AI becomes a preparation space: a place to roleplay, refine tone, and make sure the human conversation starts from care rather than accidental bluntness.

A Weekly AI Workflow for Scrum Masters

"I use it pretty much at everything I create."

Joshua's weekly rhythm includes AI-generated summaries from standups, backlog refinement, and retrospectives. He uses templates that identify who shared which updates, what action items emerged, and what the team should be able to review later. For retrospectives, he keeps a prompt library on a whiteboard, with prompts adapted for Scrum teams, Kanban teams, and team interests. A hiking team might get a Big Bend retrospective; a car enthusiast might get a BMW-themed one. The point is not novelty for its own sake, but creating retrospectives that feel more connected to the people in the room.

The Prompt Library as a Scrum Master Asset

"I save them. I reuse them. I refine them."

Joshua does not treat prompts as throwaway text. He keeps them visible on a whiteboard, labels them by purpose, and refines them over time. That library helps him preserve the structure of useful workflows while adapting the output to the team and context. For Scrum Masters and agile coaches, this is one of the practical takeaways: a prompt library becomes part of the working system, just like a facilitation kit, retrospective catalog, or coaching journal.

Faster Is Not the Same as Better

"I don't lean on it to do critical thinking for me."

Joshua connects AI adoption to a deeper risk: using it to produce more work without asking whether that work matters. He validates AI output, checks the data, and stays responsible for conclusions. AI helps him get to an end point faster, but the Scrum Master still owns the thinking, the interpretation, and the impact on people. That distinction matters when teams are being pushed to adopt AI without clear guidance.

What Scrum Masters Should Try on Monday

"Have it coach you. Say, this is my role. This is what's on my agenda for today."

Joshua's recommended first experiment is simple: do a personal standup with AI. Share what you did yesterday, what you want to do today, and the challenges in front of you. Then ask AI to act as your coach and help you identify focus, priorities, and possible next steps. Within a week, a Scrum Master can see whether this creates more clarity, better communication, and more intentional use of time.

Learning AI Without Waiting for Permission

"Start there with basic AI fundamentals."

For Scrum Masters who are new to AI, Joshua recommends beginning with practical courses on platforms like Udemy, Coursera, or LinkedIn Learning. Then, connect with peers who are already experimenting with prompt creation. The goal is not to become an AI expert overnight. The goal is to understand what AI can support, what it should not replace, and how to build a prompt library that improves your own work.

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.

Kaloyan Chalakov: Great Product Owners Start the Conversation Instead of Becoming the Boss

In this episode, we refer to Product Owner anti-patterns and team and PO collaboration.

The Great Product Owner: Open Communication, Active Listening, and Feasibility First

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.

"Start the open conversation and listen to the critical discussions." - Kaloyan Chalakov

Kaloyan describes the best Product Owner pattern as almost the opposite of control. A strong Product Owner comes to the team with the outcome, the timeline, and the stakeholder context, then starts a feasibility conversation. They ask what is possible, what is risky, what can be decomposed, and what the team needs in order to deliver. In Kaloyan's example, the Product Owner stayed focused on stakeholder communication while the team helped shape the work into something practical. Stakeholders were kept in the loop, risks were visible, and everyone could adjust plans early. The most useful behavior was not a personality trait, because every Product Owner is different. It was open communication and active listening, especially when the team raised uncomfortable technical or delivery constraints. Great Product Owners do not need the team to say yes to everything. They need the team to help them face reality early enough to make better product decisions.

Self-reflection Question: How often do your Product Owner conversations start with feasibility and shared reality, rather than commitment pressure?

The Bad Product Owner: Acting Like the Boss of 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.

"Tell me what exactly to do, and I'll do exactly what you're telling me to do." - Kaloyan Chalakov

The Product Owner anti-pattern Kaloyan warns us about is the Product Owner as the boss of the team. This shows up when the Product Owner assigns work, manages people, and controls every detail of delivery instead of focusing on product outcomes and customer needs. The consequence is a damaging loop. The team stops bringing their thinking and creativity, waits for instructions, and becomes task handlers. The Product Owner then feels overwhelmed because every decision and question returns to them, so they add more control. That control removes even more initiative from the team. Kaloyan connects this pattern to the Product Owner's real work: difficult conversations with customers, narrowing big requests into practical steps, and protecting focus on product value. When the Product Owner becomes the team's manager, both product discovery and team self-organization suffer.

In this segment, we refer to Product Owner collaboration.

Self-reflection Question: Where might your Product Owner role be taking decisions away from the team instead of creating clarity for better decisions?

[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 Kaloyan Chalakov

Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.

You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: Building Scrum Master Success Around Trust and Unspoken Leaders

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 for me is making myself obsolete in the team." - Kaloyan Chalakov

Kaloyan defines Scrum Master success in a way that sounds funny at first: forty hours a week to drink coffee and do nothing. But the point is serious. Success means the team no longer needs the Scrum Master for every decision, question, or conflict. They are self-organizing, self-managed within their context, and able to call for help only when it really matters. When Kaloyan joins a new team, he avoids setting big targets in the first three months. He observes, builds trust, and watches for what the team does not show openly. One of his key signals is the presence of "unspoken leaders," the people the team looks to when something difficult happens. He learned that pattern first in safety-critical maritime work, where trust in the people beside you is not optional. For Kaloyan, Scrum Master success starts with trust, grows through observation, and ends when the team can stand on its own.

Self-reflection Question: Who are the unspoken leaders in your team, and how are you helping them strengthen the team's self-management?

Featured Retrospective Format for the Week: Open Room Coffee Conversation

Kaloyan's favorite retrospective format is simple: no heavy gamification, no elaborate setup, just a mature team in a room with coffee or tea and a real conversation. The team uses a ball as the talking object. Whoever wants to raise a problem takes the ball, shares what hurt during the last sprint, and asks for help. The format is unpredictable, so the Scrum Master must pay close attention to small signals: is the discussion becoming personal, is a conflict rising, or is the team finding the root cause together? Kaloyan likes the format because it brings real issues to the surface quickly, and often the third person to speak has already helped others see their own concerns more clearly.

In this segment, we refer to Karin Tenelius on self-management.

[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 Kaloyan Chalakov

Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.

You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: Coaching Organizations to Challenge the Beliefs Behind Agile Pressure

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.

"What's happening with the team is just the symptom of what's happening with the whole system." - Kaloyan Chalakov

Kaloyan brings a common Scrum Master challenge: a team under pressure from a Product Owner who starts acting more like a project manager. Planning turns into a list of tasks, Daily Scrum becomes a status report, and pressure flows from customers and market competition, through management, to the Product Owner, and finally to the team. In the conversation, Vasco and Kaloyan map the system and notice something deeper than pressure: the belief that a competitor's release will directly damage the company unless the team moves faster. That belief becomes the real intervention point. Kaloyan reflects that Scrum Masters can challenge assumptions, turn beliefs into testable hypotheses, and introduce alternative beliefs that reduce pressure instead of passing it down. The practical insight is powerful: do not fight pressure by adding more pressure. Look for the source, test the assumptions behind it, and design small conversations that change the system around the team.

In this episode, we refer to systems thinking and limiting beliefs.

Self-reflection Question: What belief is creating pressure in your organization, and how could you test it with one small conversation this week?

[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 Kaloyan Chalakov

Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.

You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: The Agile Team That Built Great Architecture But Forgot the Customer

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.

"You don't have to build it only because we can. We need to lead to a purpose." - Kaloyan Chalakov

Kaloyan worked with a technically strong team that could build impressive architecture, pipelines, and infrastructure fast. Sprint after sprint, they showed the quality of the technical system they were creating. But the hard question stayed unanswered: what customer problem were they solving? The wake-up moment came in a sprint review, when a client finally joined and told the team that the network and architecture were nice, but they did not solve the actual problem. The customer needed one small piece of functionality, and the team could not point to it. The room went silent. The Product Owner felt exposed, the team felt embarrassed, and Kaloyan saw the moment as painful but necessary. Because the mistake happened early, it became a learning opportunity instead of a product disaster. The team learned to connect technical excellence to product value, and to ask sooner whether their work solved the customer's real need.

In this segment, we talk about customer feedback and Sprint Review.

Self-reflection Question: What are you building because it is technically interesting, and how will you test whether it solves a real customer problem?

Featured Book of the Week: Start With Why by Simon Sinek

Kaloyan recommends Start With Why by Simon Sinek because it changed how he thinks before acting. The book pushed him to pause before solving a problem and ask what the real purpose is. He started applying that question in workshops, team conversations, and product discussions. When a team member asked why a leadership workshop included a specific activity, Kaloyan realized his explanation had not landed. Instead of pushing forward, he stopped, reset, and rebuilt the workshop around a clearer purpose. For Kaloyan, the "why" is not a one-time statement. It is a question to ask at every step, because people do better work when they understand how their part connects to the bigger goal.

[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 Kaloyan Chalakov

Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.

You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: When Textbook Scrum Hurt the Team, Learning to Adapt as a Scrum Master

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.

"It doesn't matter if it works for you. The most important thing is that it doesn't work for me." - Kaloyan Chalakov

Kaloyan Chalakov came into Agile after years in safety-critical environments, where control and preparation mattered. That background helped him, but it also created his first big Scrum Master trap: trying to be the "perfect" Scrum Master from the books. He pushed two-week sprints, events, and practices because that was how Scrum was supposed to work. Then one team member pulled him aside and told him the truth: the process did not work for him. Kaloyan's first reaction was defensive, because his pride was hurt. But that feedback became a signal. He started using that team member as a barometer for whether the change was actually helping. The lesson was simple and hard: one approach does not fit every team. Real Scrum Mastery starts when we treat resistance as information, take smaller steps, and adapt the system to the people doing the work.

In this episode, we refer to Agile adaptation and Scrum Master role.

Self-reflection Question: Where are you defending a process because it is "right," instead of listening to the team signals that show whether it is useful?

[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 Kaloyan Chalakov

Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.

You can link with Kaloyan Chalakov on LinkedIn.

BONUS: The Chip Race Behind AI With Rakesh Kumar

AI feels like a software revolution, but Rakesh Kumar argues that the next limits may come from chips, energy, and the physical systems underneath our code. In this BONUS episode, Rakesh explains why AI progress is tied to hardware, what software teams need to relearn about efficiency, and why the economics of data centers should matter to product leaders.

Why Chips Became a Society Topic

"The race about AI essentially becomes the race about chips."

Rakesh traces his path from a small town in India to computer science, chip research, entrepreneurship, and eventually writing The Chip Age. The turning point came during the COVID-era chip shortages, when cars, appliances, and everyday electronics became harder to buy. That moment made chips visible to people outside engineering. AI then raised the stakes further: the promise of new medicines, new materials, and major productivity gains depends on models that require enormous amounts of computation. For software people, that means chips are no longer background infrastructure. They are part of the product strategy, the cost model, and the operating constraint.

AI Progress Depends on Computation

"To the first order, the more chips you can use and the more data you throw in at training AI models, the more powerful an AI model becomes."

Vasco frames the shift with a sharp comparison: AlexNet used two GPUs in 2012, while newer frontier models use tens or hundreds of thousands of GPUs. Rakesh connects that growth to AI scaling laws. The problems AI is asked to solve have changed, from recognizing cats and dogs to scientific discovery and complex reasoning tasks. That creates pressure to train larger models with more data and more chips. The result is a world where software teams cannot assume that compute is cheap, abundant, or invisible. AI roadmaps are now connected to chip availability, data center capacity, energy, and the ability to use hardware well.

Software Teams Need to Care About Efficiency Again

"Software developers now have to refocus on performance, because that dictates the quality of AI you can serve and the cost of AI when you're serving AI."

For years, software teams could often rely on hardware getting faster underneath them. Rakesh says AI changes that habit. If two teams have access to the same number of chips, the team that extracts more useful work from those chips has an advantage. That advantage shows up in model quality, inference cost, latency, and energy consumption. Efficiency is no longer a niche concern for low-level specialists. It becomes a product concern. Teams building with AI need to understand where computation goes, how much energy it consumes, and which architectural choices make expensive infrastructure work harder than it needs to.

The Hardware and Software Boundary Is Moving

"Because of AI, the hardware design and the software design at some level, those abstractions have started merging."

Rakesh points to new AI-assisted chip design workflows, including the Jalapeno chip example Vasco mentions, as a sign that software and hardware work are moving closer together. Chip design that once took years can now be accelerated with AI-supported automation and specialized partners. At the same time, hardware choices are becoming more tailored to AI workloads. General-purpose chips offer flexibility, but specialized chips may offer much better efficiency. That creates a trade-off familiar to software leaders: optimize too narrowly and the target may move; stay too general and the system may be too costly to run.

The Data Center Constraint

"I think we have to figure out how to do AI efficiently. The current way of doing AI seems pretty unsustainable to me."

Rakesh warns that AI data centers are running into physical constraints. Large facilities can consume gigawatts of power, and a significant share of that power is used to move heat out of the system. There are also inefficiencies in generation, transmission, distribution, cooling, and in the short useful life of expensive GPUs when model requirements change quickly. For agile teams and product leaders, this matters because energy and infrastructure are becoming part of the real cost of AI features. The question is not only whether an AI feature works. It is whether it can be served responsibly, affordably, and at scale.

What Breaks First in the AI Supply Chain?

"The capacity of the grid grows really slowly. We have this slowly increasing supply now hitting against the AI exponential."

When Vasco asks what may break first if AI demand keeps rising, Rakesh ranks energy supply as the biggest challenge. New transmission lines and grid connections can take years, while AI demand grows much faster. Chip supply comes next: can the industry build enough chips fast enough? Cost is also a pressure point, especially for smaller companies, developing countries, and individual consumers. Rakesh also flags a broader economic risk: data centers can cost billions, and some financing is backed by older chips as collateral. If the economics fail, the impact may reach beyond individual AI companies.

What Software Developers Should Prepare For

"Generating functional code will be a lot easier in future than generating functional code that meets your performance and energy objectives and constraints."

Rakesh argues that every software engineer needs to become fluent with AI, but that is only the starting point. The valuable work may shift toward areas where AI still struggles: physical AI, robotics, IoT, sensors, performance, energy, and verification. If AI writes more code, teams still need ways to build confidence in that code. Vasco connects this to familiar engineering practices such as testing, performance testing, security testing, and maturation. The future may include much more software than today, but the scarce skill may be knowing how to make software trustworthy, efficient, and suitable for the physical systems it touches.

About Rakesh Kumar

Rakesh Kumar is a Professor and John Bardeen Faculty Scholar in Computer Engineering at Illinois and author of The Chip Age. He studies chips and computer systems, co-founded chip companies, advised companies and governments, and developed technologies now used in phones, tablets, and computers.

You can follow Rakesh Kumar's work on his University of Illinois webpage and read The Chip Age.

Marcin Klimaszewski: The Product Owner View of Great Scrum Masters in Agile Teams

In this episode, we refer to Design Thinking, Product Build Day, and The Mom Test by Rob Fitzpatrick.

The Great Product Owner: A Scrum Master Who Knows When to Step Into Product Work

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.

"The skill of a great Scrum Master is being flexible with the role." - Marcin Klimaszewski

Because this is a Product Owner week, Marcin closes the week by describing what great Scrum Masters look like from the product side. The key word is flexibility. A great Scrum Master protects team rhythm and alignment, but also understands when the team needs something outside the textbook process. Marcin shares the example of a product or epic kickoff where the Scrum Master worked with the Product Owner and Product Designer to create a useful workshop. The team did not only hear what was expected. They clarified assumptions, named missing data, discussed whether discovery was needed, and identified risks early. That kind of kickoff can save weeks later because it gives the whole team a shared understanding of what they are trying to deliver and how they need to deliver it. For Product Owners, that Scrum Master is not a process guardian standing aside. They are a partner who notices when product clarity, team alignment, and delivery confidence need help.

Self-reflection Question: Where could you step in this week to help the team clarify product assumptions before sprint execution begins?

The Bad Product Owner: The Scrum Master Anti-Pattern of Staying Inside the Role Description

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.

"Scrum Masters could go to someone else to get inspiration. This flexibility can come from different directions." - Marcin Klimaszewski

The anti-pattern in Marcin's story is the Scrum Master who treats the role description as a boundary instead of a starting point. Product work often contains uncertainty: outdated data, missing discovery, technical blockers, stakeholder tension, or unclear decisions. A Scrum Master does not need to be a product expert, designer, architect, or developer to help. They need to sense the tension and know how to inquire. Vasco gives a simple example: hear tension in a meeting, ask the architect for coffee, and learn what is really blocking the team. Marcin adds that Scrum Masters can learn from their own background and from other specialists, just as therapists use supervisors to think through difficult situations. The lesson for Scrum Masters is practical: flexibility is not improvising randomly. It is knowing when the process is not enough, asking better questions, and helping the team find the conversation that needs to happen.

Self-reflection Question: Are you using the Scrum Master role to create clarity, or to avoid stepping into unclear conversations?

[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 Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

You can also learn more at Product Build Day.

Marcin Klimaszewski: Product Owner Ownership That Gives Agile Teams Real Direction

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.

"Ownership is one of the most important things, and knowing how to hold this ownership." - Marcin Klimaszewski

Marcin defines Product Owner success through ownership. The word is in the title, but in many organizations the role is not actually given the authority, clarity, or support needed to make decisions. A successful Product Owner protects the team from conflicting stakeholder pressure, becomes a reliable decision point, and gives the team a clear sense that product decisions will lead somewhere. Marcin shares a Product Build Day example where a founder entered the day with a clear statement: the prototypes and tests would inform real product direction, not become a fun internal exercise. That clarity changed the team's energy. People knew the work mattered, the decision would affect future sprints, and the Product Owner would own the result. Vasco connects this to Extreme Ownership by Jocko Willink: Product Owners cannot hide behind "someone told me so." They need to own the goal, the trade-offs, and the decisions that guide the team.

Self-reflection Question: Does your team know which product decisions are real decisions, and who owns them?

Featured Retrospective Format for the Week: Silent Notes, Clustering, and Dot Voting

Marcin's favorite retrospective format starts quietly. Everyone writes feedback on sticky notes, online or offline, often anonymously. The notes are then revealed, grouped into similar themes, named by the team, and voted on so the group can select the most important topic to address. The strength of this format is that it gives quieter people room to contribute, makes everyone read what others wrote, and reduces the chance that the loudest voice defines the whole conversation. Vasco adds a useful sanity check: after voting, ask whether anyone sees a better idea on the board that did not get selected. That small pause helps the team guard against groupthink. Marcin's tip: do not use any retrospective format too many times in a row. Change the format to create fresh thinking.

[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 Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

Marcin Klimaszewski: Product Owner Discovery When Agile Stakeholders Want Delivery First

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.

"If I can ship everything by the weekend, what is worth shipping?" - Marcin Klimaszewski

Marcin's current challenge is one many Product Owners recognize immediately: convincing stakeholders to invest time and money in discovery. Everyone says they want to understand the customer, but when discovery becomes real work, the pressure returns to plans, backlogs, and delivery. Marcin points to the Double Diamond design process as a useful way to explain the work. The first diamond explores problems and decides which problem deserves attention. The second diamond explores solutions. Many companies rush into the second diamond and become feature factories. The backlog is already large, stakeholders already have promises, and discovery can feel like more uncertainty instead of progress. Marcin's experiment is to shrink discovery into something stakeholders can tolerate and teams can actually run: Product Build Day, a one-day workshop where people build AI-assisted prototypes, pitch options, and design the sharpest user test for the next day. The larger shift is clear: product development is a search problem, not just a delivery problem.

In this episode, we refer to Design Thinking's Double Diamond and Product Build Day.

Self-reflection Question: How much of your backlog exists because the team is avoiding the uncertainty of discovery?

[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 Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

Marcin Klimaszewski: The Product Owner Lesson From Agile Teams That Forget the User

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.

"The user never wants to log in. That is never the goal of the user." - Marcin Klimaszewski

Marcin describes a pattern he has seen too often: teams speak about users as if the team already knows what users need. In one EdTech example, the obvious solution looked simple from the development side: students should log in. But in a classroom with twenty or thirty students and only forty-five minutes, login was not a neutral feature. A few forgotten passwords, a few typos, and the teacher suddenly became an administrator instead of a teacher. The Product Owner needed the team to see the real problem, not just the technically familiar solution. The eventual answer was simpler for the users: the teacher logged in and shared a code with the students. That gave the product enough identification without stealing classroom time. Marcin connects this to the Sam Walton reminder that the customer is the real boss. For Product Owners and Scrum Masters, the work is not to defend our preferred solution. The work is to keep asking what problem the user is trying to solve.

In this segment, we talk about EdTech and the Sam Walton idea that the customer can fire everyone by spending money somewhere else.

Self-reflection Question: Where is your team solving an internal business problem and calling it a user need?

Featured Book of the Week: The Mom Test by Rob Fitzpatrick

Marcin recommends The Mom Test by Rob Fitzpatrick because it helps product people and Scrum Masters ask better questions. The trap is familiar: we explain our idea, ask whether people like it, and receive polite opinions instead of useful evidence. Marcin points out that better discovery starts with people's real experiences, problems, and past behavior. He also recommends Sprint by Jake Knapp, a practical guide to design sprints and structured product discovery. Sprint helped him see workshops as sequenced decisions toward a larger goal, not ceremonies to follow blindly. The method is useful only when it helps the team learn, align, prototype, test, and decide.

[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 Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

Marcin Klimaszewski: When Product Owner Success Creates Blind Spots for 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.

"I am not the user. That is how I learned how important it is to keep your ego small." - Marcin Klimaszewski

Marcin Klimaszewski started in product as a webmaster, writing HTML and CSS, before discovering UX design through a colleague who became his mentor. That shift changed how he looked at software: not as screens to build, but as problems to understand. In this episode, Marcin shares an EdTech product story where the team had everything a product person could hope for: access to students and teachers, weekly validation, a strong Product Owner, and a confident team. The problem was that success started to distort the team's relationship with the rest of the organization. As the team received positive user testing feedback, they began to see themselves as the best team in the company. From the outside, that confidence looked like arrogance, and critical dependencies with sales, marketing, e-commerce, and payments became harder to manage. The product eventually launched, but never reached the sales targets. For Marcin, the lesson is sharp: user testing is not market testing, and Product Owners need Scrum Masters who help teams stay connected to reality before the market does it for them.

In this episode, we refer to EdTech and Product Build Day.

Self-reflection Question: Where is your team getting positive feedback that may be hiding the real market risk?

[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 Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

Joseph Osei-Kusi: Great Product Owners Bring Customer Problems, Not Just Backlog Items

In this episode, we refer to Product Owner anti-patterns and how Scrum Masters can coach Product Owners without becoming the hidden Product Owner.

The Great Product Owner: Clarity, Courage, and Customer Context

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.

"This product owner gave the team the problem, and not just the solution." - Joseph Osei-Kusi

Joseph describes a great Product Owner who changed the team's dynamic by bringing clarity, courage, and context. Instead of feeding tickets to developers, this Product Owner explained the customer problem, the business outcome, and what success would look like. That gave the team room to think. Developers started asking better questions: What should we build? Is there a simpler way to solve this? Can we test this with a smaller release first? The Product Owner was also clear about what the team was not doing. When urgent stakeholder requests appeared, the question became: Is this more important than the current Sprint Goal? That single question made trade-offs visible. Vasco highlights an important effect: starting with the customer problem creates empathy and brings the Product Owner into the team's problem-solving space.

Self-reflection Question: Does your Product Owner bring your team customer problems to solve, or mostly solutions to implement?

The Bad Product Owner: The Order-Taker Backlog

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.

"When everything is priority one, nothing is truly priority one." - Joseph Osei-Kusi

Joseph's Product Owner anti-pattern is the order-taker PO. This Product Owner cared and worked hard, but had become a pass-through for stakeholder requests. Every request entered the backlog. Everything was urgent. Everything was high priority. The backlog became a storage room for everyone's wishes, and the impact on the team was predictable: weak Sprint Goals, context switching, and developers building features without understanding the outcome behind them. Joseph helped by coaching through questions instead of making decisions for the PO. What problem are we solving? What outcome matters now? What happens if we do not do this right now? What are we willing to say no to? Those questions helped the Product Owner move from taking orders to making decisions, while keeping the Scrum Master out of the hidden Product Owner trap.

Self-reflection Question: What decision-making questions could help your Product Owner say "not now" with more confidence?

[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 Joseph Osei-Kusi

Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.

You can link with Joseph Osei-Kusi on LinkedIn.

Joseph Osei-Kusi: Success for Scrum Masters Is a Team That Improves Without You Driving Every Conversation

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 a team can improve without having me drive every conversation." - Joseph Osei-Kusi

For Joseph, Scrum Master success is not a clean Jira board or perfectly run events. Success shows up when the team becomes more honest, more autonomous, and more able to inspect and adapt without depending on the Scrum Master for every conversation. He looks for small accountability signals: team members raising risks early, developers challenging unclear priorities, people calling out broken working agreements, and retrospectives leading to real experiments. If the Product Owner and developers only talk when the Scrum Master arranges the conversation, the role has become a dependency. Joseph also watches how stakeholders are brought into the improvement loop without letting them take control of the team. The point is to create the right conversations and protect the team's ability to make decisions. For Scrum Masters, the invitation is clear: measure success through team behavior, not through ceremony performance.

Self-reflection Question: If you stepped away for two weeks, which improvement conversations would your team still have without you?

Featured Retrospective Format for the Week: Mad/Sad/Glad Plus One Concrete Experiment

Joseph's favorite retrospective format is Mad/Sad/Glad followed by one concrete experiment. The format helps teams talk about the human experience of the sprint instead of staying at the level of mechanics. What made us mad? What made us sad? What made us glad? But Joseph does not let the team stop at venting. Once the patterns are visible, he asks for one small experiment the team is willing to try in the next sprint. One real experiment has a better chance of changing behavior than ten action items nobody owns. In the next retrospective, the team can inspect whether the experiment helped, whether to continue it, change it, or stop it.

[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 Joseph Osei-Kusi

Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.

You can link with Joseph Osei-Kusi on LinkedIn.

Joseph Osei-Kusi: Helping Agile Managers Move from Control to Enablement

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.

"Their value is not knowing every ticket status. It is creating the conditions where the team can deliver without friction." - Joseph Osei-Kusi

Joseph brings a current challenge he calls the middle management squeeze. As Agile teams become more self-organized, some managers experience autonomy as a loss of control, visibility, or even identity. That fear can show up as more status requests, being copied on every conversation, or stepping back into decisions the team should be making. Joseph does not frame those managers as blockers. He starts with empathy, because managers are often accountable for outcomes while being asked to trust a system they did not help design. The coaching move is to shift the conversation from managing tasks to improving the system. Instead of inspecting every ticket, managers can help with approval delays, conflicting priorities, dependencies, and unclear stakeholder expectations. Vasco and Joseph explore one useful experiment: create intentional contact points where managers can support the team without taking over the backlog or sprint details.

In this episode, we refer to servant leadership and the Scrum Master role in helping managers become enablers of flow, not controllers of tasks.

Self-reflection Question: Which manager around your team may need a clearer, more useful role in the Agile system?

[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 Joseph Osei-Kusi

Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.

You can link with Joseph Osei-Kusi on LinkedIn.

Joseph Osei-Kusi: How Artificial Harmony Silences Agile Teams Before the Real Problems Surface

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.

"Silence can be more dangerous than conflict, because at least with conflict something is being expressed." - Joseph Osei-Kusi

Joseph shares a team story from a high-stakes migration project where the team looked mature on the outside. Meetings were calm. Nobody argued. Plans were accepted quickly. But what looked like alignment was really artificial harmony. Stakeholders brought pressure and proposed solutions, while the team softened their message instead of making risks visible. Over time, that silence created bottlenecks, delayed difficult conversations, increased technical debt, and left the team with fewer options. Joseph learned to treat unusual quietness as data. When a team agrees too quickly, he asks questions like: What would make this plan work? What would make it fail? What concerns are we not saying out loud? The goal is not to create drama. The goal is to make reality visible early, while the team and stakeholders still have room to choose.

In this segment, we talk about artificial harmony and how Scrum Masters can help teams make trade-offs visible before silence becomes expensive.

Self-reflection Question: Where might your team be choosing politeness over useful honesty?

Featured Book of the Week: The Five Dysfunctions of a Team by Patrick Lencioni

Joseph recommends The Five Dysfunctions of a Team by Patrick Lencioni because it helped him see that many team issues are trust problems before they are process problems. Poor planning, quiet retrospectives, weak working agreements, and missed commitments often point to something deeper: people avoiding conflict because the trust is not there. Vasco also mentions The Speed of Trust by Stephen M. R. Covey, a useful companion for understanding the business impact of high-trust versus low-trust environments. For Joseph, these books reinforce a core Scrum Master lesson: teams do not always need another process tweak. Sometimes they need to rebuild trust and learn how to disagree productively.

[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 Joseph Osei-Kusi

Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.

You can link with Joseph Osei-Kusi on LinkedIn.

Joseph Osei-Kusi: When the Jira Board Looked Fine but the Agile Team Was Drained

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.

"Metrics are conversation starters, not the full truth." - Joseph Osei-Kusi

Joseph Osei-Kusi joins us from New York to share a failure from early in his Scrum Master journey, when he became what he calls the "Jira observer Scrum Master." The board looked clean, the metrics looked acceptable, and the tasks appeared to be moving. Underneath that tidy surface, the team was losing energy. People had stopped speaking up, agreement came too quickly, and the real conversations moved outside the meetings. Joseph realized too late that he had been paying more attention to the board than to the people doing the work. The cost was real: two developers left the team. That moment changed how he approached the role. Today, Joseph uses metrics as an invitation to ask better questions: What changed? How does the team feel? What are we not seeing? For Scrum Masters, the warning is simple: a board can look healthy while the human system is already struggling.

In this episode, we refer to psychological safety and how Scrum Masters can use metrics as a doorway into better team conversations.

Self-reflection Question: What quiet signals might your team be sending that do not show up on your Jira board?

[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 Joseph Osei-Kusi

Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.

You can link with Joseph Osei-Kusi on LinkedIn.

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.