Skip to main content
AmigoFish

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product OwnerAudio

Format:
Podcast
New episodes:
Daily
Typical length:
about 15 minutes
Latest episode:
Not rated yet
CosmosOpen at the sourceReport a problemIs this your show? Get a badge

About this show

Every week day, Certified Scrum Master, Agile Coach and business consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!

Covers: software development, agile coaching, scrum, product ownership, team dynamics, agile delivery, artificial intelligence, kanban, remote teams

Show details and episodes come from the publisher's public feed at scrummastertoolbox.libsyn.com. Last updated . Names, artwork and text belong to their publishers.

Recently on this show

Summary of recent episodes, drawn from the publisher's feed.

The Scrum Master Toolbox Podcast is about Scrum and Agile work, with interviews of Scrum Masters and Agile Coaches. Recent episodes cover remote Scrum events turning into team ownership, the Product Owner and Scrum Master partnership, using working agreements to make AI safer, and breaking the permission loop in Agile teams.

Report a problem with this summary

Cosmos

Similar by topic and creator

See the full Cosmos

Similar shows

See all News and Politics shows

Explore more

Episodes

  • BONUS How Network Design Makes Teams Smarter With Damon Centola

    · 43 min

    BONUS: How Network Design Makes Teams Smarter With Damon Centola What if the way your team is connected matters as much as the people on it? Damon Centola, author of Goodthink, joins Vasco Duarte to explain why networks do more than move information: they shape trust, legitimacy, coordination, and creativity. This conversation gives software leaders a practical way to think about AI adoption, Slack, and the conditions for better collective thinking. Networks Are Prisms, Not Pipes "The networks aren't actually pipes, they're prisms." When leaders announce a new tool or practice, the message does not land in a vacuum. People interpret it through colleagues they trust, through the risks they see in changing their work, and through the signals that tell them whether the change is legitimate. Centola explains why a campaign that simply broadcasts information can fail: behavior change needs social reinforcement, not just a clearer message. Build Legitimacy Before Asking for Adoption "It's not just about teaching people facts, it's about getting them to believe and want to believe." For software leaders introducing AI or another new way of working, the useful question is not only how to communicate the change. It is whether people can see peers like them trying it, adapting it to their work, and making it safe to join. Broad bridges between groups help a practice cross from one team into another because people can build trust and confidence together rather than being sold an idea by a broker. Match the Network to the Problem "The kinds of structural solutions that facilitate and answer the coordination challenge would actually undermine the creativity challenge." Fast, highly connected channels can be exactly right when a team needs to coordinate under pressure. They can be harmful when a team needs to explore, because everyone quickly converges on the first promising answer. Centola suggests treating organization design as something fluid: amplify fast coordination when the work calls for it, then create more space and separation when the next challenge is discovery. Slow Down Information to Find Better Ideas "By slowing down the learning process in terms of peer learning, you accelerate the local discovery process." Centola's experiment with data scientists compared fully connected teams with groups organized more like hallways. In the fully connected teams, everyone saw the current best answer and rushed toward it. The hallway networks allowed different approaches to develop for longer; every one of those networks outperformed the fully connected networks across eight competitions. The lesson is not to abandon collaboration, but to protect enough diversity for people to explore beyond the obvious local peak. Design Places for Useful Collisions "We really are these geographic beings. We live in the spaces that are immediately around us." MIT's Building 20 became an unlikely source of creativity because people from unrelated disciplines kept running into one another without being pulled constantly back into their home departments. The same principle applies to digital workplaces. Leaders can ask which connections help people coordinate, which ones create conformity, and where a smaller set of unexpected conversations might give an idea time to grow. Turn Network Research into Better Decisions "All the studies I've ever done are up there, but also all the data, all the scripts, so you can kind of dig in." At the Network Dynamics Group, Centola and his colleagues connect fundamental network research with practical work in organizations, hospitals, and civic life. Their work includes network-based clinical consultation designed to reduce bias and medical errors. For listeners who want to go deeper, the group shares papers, data, and scripts alongside the research. [The Scrum Master Toolbox Podcast Community CTA] About Damon Centola Damon Centola is the Elihu Katz Professor of Communication, Sociology, and Engineering at…

    Not rated yet
  • Scrum Masters Who Build Ownership Instead Of Team Dependency | Paola Elefante

    · 15 min

    Paola Elefante: Scrum Masters Who Build Ownership Instead Of Team Dependency In this episode, we refer to Sprint Goals and Product Owner/Scrum Master collaboration. The Great Scrum Master: Clear Responsibilities, Preparation, And Team Safety 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. "After a year and a half or so of working together, we were even reading each other's mind." - Paola Elefante Paola's great Scrum Master example is Petri, a Scrum Master who prepared before meetings, respected the team's time, and kept discussions focused. He knew when to park a topic, when a story was not refined enough for planning, and how story-level prioritization connected to the roadmap Paola owned. Their collaboration worked because responsibilities were explicit. Petri protected the team's day-to-day focus, removed obstacles, and became the go-to person for detailed team questions. Paola handled external stakeholders, roadmap direction, and feature-level trade-offs. The team knew who to ask, which created safety and reduced friction. Over time, the collaboration became so tight that Paola and Petri anticipated each other's needs. For listeners, the practical lesson is clear: great PO/SM collaboration starts with transparent communication and agreed responsibility areas, then becomes trust through repeated small decisions. Self-reflection Question: Does your team know who owns which kind of decision, or do people have to guess every time they need help? The Bad Scrum Master: Becoming The Owner Of Every Scrum Event 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 whole thing is a shared responsibility, and these are just the tools to make sure that we can deliver on it." - Paola Elefante Paola does not describe a personal bad Scrum Master story. Instead, she names a pitfall Scrum Masters can fall into: making the ceremonies flow so smoothly that the team starts leaning on the Scrum Master to own them. The Scrum Master prepares, facilitates, calls the next person, asks the hard questions, and slowly the team becomes passive. Paola connects this to sprint goals. If the team stays silent, the easy move is for the facilitator or Product Owner to suggest the sprint goal. The better move is to let the silence exist and ask the team what they can promise for the sprint. That moment transfers ownership back where it belongs. Scrum events are not performances delivered by the Scrum Master. They are tools the team uses to take responsibility for delivery. Self-reflection Question: Where are you making an Agile event easier in a way that may also be making the team less responsible? [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 Paola Elefante Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices…

    Not rated yet
  • Sprint Goals And Simple Retrospectives For Agile Product Owner Success | Paola Elefante

    · 15 min

    Paola Elefante: Sprint Goals And Simple Retrospectives For Agile Product Owner Success 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 feel I'm the shield between them and the chaos." - Paola Elefante For Paola, Product Owner success starts with creating clarity for the team. She wants the team to understand what to focus on now, why it matters, what is coming next, and how the work connects to users and company strategy. That clarity shows up in practical signals: sprint scopes changing minimally, the team understanding the reason behind a deadline, and lightweight team check-ins that ask whether people know the current and next focus. Paola also uses Jira analysis, helped by AI tools, to inspect scope movement and sprint goal achievement. The deeper point is that success is not just delivery volume. It is the team's ability to work with confidence. Sprint goals matter because they give the team a sharper sense of what must be closed, what can wait, and where attention should go when reality gets messy. Self-reflection Question: What signal tells you that your team has clarity, not just a list of tickets? Featured Retrospective Format for the Week: Start/Stop/Continue Paola recommends the classic Start/Stop/Continue retrospective because its simplicity lets the team move quickly into the real conversation. She often asks people to fill the board before the meeting, groups related notes into discussion areas, and then uses the live time to focus the conversation. The facilitation challenge is not collecting complaints. It is helping the team identify one concrete step. With engineers, Paola notes, the temptation can be to search for the perfect fix or do nothing. A good retrospective turns that into incremental change: one step in the right direction, not the final answer to every problem. [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 Paola Elefante Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices to the reality of people and teams. You can link with Paola Elefante on LinkedIn.

    Not rated yet
  • Product Discovery In B2B IoT When Agile Teams Have No Analytics | Paola Elefante

    · 21 min

    Paola Elefante: Product Discovery In B2B IoT When Agile Teams Have No Analytics 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. "There is no analytics. So that's a source of information I do not have." - Paola Elefante Paola's current Product Owner challenge comes from a complex B2B IoT context. Her company's software is cloud-based, but often installed in the customer's own cloud, which means she cannot rely on product analytics. The user base is also highly varied: some customers use the UI, some integrate through APIs, and many users are specialized engineers working in very different domains, from smart metering to industrial IoT. Paola tried targeted interviews around firmware updates, deliberately avoiding product demos and asking customers how they worked today. The result was useful, but also messy: the interviews exposed different roles, different use cases, different levels of expertise, and few obvious patterns. In this coaching conversation, Vasco suggests taking another step back: treat technical experts simply as users trying to get a job done. Instead of starting from personas or features, explore motivations, anxieties, and the business context behind the task. In this episode, we refer to Jobs To Be Done and user research. Self-reflection Question: When your users are highly technical, are you still asking what they are trying to accomplish before asking how they use the product? [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 Paola Elefante Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices to the reality of people and teams. You can link with Paola Elefante on LinkedIn.

    Not rated yet
  • Turning Silent Remote Scrum Events Into Agile Team Ownership | Paola Elefante

    · 15 min

    Paola Elefante: Turning Silent Remote Scrum Events Into Agile Team Ownership 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 Scrum events should be ceremonies of ownership of the team." - Paola Elefante When Paola joined a fully remote team, she found a group that had been productive but disengaged. The team had gone several months without a Product Owner, another colleague had been carrying the role on top of other work, and the Scrum events had become quiet. Planning and daily conversations often felt like Paola and the architect talking while the rest of the team waited. She did not try to redesign everything at once. She first copied the existing format, observed, and then started with small changes that shifted responsibility back to the team. Cameras on helped create accountability. Rotating daily facilitation helped even more. Whoever appeared last in Jira's random order became the next day's facilitator, and people began adding their own personality to the meeting. What looked tiny changed the energy: the daily was no longer something served to the team, but something the team owned together. In this segment, we talk about remote work and team ownership. Self-reflection Question: What is one Scrum event your team attends but does not yet own? Featured Book of the Week: Dare to Lead by Brené Brown Paola recommends Dare to Lead: Brave Work. Tough Conversations. Whole Hearts. by Brené Brown, not because it is a product management manual, but because Product Owners spend so much of their time in relationship-heavy work. As one former colleague told her, a Product Owner spends a lot of time saying no. The real skill is saying no while preserving the relationship with stakeholders, protecting the team, and keeping product boundaries clear. For Paola, Brené Brown's research-backed work on vulnerability, empathy, and leadership helps Product Owners build the self-awareness and confidence needed to hold those boundaries without creating hostility. [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 Paola Elefante Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices to the reality of people and teams. You can link with Paola Elefante on LinkedIn.

    Not rated yet
  • The Product Owner And Scrum Master Partnership That Protects Agile Teams | Paola Elefante

    · 12 min

    Paola Elefante: The Product Owner And Scrum Master Partnership That Protects 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 were defending the team's peace from the external disturbances." - Paola Elefante Paola Elefante opens the week from an unusual angle: she could not point to a Scrum Master failure story because the Scrum Master she worked with set such a high bar. Instead, she explains what made that collaboration work. The Product Owner and Scrum Master had a clear shared goal: protect the team's focus. The Scrum Master handled day-to-day obstacles, story-level questions, and the team's operational rhythm. Paola handled roadmap priorities, feature-level decisions, stakeholder negotiation, and strategic context. Because they kept each other updated on priorities, deadlines, and product direction, the Scrum Master could make autonomous decisions close to the team without creating confusion. Paola also shares her own onboarding practice: observe first, meet every team member, ask what they expect from her role, and use those patterns to shape her interventions. For Scrum Masters, this episode is a reminder that great PO/SM collaboration is not role theory. It is explicit agreements, visible responsibility boundaries, and continuous communication. Self-reflection Question: Where does your team still lose energy because people are not sure whether to ask the Product Owner or the Scrum Master? [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 Paola Elefante Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices to the reality of people and teams. You can link with Paola Elefante on LinkedIn.

    Not rated yet
  • The Product Owner Who Commits Before the Team Can Think | Rajveer Prasad

    · 13 min

    Rajveer Prasad: The Product Owner Who Commits Before the Team Can Think In this episode, we refer to product discovery, user acceptance testing, and REST APIs. The Great Product Owner: Market Knowledge Without Intrusion 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. "They have the knowledge, they are not intrusive with that knowledge." - Rajveer Prasad Rajveer has seen strong Product Owners combine market understanding, discovery discipline, and technical awareness without taking control away from the team. Great Product Owners understand the product market, run product discovery and hypothesis cycles, and bring capabilities to the team only after doing the groundwork on value and importance. They also understand enough about the technology to follow the conversation when developers talk about APIs or architecture, but they do not use that knowledge to dictate the solution. Instead, they stay with the "what" and let the team work through the "how." Rajveer also values Product Owners who participate in retrospectives and sizing sessions, challenge the team to think better, and let the team learn through its own cycles. Self-reflection Question: Where could your Product Owner's technical knowledge help the team think better without taking ownership away from them? The Bad Product Owner: Client Promises That Cut Testing 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. "Don't give a date yet. We are not sure. Let's take this back to the team." - Rajveer Prasad The anti-pattern Rajveer highlights is the client-facing Product Owner who commits too early. In his example, the Product Owner had technical acumen and good intentions, but when the client pushed for a better timeline, he shortened UAT, reduced integration time, ignored technical debt, and left the team to absorb the consequences. From the outside, this Product Owner looked successful because he got commitments and the organization rewarded that behavior. Under the hood, the team struggled. Rajveer's advice is to first understand the Product Owner's perspective and align around the same objective: helping the client win. Then get closer to the conversations where commitments are made. Rajveer became a sounding board, joined key cadences, and helped the Product Owner replace instant dates with a better habit: take the request back to the team, include the tech lead, and return with a commitment the team could actually hold. Self-reflection Question: What commitment habit do you need to help your Product Owner change before it damages the 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 Rajveer Prasad Our guest today is Rajveer Prasad, founder of OAKKTREEUNII. He's spent years helping aspiring and working project managers and Scrum Masters break into IT delivery — and grow once they're there — through real projects, real interview prep, and real accountability. He's mentored hundreds through career changes most people call impossible. Welcome, Rajveer You can link with Rajveer…

    Not rated yet
  • Success for Scrum Masters Is the Team's Life After You Leave | Rajveer Prasad

    · 12 min

    Rajveer Prasad: Success for Scrum Masters Is the Team's Life After You Leave 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 you have not helped your team move from point A to point B positively, you are just doing part of the job." - Rajveer Prasad Rajveer defines success for Scrum Masters through the change they leave behind in the lives of the people they serve. Delivery outcomes matter, and he names lead time as a useful end-to-end metric, but he warns that numbers alone miss the deeper work. For Rajveer, success shows up in relationship signals: whether people want to have lunch with you, whether they trust you enough to help in a rare crunch without being forced, and whether they still call you after you leave the organization. Those signals matter because Scrum Masters often come from outside the technical team and must earn a place in the system. The job is to help people move from point A to point B, not only in output, but also in work-life balance, skills, confidence, and the quality of collaboration across the whole team, including the Product Owner. Self-reflection Question: If you left your team next month, what evidence would show that their day-to-day life improved because you were there? Featured Retrospective Format for the Week: Sailboat Retrospective Rajveer's preferred retrospective is the Sailboat format because it helps teams move beyond sprint details and talk about the system they operate in. He uses it to explore what is pushing the team forward, what is anchoring them, where the risks are, and how the team feels. For Rajveer, the format works because it "conditions you for a conversation" and creates space to discuss patterns, behaviors, and ways of working instead of only reviewing tasks. [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 Rajveer Prasad Our guest today is Rajveer Prasad, founder of OAKKTREEUNII. He's spent years helping aspiring and working project managers and Scrum Masters break into IT delivery — and grow once they're there — through real projects, real interview prep, and real accountability. He's mentored hundreds through career changes most people call impossible. Welcome, Rajveer You can link with Rajveer Prasad on LinkedIn.

    Not rated yet
  • Using Scrum Master Working Agreements to Make AI Safer | Rajveer Prasad

    · 16 min

    Rajveer Prasad: Using Scrum Master Working Agreements to Make AI Safer 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. "AI can put garbage in a very good wrapping and give it to you, and you're none the wiser." - Rajveer Prasad Rajveer brings a current challenge from his own work with AI: the false sense of achievement that comes from getting a polished output before the work is truly safe, scalable, or responsible. As a non-developer building AI-supported systems, he found that an agent can quickly produce something that appears to work, while missing security, architecture, testing, or cost implications. The coaching conversation turns toward something Scrum Masters know well: working agreements. Rajveer started defining roles, values, principles, and rules for the agent, treating it like a team member that needs clear expectations. He asks the AI to explain decisions in a way a Scrum Master can understand, captures lessons when something goes wrong, and plans more before building. The surprise is that AI work mirrors team coaching: set agreements, run small experiments, inspect the results, update the system, and avoid rushing into output just because the tool can move fast. In this episode, we refer to working agreements, red-green-refactor, Ollama, and AI agents. Self-reflection Question: What working agreements would make your AI experiments safer before you scale them? [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 Rajveer Prasad Our guest today is Rajveer Prasad, founder of OAKKTREEUNII. He's spent years helping aspiring and working project managers and Scrum Masters break into IT delivery — and grow once they're there — through real projects, real interview prep, and real accountability. He's mentored hundreds through career changes most people call impossible. Welcome, Rajveer You can link with Rajveer Prasad on LinkedIn.

    Not rated yet
  • The Agile Team That Turned Overtime Into a Quality Problem | Rajveer Prasad

    · 13 min

    Rajveer Prasad: The Agile Team That Turned Overtime Into a Quality 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. "Working harder and working longer is not helping anyone. It's just making what we do more difficult and complex." - Rajveer Prasad Rajveer worked with a retail organization moving into SAP HANA, with teams spread across geographies and cultures. The team wanted to help, so they worked evenings, weekends, and extra hours to keep commitments alive. At first, the organization did not demand that behavior, but once it became visible, it became the new normal. The downstream effect was predictable: bad planning, overcommitment, reduced testing, skipped regression, failed integrations, rework, and a rising defect rate. Rajveer gathered data to show the cause and effect, then worked first with leadership because expectations had already been formed outside the team. Once stakeholders understood that the "faster" approach was degrading quality, Rajveer brought the data to the team and created a stricter operating routine. The team needed slack, a five-day working rhythm, and permission to say no so they could improve quality instead of competing against themselves. In this segment, we talk about SAP HANA, technical debt, and sustainable pace. Self-reflection Question: Where is your team using extra hours to hide a planning or quality problem? Featured Book of the Week: The Goal by Eliyahu M. Goldratt Rajveer has read and listened to The Goal by Eliyahu M. Goldratt many times, and each pass gives him a new angle on bottlenecks, flow, and the theory of constraints. For him, the book is foundational because it teaches Scrum Masters to look beyond local effort and see how the system shapes outcomes. As Rajveer puts it, "Every time I'm going through the book, I'm thinking slightly different." [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 Rajveer Prasad Our guest today is Rajveer Prasad, founder of OAKKTREEUNII. He's spent years helping aspiring and working project managers and Scrum Masters break into IT delivery — and grow once they're there — through real projects, real interview prep, and real accountability. He's mentored hundreds through career changes most people call impossible. Welcome, Rajveer You can link with Rajveer Prasad on LinkedIn.

    Not rated yet
  • When Delivery Pressure Pulls Scrum Masters Into the Details | Rajveer Prasad

    · 14 min

    Rajveer Prasad: When Delivery Pressure Pulls Scrum Masters Into the Details 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. "Failures are expected no matter when and where you are." - Rajveer Prasad Rajveer Prasad did not plan to become a Scrum Master. He studied hospitality management and expected to build a career as a chef, but the travel and hospitality industry froze after 9/11. A survival job led him into a call-center environment, then American Express, and eventually into delivery work and Scrum training. In this episode, Rajveer shares a failure from a new product introduction where he was brought in as a consultant, expected to run the team, and slowly pulled into delivery management. The milestone plan looked reasonable, but customer collaboration was weak, dependencies were unclear, and Rajveer found himself operating at a 50-foot view when he needed to step back. The turning point came from a client-side manager who gave direct feedback without turning the situation into a personal judgment. That support helped Rajveer move from firefighting to orchestration, rebuild structure, and treat the problem as a system to improve. In this episode, we refer to new product introduction and systems thinking. Self-reflection Question: When delivery pressure rises, do you move closer to the details, or do you step back far enough to see the 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 Rajveer Prasad Our guest today is Rajveer Prasad, founder of OAKKTREEUNII. He's spent years helping aspiring and working project managers and Scrum Masters break into IT delivery — and grow once they're there — through real projects, real interview prep, and real accountability. He's mentored hundreds through career changes most people call impossible. Welcome, Rajveer You can link with Rajveer Prasad on LinkedIn.

    Not rated yet
  • BONUS Breaking the Permission Loop in Agile Teams With Tara Scott

    · 29 min

    BONUS: Breaking the Permission Loop in Agile Teams In this BONUS episode, we explore why teams often wait for permission even when they already have skill, tools, and good ideas. Tara Scott, executive, product, and culture coach and author of Breaking the Permission Loop, explains how agency starts with noticing our own reactions, building alignment, and practicing small moments of self-trust. When a Compliment Becomes a Detour "You don't really feel like you can say no. So I said yes." Tara starts with a startup story many Scrum Masters and product leaders will recognize. She was building momentum with user research when a CEO redirected her into a data science initiative that sounded urgent, but did not answer the core product question: do people actually use this product? The request was framed as a compliment, and that made it harder to challenge. Tara's point is practical: sometimes the permission loop begins in the small space between our concern and the automatic yes that comes out before we have understood the tradeoff. Slow Down Before the Yes "Sometimes no isn't even no. It's just not right now or give me more context." For Tara, the first move is observation. Before a team can change a pattern, people need to notice what happens inside them when pressure rises: defensiveness, shame, blame, justification, or the urge to please. Tara connects this to The Responsibility Process, a practice for recognizing when we are below the line and bringing attention back to our own behavior. In a team setting, this is not about blaming ourselves for everything. It is about giving ourselves enough room to ask a better question before committing to work we do not believe in. Permission Loops Are Patterns We Can Interrupt "For me, a permission loop is there's different opportunities within those loops where we can step in and say, this could be a really good time to break this." Tara chose the word loop because the pattern repeats until someone interrupts it. Teams say, "it is what it is," decisions wait for a manager, and people move through the same script because it feels familiar. The useful part is that loops also create openings. A meeting, a question, a moment of discomfort, or a request for one more thing can become the cue to pause and run a small experiment. The goal is not dramatic confrontation. It is a calmer, clearer way to step into the moment with evidence, context, and a suggestion. Healthy Alignment Is Different From Waiting for Permission "It is validate, communicate, confirm." Tara makes an important distinction between acts of authorization and permission-based behavior. In software teams, some decisions need security, architecture, compliance, or dependency alignment. That is real. The permission loop starts when people ask for approval for things nobody can actually give them, such as self-trust, courage, or the right to raise a concern. Tara's working pattern is simple: validate what needs to happen, communicate it clearly, and confirm that the right people are aligned. That connects closely with intent-based leadership from David Marquet's Turn the Ship Around!: say what you intend to do, check alignment, then move. Autonomy Without Direction Can Leave Teams Lost "I was told I have total freedom, but to do what?" Tara challenges a common agile assumption: autonomy alone will not solve the problem. She describes a team that had been told they had freedom, but no shared goal. Leadership and developers blamed each other, and everyone was using different language for success. Without direction and explicit alignment, autonomy becomes another source of confusion. That is why Tara shifts the focus toward agency: enough trust in yourself to speak, enough confidence to offer a path forward, and enough humility to be wrong and still keep working with others. Atomic Habits for Breaking the Loop "We have to start where we start and start small." Tara connects her six-week practice to James Clear's Atomic…

    Not rated yet
  • BONUS AI as the Third Perspective for Agile Delivery With Rohini Prava

    · 25 min

    BONUS: AI as the Third Perspective for Agile Delivery AI is already changing how agile delivery managers, Scrum Masters, and software teams handle the day-to-day work of delivery. In this BONUS episode, Rohini Prava shares how her team moved from experimenting with Cursor to using AI for practical work: bug analysis, ticket preparation, test planning, reporting, and reducing painful meetings. From Java Developer to Agile Delivery Manager "I see a good fit. And one of the scrum masters was going on holiday and I got the opportunity, I tried it, I liked it and I think I did well because I was given the role." Rohini started her career as a Java developer in India, then moved into people management and delivery-focused work before relocating to the UK. A temporary opportunity to cover for a Scrum Master opened the door to a new direction. That experience eventually led her into the Agile Delivery Manager role, where she now leads a distributed team delivering insurance solutions. When AI Became Part of the Work "It stopped being a curiosity when I integrated it in my work. And the fun started." For Rohini, the shift happened when her company gave access to Cursor, a developer-focused AI tool. Instead of treating it as something only developers could use, she tested it against real delivery work. The first meaningful example came before a retrospective-style meeting on a difficult project. By giving AI access to project data from Jira Service Management and Azure DevOps, she generated an eight-page analysis in under an hour. The result was a more factual, constructive conversation instead of a meeting based on memory, frustration, or blame. AI Across the Delivery Team "It really helps the devs to investigate issues, going through the legacy code, because some of the technology they may not even be familiar with." Rohini describes AI adoption as early, practical, and team-specific. Her team connected Cursor with Azure DevOps through the Model Context Protocol concept, giving the tool useful context about tickets and code. Developers use it to explore legacy code, brainstorm solutions, and support pair-programming-style thinking. Business analysts use it to draft tickets and acceptance criteria. QA team members use it to strengthen test plans and coverage. Rohini uses it for reporting, meeting preparation, email drafting, and pulling useful data from delivery events. Measuring Impact Beyond Speed "If you're just simply going with, oh, I've used it for quickly getting the reports, but we need to sit and look at, do we really need that report?" Rohini is careful not to frame AI only as a speed tool. Her point is that teams need to measure whether AI changes anything that matters. One personal example was timesheet review: a weekly task that used to take five to six hours. By building a small tool to help with review, she reduced that work to about one hour. The lesson for agile practitioners is direct: start by looking at the work that consumes time, then ask whether AI actually reduces waste or simply creates more output. Using AI to Reduce Meetings and Improve Quality "AI showed us that you can do less meetings, but just focus on one or two actions and see what change you can bring." One of the strongest team examples came from long root cause analysis meetings. The team had many bugs and spent 60 to 90 minutes with 11 or 12 people trying to analyze them. The meetings produced long action lists, but those lists were hard to turn into focused improvements. Rohini gave AI six months of bug data and asked for the most painful patterns. The suggestion was simple: QA slippage was high, and the team needed an "escape reason" field to understand why bugs were missed before reaching customers or UAT. That small change helped the team move from broad discussion to focused learning about test plan gaps and test coverage. The Risks: Over-Reliance, Overuse, and Governance "We don't have to automate everything just because we have…

    Not rated yet
  • BONUS AI Makes Starting Work Easy, But Flow Still Finishes It With Liz Rettig

    · 35 min

    BONUS: AI Makes Starting Work Easy, But Flow Still Finishes It AI is changing software teams, but Liz Rettig brings the conversation back to flow, strategy, and the discipline of finishing. In this BONUS episode, Vasco and Liz explore how Scrum Masters can use AI to make policies visible, help teams manage WIP, support Product Owners, and keep the organization focused on valuable slices instead of faster output alone. From Anthropology To Kanban And AI "As a Scrum Master, you're an anthropologist because you're watching people and you're recording how they are working." Liz starts with her path from anthropology to Scrum Mastering, agile coaching, and professional Kanban training. That background matters because her work has always been about observing how people interact with systems. AI did not replace that skill. It made the system easier to see. In one client engagement, a team adopting an agentic framework also needed agile ways of working around that new capability. Liz saw that AI could help teams reach forecasting, strategy, and board-reading conversations much faster than before, as long as the human system was still designed with intent. AI Helps Teams See Flow Earlier "This is a tool that can help me get teams further quicker than ever before." Liz describes AI as a practical accelerator for visibility. Instead of spending months collecting and cleaning data by hand, teams can use AI-enabled tools to surface the information already living in Jira, code repositories, customer feedback, and flow metrics systems. That changes the coaching conversation. Scrum Masters and agile coaches no longer need to persuade teams that the data could exist. They can bring the data into the room and ask what it means for the way work is moving. Starting Is Free, Finishing Is Still The Discipline "Starting is free with AI, and I get into that pickle all the time too." The central warning from Liz is simple: AI makes it easier to start work, but it does not automatically make teams finish the right work. She connects this directly to Kanban practices: limit work in progress, watch aging work, make policies explicit, and help the team focus on moving existing items before pulling more into the system. Liz has used AI hooks, skills, commands, and team rules to remind people when they are about to break their own policies. The point is not to block people blindly. The point is to make the tradeoff visible, capture why the team chose to break a WIP limit, and bring that evidence into retrospectives. Scrum Masters Can Put Team Policies Into The AI System "Everybody has the ability to run it, and I expect everybody on the team to run it." Liz does not keep the AI-enabled flow tools as a coaching black box. She works with teams to define their policies, then embeds those policies into the tools the team uses every day. A daily board walk can highlight aging work, blocked items, WIP issues, and the topics worth discussing in the daily review of flow or daily Scrum. This shifts the Scrum Master's work away from repeating reminders and toward helping the team interpret what they see. AI becomes a way to make the team's agreements visible and repeatable. Leaders Still Need Outcome Conversations "Everybody wants more faster." Liz is clear that many organizations begin AI adoption with an output goal: more stories, more work items, more projects, less time. One client moved from roughly 75 items per month to around 400. That created a new and more important question: are those 400 items connected to the value the organization actually wants? Liz explains how AI helped reorganize work around objectives, key results, epics, and delivery data so leadership could see how throughput was being spent. The useful conversation was not "how much more did we do?" It was "how much of our capacity went to strategy, bugs, maintenance, and the work we said mattered?" The Constraint Moves Left "The constraint that we're finding is having the right work…

    Not rated yet
  • BONUS AI Is Not Just Typing Faster With Marcus Hammarberg

    · 46 min

    BONUS: AI Is Not Just Typing Faster With Marcus Hammarberg In this BONUS episode, Vasco Duarte and Marcus Hammarberg explore what changes when AI agents move from writing small functions to creating whole features, running through tickets, and even improving their own instructions. The conversation keeps coming back to a simple but difficult question: if agents make software delivery faster, what should humans use that speed for? When the Agent Writes the Feature "What I realized was that the agent could now write the code from a prompt that I gave it, and it was good enough that I didn't have to touch a lot of it." Marcus starts with the moment that changed his own practice: in December 2025, he used an AI agent to build a feature for a flow metrics app based on Jira change logs. Before that, AI coding felt like asking for small functions and then cleaning up the result. This time, the agent could take a feature-level prompt and produce something useful. That shifted the question from "can AI help me type code?" to "what happens to planning, quality, and ownership when implementation becomes dramatically faster?" Slowing Down Enough To Think "You end up not only not having seen the code, but not maybe even know what you wrote." Vasco connects Marcus' experience to an earlier episode where Marcus had to learn to program after breaking his hand. Back then, the lesson was that typing was not the bottleneck. Thinking was. Now AI has made "typing" even faster, and Marcus warns that this creates a new danger: teams can approve suggestions, specs, and generated code without really understanding the intent they gave the system. In that world, slowing down becomes part of the human job. From Developer To Robot Instructor "With the robot in place, what are you doing now? You're giving the robot instructions, and you're verifying the result. This is exactly what we are doing with the AI now." After rereading The Goal, Marcus started to see AI agents as the software equivalent of factory robots. A welder used to make the weld directly. With robots, the human writes instructions and verifies the result. Software is entering the same kind of transition. The open question is uncomfortable: can someone reliably verify AI-generated software without being a strong developer first? Marcus does not pretend to know the answer, and that uncertainty is part of the value of the conversation. Harnesses, Feedback Loops, And Agent Teams "A really good harness should also have some deterministic checks in the feedback mechanism." Marcus describes teams experimenting with "lights-out" agent factories: a project manager agent receives intent, delegates to sub-agents, the agents move work across a Kanban board, and they even run retrospectives to improve their own instructions. That sounds futuristic, but Marcus brings it back to Agile basics. If prompts and guardrails are non-deterministic, then the harness needs deterministic feedback: tests, linting rules, functional checks, non-functional checks, architectural rules, and explicit slices of work that humans can test before moving on. The lesson is not to abandon Agile. It is to make feedback loops more concrete because the work is moving faster. The Human Side Of Losing The Easy Wins "I don't feel the same kind of ownership when I have prompted my way to a good application as I did when I wrote it." The episode also names a quieter transformation: developers may lose the small dopamine hits that came from solving tiny coding problems, seeing tests pass, and refactoring by hand. If agents handle the easy work, humans may be left with harder, slower problems: intent, architecture, product value, safety, and trade-offs. That changes the emotional shape of development. Marcus and Vasco explore what happens when a developer is no longer only a coder, but the manager of an agent team. Stop Measuring AI By Output "Awesome, are you selling percentages?" Marcus brings the conversation back to Theory…

    Not rated yet
  • BONUS AI in the SDLC Puts Customer Feedback Before Faster Typing With David Mantica

    · 35 min

    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…

    Not rated yet
  • BONUS The Scrum Master's AI Prompt Library With Joshua McDonald

    · 30 min

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

    Not rated yet
  • Great Product Owners Start the Conversation Instead of Becoming the Boss | Kaloyan Chalakov

    · 13 min

    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,…

    Not rated yet
  • Building Scrum Master Success Around Trust and Unspoken Leaders | Kaloyan Chalakov

    · 15 min

    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.

    Not rated yet
  • Coaching Organizations to Challenge the Beliefs Behind Agile Pressure | Kaloyan Chalakov

    · 19 min

    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.

    Not rated yet