Advertise on podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches

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.

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.

Oluyomi Emmanuel: When Agile Team Trust Breaks Before the Scrum Master Acts 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.   "Once that trust is broken, everything else, nothing else matters." - Oluyomi Emmanuel   Oluyomi Emmanuel started his Scrum Master journey after a strategic move toward Agile ways of working changed his project coordinator role into something deeper: helping people communicate when the answers were unclear. In this episode, he shares a hard lesson from a newly formed software team of eight people, where tension between a tech lead and a new developer first appeared in GitHub pull request comments. There were sarcastic replies, cameras switched off during the daily standup, and a growing distance when the team worked in the same office. Oluyomi initially treated it as a normal forming-stage conflict and waited for the team environment to absorb the tension. By the time the tech lead escalated concerns to the developer's line manager, trust had already deteriorated. A facilitated feedback session produced an improvement plan, but the developer experienced the feedback as judgment rather than support and left the team less than a month later. Oluyomi's lesson was clear: a Scrum Master needs to name trust concerns early, first in one-on-ones, then together, before the relationship becomes too damaged to repair.   In this episode, we refer to psychological safety, conflict resolution, and team trust.   Self-reflection Question: What early sign of broken trust have you noticed but not yet named with your team?   [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.