Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: Conflict Is the Yellow Brick Road to Success — How Embracing Conflict Transforms Teams and Leaders In this bonus episode, we explore why fear, conflict, and courage sit at the heart of true agility with Dan Tocchini, a leadership catalyst who has spent over four decades helping teams at organizations like ESPN, Disney, and Homeboy Industries break through the human barriers to high performance. Dan shares powerful stories and practical wisdom on how leaders can embrace conflict as a generative force, build trust through vulnerability, and restructure their teams for genuine agility. The Power of Vulnerability in Leadership "I'd rather have it on an honest basis, where she knows what I'm thinking, what I'm aiming at, and we're shoulder to shoulder, not head to head."   Dan's career-defining moment came when he told a CFO at ESPN — while he was competing against McKinsey for the same contract — that she was the problem behind her department's 75% turnover rate. Rather than sugarcoating or deflecting, Dan chose vulnerability and honesty, even at the risk of losing the contract. This radical transparency became his superpower. The CFO hired him, and within six months, turnover dropped to 15%. Dan stayed with ESPN for eight years. The lesson for Scrum Masters and leaders: you can only truly connect with someone if you're willing to be honest, even when it might cost you. Listening for Openings, Not Outcomes "Most people listen for outcomes. I listen for openings."   Dan draws a critical distinction between chasing outcomes and discovering openings. When faced with an angry car buyer who felt ripped off, Dan didn't try to close the sale. Instead, he leaned into the conflict, acknowledged the customer's perspective, and opened all the books. The result? A sale with 17% margin — above the dealership average — because the customer chose the price himself. For leaders, this means detaching from your desired outcome and focusing on understanding the opening in front of you. That shift builds trust and often produces better results than pushing for what you want. Why Team Drama Is a Distraction Strategy "Whenever there's drama, it's because people don't want you to see something."   Drama in teams happens because people are siloed, and they silo because they don't trust each other. They share only the information that serves their position without jeopardizing their role. The drama itself is a distraction — like a child throwing a tantrum so you'll forget what they did wrong. Dan's approach: ask three questions. What are they committed to causing? How much of that are they producing? And what's the story between the two? The problem is never the problem — the problem is how you think about the problem. Restructuring for Agility: A Restaurant Case Study "Your way of being needs to be bigger than the structure."   Dan illustrates agile restructuring through a top-25 restaurant in Boise where the general manager flows seamlessly between roles — bussing tables, coordinating with the kitchen, and leading the team — without ever pulling rank. The secret? He grounds his team before every shift with genuine connection, shared meals, and open dialogue. When he gives direction, people move — not from fear, but from respect. Structure alone won't solve problems; it only organizes them so you can see them better. Leaders must be committed to what the structure is designed to accomplish, altering it in motion when needed. Conflict as a Generative Force "What you're not willing to face will eventually defeat you."   Dan's core philosophy centers on embracing conflict rather than avoiding it. When people face conflict, they either seek comfort by avoiding it or realize what's at stake and find a way through. The Stoic principle "the obstacle is the way" applies: to find the path, you must hug the cactus and pull the problem close. In relationships — whether marriage, team, or client — breakdowns should deepen intimacy and trust. Dan reports that 90% of the time, authentically facing into mistakes with clients deepens relationships and keeps contracts alive. What Keeps Dan Going After Four Decades "People love to accomplish things they didn't think they could do. To me, that's exciting."   After more than 40 years in this work, Dan remains energized by working with people to accomplish challenges they initially thought impossible. He describes his work as akin to family — that same depth of connection and shared purpose. His one-liner: "We turn leadership into leadership." It sparks curiosity and opens conversations about what real leadership transformation looks like. About Dan Tocchini   Dan Tocchini has spent 35+ years working with leadership teams across the spectrum — from ESPN to nonprofits like Defy Ventures — helping them evolve from functional to fully alive. His work focuses on the human systems that make agile succeed… or silently kill it.   You can find out more about Dan and his leadership training programs at TakeNewGround.com.

Juliana Stepanova: Why "I'll Just Do It Myself" Is the Most Expensive PO Shortcut 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.   In this episode, we refer to previous discussions about team collaboration and Product Owner patterns. The Great Product Owner: Opening Up to the Team for Solutions "The PO who's not sitting and saying 'I know how it's right, I will solve it by myself,' but coming and saying 'Hey, let's think all together'—that's what gives very, very speed-up development into becoming a great PO." - Juliana Stepanova   Juliana describes the Product Owners she considers truly great as those who bring their challenges to the team rather than solving everything alone. Her example features a PO who was invited to recurring release meetings that consumed one and a half to two hours every two weeks—30 people in a room, largely a waste of time. Instead of suffering in silence or trying to fix it alone, this PO approached the team: "Hey guys, I have these meetings, and they're useless for me. How can we deal with that?" The team collaborated with the Scrum Master to explore multiple options.  Together, they developed a streamlined, semi-automatic system that reduced the process to 10 minutes without requiring anyone to sit in a room. This solution was so effective that it was eventually adopted across the entire company, eliminating countless hours of wasted meetings. The key insight: great POs see themselves as part of the team, not above it. They're open to solutions from anyone and understand that collaboration—not individual genius—drives real improvements.   Self-reflection Question: When facing challenges that seem outside the team's domain, do you bring them to the team for collaborative problem-solving, or do you try to solve them alone? The Bad Product Owner: The Loner Who Does Everyone's Job "To make it quicker, I will skip asking the designer, I will directly put it by myself. I learned how to design five years ago. But afterwards, it's neglecting the whole team—you don't take into account the UX, and actually you need to rework." - Juliana Stepanova   The anti-pattern Juliana sees most frequently is the "loner" PO—someone who takes on other roles to move faster. The classic example: a PO who bypasses the UX/UI designer because "I learned design five years ago, I'll just do it myself." This behavior seems efficient in the moment but creates multiple problems. It disrespects the expertise of team members, undermines the collaborative nature of agile development, and almost inevitably leads to rework when the shortcuts create quality gaps.  Juliana points out this isn't unique to POs—developers sometimes bypass testers for the same "efficiency" reasons. The solution isn't punishment but cultural reinforcement: helping people see the value of professional work, encouraging communication and openness, and building respect for each role's contribution. The key principle: if someone hasn't asked for help, don't assume they need yours. Focus on your own job, and offer assistance only when invited or when you explicitly ask "Do you need help?"   Self-reflection Question: When have you taken on someone else's role because it seemed faster, and what was the real cost of that shortcut?   [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 Juliana Stepanova   Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.   You can link with Juliana Stepanova on LinkedIn.   You can also follow Juliana on Twitter.

Juliana Stepanova: When a Former Skeptic Calls to Say "Now I Know What You Did" — Defining Scrum Master 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.   "Juliana, now I know what you did that time. It was so amazing work. Sometimes the work of the Scrum Master, you cannot measure it in real numbers, because the work of the Scrum Master is dependent on the persons who are working with the team." - Juliana Stepanova   Juliana shares a story that captures the often invisible nature of Scrum Master success. For a year and a half, she worked with a distributed team across Europe, and one colleague in her office would repeatedly ask—half joking, half serious—"Juliana, what do you do here? Why are you getting a salary? I don't see any improvements."  Eight months after that colleague moved to another company, he called her with a revelation: working in a team without effective Scrum Mastering made him finally understand the value she had created. This delayed recognition highlights a fundamental challenge: Scrum Master success often can't be measured in real numbers because it depends on enabling others. Juliana's practical approach is to set three main focus areas every three months, aligned with team and company needs.  She tracks concrete progress—like implementing a Definition of Done across multiple teams—and measures whether specific goals are achieved. She even asks in job interviews: "How will you measure my success in three or six months?" Without this intentional focus and self-measurement, she says, "it's truly hard to see what you're really doing."   Self-reflection Question: What three focus areas would you choose for the next three months, and how would you know you've succeeded in each? Featured Retrospective Format for the Week: Wedding Retro Juliana recommends the Wedding Retro format from Retromat, and when she mentions the name, people immediately smile—which is exactly the point. The format uses the traditional wedding saying "something old, something new, something borrowed, something blue" to structure reflection: Something Old represents practices that are working and should continue; Something New covers areas for improvement or experimentation; Something Borrowed invites the team to identify ideas from other teams or departments worth adopting; and Something Blue addresses blockers, risks, and issues.  Juliana loves this format because the playful framing creates positive emotions from the start, disarming tension and making people more open to genuine reflection. "If you laugh at the start of the retrospective," she explains, "you're ready for a much better retrospective than if you're tense and anxious." She uses this exercise "all over the time," even outside her Scrum Master work.   [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 Juliana Stepanova   Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.   You can link with Juliana Stepanova on LinkedIn.   You can also follow Juliana on Twitter.

Juliana Stepanova: Trust Over Escalation — A Patient Approach to Difficult PO Relationships 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 team still believes it could be solved with proper communication to the PO. My idea is to really try, in a supportive way, to build trust, to encourage communication, and to come to the solution as a team altogether. This is like a win-win situation." - Juliana Stepanova   Juliana brings a challenge that many Scrum Masters will recognize: a Product Owner who doesn't want to be coached and whose behaviors are undermining Scrum rituals. The situation is complicated by organizational structure—the Scrum Master reports to the people department while the PO reports to the product department, creating misaligned directions with no common leadership thread.  The PO arrives at refinement meetings unprepared, writing user stories on the spot while eight team members sit idle for hours. When Juliana explores the root cause, she discovers the PO is genuinely overwhelmed with responsibilities outside the team. But here's the twist: this newly promoted PO is proud of the role and resistant to accepting help, preferring to say "just wait, I will manage it."  Rather than escalating—which Juliana notes would damage trust for years or potentially lose the PO entirely—she advocates for a patient, collaborative approach. The experiment she designs focuses on engaging more deeply with the PO's activities to understand which tasks could be delegated or eliminated, while continuing to build trust through support rather than confrontation. The team maintains hope that the PO will eventually accept help, choosing persistence over escalation.   In this segment, we talk about coaching Product Owners and building trust.   Self-reflection Question: When facing a resistant stakeholder, do you default to escalation, or do you invest in building the trust that enables genuine collaboration?   [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 Juliana Stepanova   Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.   You can link with Juliana Stepanova on LinkedIn.   You can also follow Juliana on Twitter.

Juliana Stepanova: The Slippery Slope — How Small Compromises Lead Teams to Abandon Scrum Entirely 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 it like once, you think it's okay. But it starts to change our mindset in the way that these rules, these frameworks could be changed. And with the small stuff that it's not correct, within half a year, Scrum will not work at all." - Juliana Stepanova   Juliana describes a pattern she witnessed in an experienced seven-person development team that had practiced Scrum for years. It began innocuously: the daily standup stretched from 15 to 30 minutes because the team was larger. Then came the skipped retrospectives during release phases—"we don't have time today." Each compromise seemed reasonable in isolation, but together they formed a slippery slope that eventually dismantled the entire framework. The root cause often lies outside the team: misaligned Scrum rituals across multiple teams, company-wide meetings that override sprint events, and pressure from management to prioritize immediate fires over process discipline. Once the brain accepts that "we can skip it for a good reason," finding the next good reason becomes easier and easier. Juliana emphasizes a crucial distinction: teams that actively choose Scrum—those who approach management saying "we want to try this"—naturally protect the framework. They understand its value from personal conviction. When Scrum is imposed rather than chosen, the team lacks the intrinsic motivation to defend it against organizational pressure, making the slippery slope almost inevitable.   In this segment, we talk about the challenges of organizational alignment and protecting Scrum events.   Self-reflection Question: What small compromises has your team made to the Scrum framework, and are they leading you toward a slippery slope where the entire process may eventually be abandoned? Featured Book of the Week: Startup, Scaleup, Screwup by Jurgen Appelo Juliana recommends Startup, Scaleup, Screwup by Jurgen Appelo as her go-to resource for Scrum Masters and Agile Coaches. The book contains 42 tools designed to accelerate business growth, presented in accessible chapters that cover the most essential knowledge for agile practitioners. What sets this book apart for Juliana is its scope: it addresses not just team-level concerns but company-wide perspectives. "Sometimes Scrum Masters don't pay so much attention to the company level or between departments," she explains. "In this book, you'll find normal tools which you can apply all over the company, not only for the team." She uses it constantly for inspiration and recommends reading it at least once—though she returns to it repeatedly for reference.   [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 Juliana Stepanova   Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.   You can link with Juliana Stepanova on LinkedIn.   You can also follow Juliana on Twitter.

Juliana Stepanova: The 90-Minute Retrospective Disaster That Taught Me Servant Leadership Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It's not my job to find the points to improve. My job is to help the team find them, to interact their communication, to start thinking about the improvements, and not pushing them into my exercises." - Juliana Stepanova   Juliana shares a humbling experience from her first year as a Scrum Master that transformed how she approaches facilitation. She had meticulously prepared what she believed was a brilliant 90-minute retrospective—carefully designed exercises, content tailored to the sprint, everything by the book. Yet when she asked the team for feedback at the end, they delivered a crushing verdict: "It was the worst retro ever." The disconnect wasn't about the quality of preparation but about whose perspective drove the design. Juliana had crafted the session based on her observations and assumptions about what the team needed, rather than asking them what they actually wanted to discuss.  This experience crystallized a fundamental insight about servant leadership: the difference between leading and servant leading. Today, Juliana prepares at least twice as many tools and exercises as she needs for any workshop, ready to pivot based on the room's energy and the team's expressed needs. She opens sessions with questions about expectations, aligning with the team's mood while setting appropriate boundaries. The failure taught her that even the most carefully prepared facilitation can miss the mark when it doesn't serve what the team actually needs in that moment.   Self-reflection Question: When was the last time you asked your team what they wanted from a retrospective before you designed it, and how might their input change your approach?   [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 Juliana Stepanova   Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.   You can link with Juliana Stepanova on LinkedIn.   You can also follow Juliana on Twitter.  

Agile in Construction: The Product Owner Role in Construction—Voice of the Customer Across Every Phase With Felipe Engineer-Manriquez 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. In this episode, we refer to Extreme Ownership by Jocko Willink and Team of Teams by General Stanley McChrystal, as well as our Agile in Construction episodes. The Great Product Owner: Bringing the Voice of the Customer to Every Decision "I want you to think like the owner, and bring that to the team meetings, because we can't have the owner in the meetings with us." - Felipe Engineer-Manriquez   The Product Owner role in construction is radically different from software—and Felipe has learned to find it in unexpected places. When Jeff Sutherland told his class to "tear up your business cards" because only three roles exist (Developer, Scrum Master, Product Owner), construction people were confused. Felipe's approach: ask the team who can bring the voice of the customer. Sometimes it's the superintendent, interfacing daily with charge nurses and doctors in a working hospital. Sometimes it's a project executive. Rarely, it's the project manager. The key is that the PO role changes across phases because every day in construction is brand new—the building is physically taking shape. Felipe studied military leadership in Extreme Ownership and Team of Teams and found strong product owner culture—leaders who brought customer voice to cell-level teams against hierarchical norms. Great product owners speak in terms of what the customer wants, transforming how teams prioritize and align naturally.   Self-reflection Question: Who on your team currently embodies the voice of the customer, and how might you coach them to bring that perspective more explicitly to every team interaction? The Bad Product Owner: When Gut Decisions Override Value "Value is a beneficial transformation of materials, information, or a combination of both. Let's not do things that don't transform information or materials." - Felipe Engineer-Manriquez   Felipe shares a powerful anti-pattern: owners who make gut decisions based on past project trauma without checking if conditions are still true. On a $100 million project, an owner repeatedly introduces work that doesn't add value—reacting to bad things that happened on previous projects, even when those conditions no longer exist. The result? Teams waste time on activities that don't transform materials or information. Felipe teaches teams an industrial engineering definition of value: "a beneficial transformation of materials, information, or a combination of both." Status updates that don't change behavior are waste. Markings on metal decking that will be buried under 5 inches of concrete are waste. The fix? Make the backlog visible and ask: "Where should we zipper this in so it has the most impact on transforming materials or information?" For construction, prioritization always comes back to getting the right materials in place, one time, at the right time—not touching things twice.   Self-reflection Question: When stakeholders introduce work based on past experiences, how do you help them evaluate whether those conditions still apply to the current situation?   [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 Felipe Engineer-Manriquez   Felipe Engineer-Manriquez is a best-selling author, international speaker, and host of The EBFC Show. A force in Lean and Agile, he helps teams build faster with less effort. Felipe trains and coaches changemakers worldwide—and wrote Construction Scrum to make work easier, better, and faster for everyone.   You can link with Felipe Engineer-Manriquez on LinkedIn.   You can also find Felipe at thefelipe.bio.link, check out The EBFC Show podcast, and join the EBFC Scrum Community of Practice.  

Agile in Construction: Team Happiness as the True Measure of Scrum Master Success in Construction With Felipe Engineer-Manriquez 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 teams that are having fun and are light-hearted, making jokes—these are high-performing teams almost 99% of the time. But the teams that are overly sarcastic or too quiet? They're burning out." - Felipe Engineer-Manriquez   Felipe offers a refreshingly human definition of success for Scrum Masters: team happiness. After years of traumatic experiences in construction—days when he pounded his steering wheel in frustration during his commute—Felipe developed what he calls being a "human thermometer." He can sense a team's emotional state within 5 minutes of being with them. His proxy for success is a simple Likert scale of 1-5: 5 is Nirvana (working at Google with massages), and 1 is wanting to jump out the window. Felipe emphasizes that most people in construction internalize stress and push it down, so you have to ask directly. When he asked an estimator this question, the man quietly admitted he was at a 2—ready to walk away. Without asking, Felipe would never have known. The key insight: schedule improvements happen as teams move closer to a 5. And the foundation of it all? Understanding. "People do not have an overt need to be loved," Felipe shares from his Scrum training. "They have an overt need to be understood." A successful Scrum Master meddles appropriately, runs toward problems, and focuses on understanding teammates before trying to implement change.   Self-reflection Question: If you asked each of your team members to rate their happiness from 1-5 today, what do you think they would say, and what would you learn that you don't currently know? Featured Retrospective Format for the Week: Start/Stop/Keep Felipe's favorite retrospective format is Start/Stop/Keep—but his approach to introducing it is what makes the difference. He connects it to something construction teams already know: the post-mortem. He explains the morbid origin of the term (surgeons standing around a dead patient discussing what went wrong) to emphasize the seriousness of learning. Then he reframes the retrospective as a recurring post-mortem—a "lessons learned" cycle. Start: What should we begin doing that will make things better? Stop: What should we no longer do that doesn't add value? Keep: What good things are we doing that we want to maintain? Felipe uses silent brainstorming so everyone has time to think, then makes responses visible on a whiteboard or digital display. The cadence scales with sprint length—45 minutes for a week, 2 hours for two weeks, half a day for a month. His current team committed to monthly retrospectives and pre-writes their Start/Stop/Keep items, making the facilitated session efficient and focused.   [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 Felipe Engineer-Manriquez   Felipe Engineer-Manriquez is a best-selling author, international speaker, and host of The EBFC Show. A force in Lean and Agile, he helps teams build faster with less effort. Felipe trains and coaches changemakers worldwide—and wrote Construction Scrum to make work easier, better, and faster for everyone.   You can link with Felipe Engineer-Manriquez on LinkedIn.   You can also find Felipe at thefelipe.bio.link, check out The EBFC Show podcast, and join the EBFC Scrum Community of Practice.

Agile in Construction: The DOWNTIME Strategy—Eliminating Waste Before Adding Process With Felipe Engineer-Manriquez 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.   "My first rule is that I will do no harm. And if something goes wrong, I will take full responsibility with leadership. My neck is literally on the line." - Felipe Engineer-Manriquez   Felipe shares his change strategy for introducing Lean and Agile into construction projects, and it starts with an unexpected principle borrowed from Hippocrates: do no harm. He explicitly tells teams this promise, putting his neck on the line to build trust. But the real magic happens in what comes next: instead of adding new processes, Felipe first helps teams stop doing things. Using the DOWNTIME acronym (Defects, Overproduction, Waiting, Transportation, Inventory, Motion, Excess processing), he identifies wasteful activities that don't add value. In construction, 60-80% of every dollar doesn't add value from the customer's perspective—compared to manufacturing (above 50% value) or agriculture (90% value). Felipe's approach: eliminate waste first to create excess capacity, then introduce new processes. On a project that was 2 years behind schedule with lawyers already engaged, he spent just 5 minutes with the team defining a visible milestone goal on a whiteboard. Two weeks later, they met their schedule and improved by 4 days—the first time ever. The superintendent said, "Never in the entire time I've worked here have we ever met a schedule commitment." The secret? Free up capacity before adding anything new.   In this episode, we refer to the 8 wastes video by Orbus and WIP limits.   Self-reflection Question: Before introducing your next process improvement, what wasteful activity could you help your team stop doing to free up the capacity they need to embrace change?   [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 Felipe Engineer-Manriquez   Felipe Engineer-Manriquez is a best-selling author, international speaker, and host of The EBFC Show. A force in Lean and Agile, he helps teams build faster with less effort. Felipe trains and coaches changemakers worldwide—and wrote Construction Scrum to make work easier, better, and faster for everyone.   You can link with Felipe Engineer-Manriquez on LinkedIn.   You can also find Felipe at thefelipe.bio.link, check out The EBFC Show podcast, and join the EBFC Scrum Community of Practice.

Agile in Construction: Over-Commitment and Silence—The Deadly Duo Destroying Your Teams With Felipe Engineer-Manriquez 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 don't think people are bad. They don't self-destruct because they're bad. What I do see is people getting crushed in terribly bad systems." - Felipe Engineer-Manriquez   Felipe shares a powerful insight about team dysfunction: teams don't self-destruct because of bad people—they get crushed by broken systems. On a hospital construction project, he witnessed a dangerous pattern: over-commitment coupled with silence. People would commit to pouring concrete on Thursday when there wasn't even rebar in place—a physical impossibility. But psychological safety was so low that no one could say the emperor had no clothes. Felipe's approach? Ask obvious questions that break the pattern. "Don't you need this so you can do that?" This simple question, framed with verb-noun phrases, surfaces what cannot be spoken. He positions himself as "just a simple, dumb general contractor" who doesn't understand—creating safety for others to speak truth. The turning point comes when you slow down, make work visible, and allow people to say no. As Felipe puts it: "For real accountability, if people are not allowed to say no, then they actually can't make a real promise." Silence is not alignment, and saying yes in low-trust environments is actually hiding from accountability.   In this segment, we talk about psychological safety and systems thinking in team dynamics.   Self-reflection Question: When you see a team over-committing to impossible deadlines, what question could you ask that surfaces the truth without putting individuals at risk? Featured Book of the Week: The Goal by Eliyahu Goldratt Felipe chose The Goal by Eliyahu Goldratt as the most transformative book of his early lean career. He describes it as "the number one game changer"—a fictional story that teaches the Theory of Constraints in a way you can internalize. The famous "Herbie story" within the book illustrates how helping the slowest part of a process speeds up the entire system. Felipe emphasizes that Theory of Constraints is often skipped in Scrum training when classes run out of time, leaving many credentialed Scrum Masters without this essential knowledge. He uses these principles daily with the Last Planner System in construction—creating visual boards that look like Gantt charts (because construction loves schedules) but function like Scrum boards with days of the week instead of "to do, doing, done."   [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 Felipe Engineer-Manriquez   Felipe Engineer-Manriquez is a best-selling author, international speaker, and host of The EBFC Show. A force in Lean and Agile, he helps teams build faster with less effort. Felipe trains and coaches changemakers worldwide—and wrote Construction Scrum to make work easier, better, and faster for everyone.   You can link with Felipe Engineer-Manriquez on LinkedIn.   You can also find Felipe at thefelipe.bio.link, check out The EBFC Show podcast, and join the EBFC Scrum Community of Practice.  

Agile in Construction: Stop Teaching and Start Doing—The Secret to Agile Adoption in Construction With Felipe Engineer-Manriquez 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 forgot a couple key things. Number one, they don't have the enthusiasm and love for these new ways of working like I do because they didn't understand the problem that they were in." - Felipe Engineer-Manriquez   Felipe shares a powerful failure story from his early days adopting Lean and Agile in construction. After discovering Jeff Sutherland's "Red Book" and experiencing incredible results using Scrum with his 4-year-old son on a weekend project, he was eager to bring these methods to his construction team. The problem? He immediately went into teaching mode. His boss Nate and the rest of the team wanted nothing to do with Scrum—they Googled it, saw it was "a software thing," and shut down completely. This is what Felipe now calls the "Not Invented Here Syndrome"—people resist ideas that don't originate from their domain. The breakthrough came when Felipe stopped teaching and started doing. He calls it the "ninja Scrum approach"—embodying the processes and tools without labeling them, making work visible, and delivering results.  When he managed $25 million worth of scopes using these methods silently, one project manager named Tom stopped him and said, "We've never come to a project where people held their promises." Within a year, even his resistant boss Nate acknowledged the transformation in a post-mortem review. The lesson: don't teach until people pull for the teaching.   In this episode, we refer to NoEstimates and Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland.   Self-reflection Question: When you introduce new practices to a team, do you wait until they pull for the teaching, or do you default to explaining before they've seen the value?   [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 Felipe Engineer-Manriquez   Felipe Engineer-Manriquez is a best-selling author, international speaker, and host of The EBFC Show. A force in Lean and Agile, he helps teams build faster with less effort. Felipe trains and coaches changemakers worldwide—and wrote Construction Scrum to make work easier, better, and faster for everyone.   You can link with Felipe Engineer-Manriquez on LinkedIn.   You can also find Felipe at thefelipe.bio.link, check out The EBFC Show podcast, and join the EBFC Scrum Community of Practice.  

BONUS: Thinking Like an Architect in the Age of AI-Assisted Coding How can engineers leverage AI to write better code—and think like architects to build systems that truly scale? In this episode, Brian Childress, a CTO and software architect with over 15 years of experience, shares hard-won lessons from teams using AI coding tools daily, and explains why the real challenge isn't just writing code—it's designing systems that scale with users, features, and teams. The Complexity Trap: When AI Multiplies Our Problems "Most engineering projects and software engineers themselves lean more towards complexity, and I find that that complexity really is multiplied when we bring in the power of AI and its ability to write just tons and tons and tons of code."   Brian has observed a troubling pattern: AI tools can generate deeply nested components with complex data flows that technically work but are nearly impossible to understand or maintain. When teams don't guide AI through architectural decisions, they end up with code that becomes "a little too complex for us to understand what is actually going on here." The speed at which AI produces code makes understanding the underlying problem even more critical—we can solve problems quickly, but we must ensure we're solving them the right way. In this segment, we mention our longer AI Assisted Coding podcast series. Check that out for further insights and different perspectives on how our software community is learning to make better use of AI Assisted Coding tools.  Vibe Coding Has Its Place—But Know Its Limits "Vibe coding is incredibly powerful for designers and product owners who want to prompt until they get something that really demonstrates what they're trying to do."   Brian sees value across the entire spectrum from vibe coding to architect-driven development. Vibe coding allows teams to move from wireframes and Figma prototypes to actual working code much faster, enabling quicker validation with real customers. The key distinction is knowing when to use each approach:   Vibe coding works well for rapid prototyping and testing whether something has value Architect thinking becomes essential when building production systems that need to scale and be maintained What Does "Thinking Like an Architect" Actually Mean? "When I'm thinking more like an architect, I'm thinking more around how bigger components, higher level components start to fit together."   The architect mindset shifts focus from "how do I work within a framework" to "what is the problem I'm really solving?" Brian emphasizes that technology is actually the easiest part of what engineers do—you can Google or AI your way to a solution. The harder work is ensuring that the solution addresses the real customer need. An architect asks: How can I simplify? How can I explain this to someone else, technical or non-technical? The better you can explain it, the better you understand it. AI as Your Thought Partner "What it really forces us to do is to be able to explain ourselves better. I find most software engineers will hide behind complexity because they don't understand the problem."   Brian uses AI as a collaborative thought partner rather than just a code generator. He explains the problem, shares his thought process, and then strategizes back and forth—looking for questions that challenge his thinking. This approach forces engineers to communicate clearly instead of hiding behind technical jargon. The AI becomes like having a colleague with an enormous corpus of knowledge who can see solutions you might never have encountered in your career. Simplicity Through Four Shapes "I basically use four shapes to be able to diagram anything, and if I can't do that, then we still have too much complexity. It's a square, a triangle, a circle, and a line."   When helping colleagues shift from code-writing to architect-thinking, Brian insists on dead simplicity. If you can diagram a system—from customer-facing problems down to code component breakdowns, data flow, and integrations—using only these four basic shapes, you've reached true understanding. This simplification creates that "light bulb moment" where engineers suddenly get it and can translate understanding into code while in flow state. Making AI Work Culturally: Leading by Example "For me as a leader, as a CTO, I need to show my team this is how I'm using it, this is where I'm messing up with it, showing that it's okay."   Brian addresses the cultural challenge head-on: mid-level and senior engineers often resist AI tools, fearing job displacement or having to support "AI slop." His approach is to frame AI as a new tool to learn—just like Google and Stack Overflow were in years past—rather than a threat. He openly shares his experiments, including failures, demonstrating that it's acceptable to laugh at garbage code while learning from how it was generated. The Guardrails That Make AI Safe "If we have all of that—the guardrails, the ability to test, automation—then AI just helps us to create the code in the right way, following our coding standards."   The same engineering practices that protect against human errors protect against AI mistakes: automated testing, deployment guardrails, coding standards, and code review. Brian sees an opportunity for AI to help teams finally accomplish what they've always wanted but never had time for—comprehensive documentation and thorough automated test suites. Looking Ahead: More Architects, More Experiments, More Failures "I'm going to see more engineers acting like architects, more engineers thinking in ways of how do I construct this system, how do I move data around, how do I scale."   Brian's 2-3 year prediction: engineers will increasingly think architecturally because AI removes the need to deeply understand framework nuances. We'll have more time for safeguards, automated testing, and documentation. But expect both sides of the spectrum to intensify—more engineers embracing AI tools, and more resistance and high-profile failures from CEOs vibe-coding production apps into security incidents. Resources for Learning Brian recommends staying current through YouTube channels focused on AI and developer tools. His top recommendations for developer-focused AI content:   IndyDevDan NetworkChuck AI Jason   His broader advice: experiment with everything, document what you learn as you go, and be willing to fail publicly. The engineers who thrive will be those actively experimenting and learning.   About Brian Childress   Brian Childress is a CTO and software architect with over 15 years of experience working across highly regulated industries including healthcare, finance, and consumer SaaS products. He brings a non-traditional background to technology leadership, having built his expertise through dedication and continuous learning rather than formal computer science education. Brian is passionate about helping engineers think architecturally and leverage AI tools effectively while maintaining simplicity in system design.   You can link with Brian Childress on LinkedIn.

Cristina Cranga: Coaching Product Owners From Output Obsession to Value Conversations 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.   In this episode, we refer to the work of Esko Kilpi on conversations and episodes on Nonviolent Communication (NVC) on the podcast. The Great Product Owner: A People Person Who Clarifies Before Deciding   "He was comfortable saying 'I don't know yet. What do you think?' It was a bi-directional conversation, not just one-way." - Cristina Cranga   The best Product Owner Cristina worked with was fundamentally a people person and a leader—human skills, not just hard skills. What made him exceptional was his approach to conversation: he started by clarifying the problem first, then decided. By doing this, he separated requests from decisions and made trade-offs explicit.  He was comfortable admitting uncertainty, asking "What do you think?" and engaging the team in co-creation rather than issuing directives. Cristina emphasizes that between the PO and Scrum Master, there's a special bond—a strong leadership partnership that teams look to as a reference. She highlights the concept of "ask more, say less": when you ask questions, you collect information that leads to better, more validated decisions.  The communication process, as outlined in Nonviolent Communication by Marshall Rosenberg, has four components: observation, feelings, needs, and requests. Great POs embody this by treating uncertainty as part of their job, engaging teams more deeply, and connecting work to value rather than just output.   Self-reflection Question: How often does your Product Owner ask "What do you think?" and what would change if they separated requests from decisions more explicitly? The Bad Product Owner: Output Obsession and the Velocity Trap "Success is measured by how much is delivered, not what changes. Teams get faster, but not smarter." - Cristina Cranga   The worst Product Owner anti-pattern Cristina has witnessed is output obsession—measuring success by how much is delivered rather than what actually changes for users or the business. When velocity replaces outcomes as the primary metric, teams get faster but not smarter. Faster doesn't equal smarter. This anti-pattern is particularly dangerous in an AI-accelerated environment where delivery speed is no longer a constraint. The challenge for practitioners is shifting this mindset. The strongest POs make different choices: they own their decisions at the team level, make decisions explicit, treat uncertainty as part of the job, and connect work to value. When POs break free from output obsession, the results are powerful: faster alignment, no decision hallucinations, more engaged teams willing to experiment, and genuine connection between work and value.   In this segment, we refer to Nonviolent Communication by Marshall Rosenberg.   Self-reflection Question: If you removed velocity from your team's dashboard tomorrow, what conversations would emerge about actual value delivered?   [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 Cristina Cranga   Human, Innovation enthusiast with a curious mind always learning new things. Sometimes a dreamer and a restless soul. Her mission in life is helping People thrive. She has a background in psychology and an experience in supporting the implementation of multiple IT software projects in complex digital eco-systems with different technologies at international level. How these two worlds can shape a professional? Let's discover it ...   You can link with Cristina Cranga on LinkedIn.

Cristina Cranga: Decision Quality as the True Measure of Scrum Master Effectiveness 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 Scrum Master is successful when teams make better decisions, faster, with clear trade-offs—everything else is a side effect, not the job." - Cristina Cranga   Cristina offers a refreshingly clear definition of Scrum Master success for 2026: increasing the team's decision quality under accelerating change. She emphasizes that success as a term changes over time, and what mattered in previous years may not be what matters now. It's not about ceremony fluency or even making yourself unnecessary—those are side effects. The core of success is helping teams navigate complexity and AI-driven acceleration by making better decisions faster with explicit trade-offs.  Cristina describes this as an evolution from a "mechanic" role—focused on ceremonies, flow, and structure—to a strategic role. The Scrum Master elevates into a leader of team systems and human behaviors, possibly even becoming an AI integration enabler. This requires reskilling and upskilling as the environment changes. Her prompt for self-reflection: How can you orient your execution of the Scrum Master role more towards strategic aspects, focusing on decision quality as the opposite of decision hallucination?   Self-reflection Question: What would change in your daily work if you measured your success by the quality of decisions your team makes rather than the smoothness of your ceremonies? Featured Retrospective Format for the Week: Start/Stop/Continue Cristina advocates for simplicity in retrospectives, choosing the classic Start/Stop/Continue format. But she emphasizes that the format itself is secondary—what matters is the environment you create and the outcomes you achieve. Her two key conditions for any retrospective: an actionable plan and a simple conversational approach.  She challenges Scrum Masters to focus on the "how" rather than the "what"—how do you hold the space? How do you hold the silence? How do you approach disagreements? The power of Start/Stop/Continue lies in its simplicity, which frees facilitators to focus on creating psychological safety. Cristina also warns against the instinct to take ownership of action items yourself—instead, delegate to team members so they own their problems and become more committed to finding solutions.   [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 Cristina Cranga   Human, Innovation enthusiast with a curious mind always learning new things. Sometimes a dreamer and a restless soul. Her mission in life is helping People thrive. She has a background in psychology and an experience in supporting the implementation of multiple IT software projects in complex digital eco-systems with different technologies at international level. How these two worlds can shape a professional? Let's discover it ...   You can link with Cristina Cranga on LinkedIn.

Cristina Cranga: Why Speed Without Value Creates Chaos in AI-Accelerated 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.   "When output becomes cheap, value becomes harder to see. AI is amplifying this risk." - Cristina Cranga   Cristina brings a timely challenge to the table: how do Scrum Masters stay focused on value when AI tools are accelerating delivery to unprecedented speeds? Teams are delivering faster than ever—AI provides code, tests, documentation, even backlog items—but speed is no longer the constraint. The real challenge is meaning. Teams struggle to explain why their work matters to users or the business.  Cristina frames this as a shift from "delivery" as the primary keyword to "value." She suggests that Scrum Masters are evolving from facilitators of flow to protectors of intent—what she playfully calls "strategic guardians of the value chain" or even "value masters." Together with Vasco, they explore experiment ideas around building clarity of value cycles with product owners, bringing signals of value into earlier backlog work, and helping teams validate faster, not just deliver more.  The key insight: in an AI-accelerated world, the Scrum Master's role becomes more strategic, focused on ensuring teams make better decisions with clear trade-offs rather than just executing ceremonies.   Self-reflection Question: How might you help your product owner build a "clarity of value" cycle that tests ideas before they reach the development 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 Cristina Cranga   Human, Innovation enthusiast with a curious mind always learning new things. Sometimes a dreamer and a restless soul. Her mission in life is helping People thrive. She has a background in psychology and an experience in supporting the implementation of multiple IT software projects in complex digital eco-systems with different technologies at international level. How these two worlds can shape a professional? Let's discover it ...   You can link with Cristina Cranga on LinkedIn.  

Cristina Cranga: Why Nice Teams Still Fail and the Power of Honest Conversations 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.   "Sometimes you can change people by only listening to them. Not giving advice—don't become an advice monster." - Cristina Cranga   Cristina shares her experience of sensing that something was off with a team but being unable to pinpoint exactly what it was. Instead of jumping to conclusions, she paused, reflected, and created an intervention plan centered on one thing: starting honest conversations. Through one-on-one discussions with team members, she discovered that the problem wasn't performance or process—it was something deeper.  Expectations weren't aligned with reality, and frustration stemmed from a company culture that didn't offer psychological safety. Cristina introduces the concept of the "advice monster"—someone who constantly tells others what they should do rather than simply listening. She emphasizes that as Scrum Masters, we need to recognize the three layers of our influence: control, influence, and no control.  Even when we can't solve problems, being present and listening can create profound change. The key is self-awareness of our own vulnerability as humans and compassion for others who might be at 80% or 10% of their mental health and energy on any given day.   In this segment, we talk about the importance of psychological safety and active listening in team dynamics.   Self-reflection Question: How often do you enter conversations with the intention of truly understanding rather than solving, and what might you discover if you listened more and advised less? Featured Book of the Week: The Fearless Organization by Amy Edmondson Cristina chose The Fearless Organization by Amy Edmondson as her most influential book because it explains what Scrum Masters see every day but struggle to name. The book provides a mental model for why teams don't speak up and how to influence behavior without forcing it. As Cristina puts it: "She explains why nice teams still fail. Silence is not always alignment and politeness—most of the time, it's distrust." The book repositions the Scrum Master role from someone focused on ceremonies to someone who creates the conditions for psychological safety. It also explains why process alone doesn't fix everything and helps Scrum Masters measure what really matters in a 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 Cristina Cranga   Human, Innovation enthusiast with a curious mind always learning new things. Sometimes a dreamer and a restless soul. Her mission in life is helping People thrive. She has a background in psychology and an experience in supporting the implementation of multiple IT software projects in complex digital eco-systems with different technologies at international level. How these two worlds can shape a professional? Let's discover it ...   You can link with Cristina Cranga on LinkedIn.

Cristina Cranga: When Teams Stop Testing Reality and Fall Into Decision Hallucinations 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.   "Over time, what I notice is that teams stop testing reality. They optimize execution around constraints that might no longer exist." - Cristina Cranga   Cristina introduces a powerful concept she calls "decision hallucinations"—the perception of constraints and boundaries that aren't actually real or present. In her experience working with teams in complex matrix environments, she noticed a troubling pattern: team members would say things like "we can't change this because it's already decided" or "the priority comes from the top level" without ever verifying these assumptions.  The impact on team behavior was significant—teams stopped asking questions, stopped having conversations with stakeholders, and began operating within perceived limitations rather than actual ones. Cristina emphasizes that as Agile practitioners, our work isn't just about ceremonies and metrics—it's about supporting and facilitating decision processes.  When she encouraged teams to ask better questions like "Is this an assumption-based decision or an explicit shared choice?", something beautiful happened: options reappeared, conversations changed, and teams realized they were constrained by perception rather than reality. She uses the famous duck vs. rabbit optical illusion from psychology to illustrate how our brains can only see one reality at a time, making the case that we must constantly test our view of reality through continuous conversations with stakeholders.   In this episode, we refer to the work of Esko Kilpi on conversations and the duck vs rabbit image from psychology.   Self-reflection Question: When was the last time you challenged an assumption your team operates under, and what did you discover when you tested that reality?   [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 Cristina Cranga   Human, Innovation enthusiast with a curious mind always learning new things. Sometimes a dreamer and a restless soul. Her mission in life is helping People thrive. She has a background in psychology and an experience in supporting the implementation of multiple IT software projects in complex digital eco-systems with different technologies at international level. How these two worlds can shape a professional? Let's discover it ...   You can link with Cristina Cranga on LinkedIn.

Mohini Kissoon: The One Question That Transforms Messengers Into Product Owners The Great Product Owner: The Calm Navigator Who Shields 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.   "He said "no" often, but he did it with such clarity that people respected it. It's not just no—it's giving the reason why." - Mohini Kissoon   Mohini has had the privilege of working with many great Product Owners, but one stood out for his calm demeanor and ability to navigate complex situations. Whatever stakeholders threw at him, he remained professional and calm—and critically, he never transferred that pressure onto the team. He had built strong relationships with stakeholders and was the go-to person who commanded respect across the organization.  When stakeholders demanded features that didn't align with team goals, he would acknowledge the request, explain the trade-offs, and offer to revisit it once the current direction was validated. He said no often, but with such clarity and reasoning that people respected his decisions.  This Product Owner also shielded the team from ad hoc requests, handling stakeholder bypass attempts so developers could maintain focus. He would only bring truly urgent items—like compliance issues—directly to the team.  With his helicopter view, he understood how incoming work would impact different stakeholders and parts of the business. Most importantly, he was a good listener who gave the team space to grow and experiment while challenging them constructively.   Self-reflection Question: When you work with your Product Owner, do they shield the team from chaos or pass it through unfiltered—and how might you help them develop that protective capability? The Bad Product Owner: The Messenger Who Couldn't Say No 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 the team would ask 'why are we building this?' the answer would be 'because sales asked for it.' There was no triaging, no challenging stakeholders—just saying yes." - Mohini Kissoon   Mohini shares a story about a Product Owner who appeared to be doing everything right on paper: attending ceremonies, responding to questions, being present for the team, and working closely with stakeholders. But the team was constantly frustrated with scope creep, and the root cause was that this Product Owner was operating as a messenger, not a decision maker. She would bring requests from stakeholders directly into the backlog with no prioritization based on value and no pushback.  Major new work would appear at sprint planning that hadn't been discussed during backlog refinement. The team was committing to 100 story points but only completing 40, with items constantly carrying over.  When Mohini was brought in to help, she asked one simple question that changed everything: "What is the vision for your product?" The Product Owner couldn't answer—because nobody had ever asked her before.  Mohini ran a product vision workshop with her and key stakeholders, created a one-page strategy identifying target users, core problems, and success metrics, and established a working agreement that backlog items must align with identified goals. She also introduced prioritization sessions involving stakeholders. The transformation came when the Product Owner finally felt equipped to say no with informed reasoning.   Self-reflection Question: Does your Product Owner have a clear product vision they can articulate, and if not, what workshop or conversation could you facilitate to help them discover 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 Mohini Kissoon   Mohini is an Agility Lead with over eight years of experience as a Scrum Master. She is passionate about building high-performing, self-managing teams that delight customers. Mohini improves flow and collaboration across systems, meets teams where they are, and co-creates environments enabling adaptability, meaningful interactions, and continuous improvement and learning.   You can link with Mohini Kissoon on LinkedIn.

Mohini Kissoon: The Language Test That Reveals True 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.   "When I see my team taking ownership of their work, taking ownership of the Scrum events, asking questions, challenging each other constructively without waiting for me—that's when I know I've done my job." - Mohini Kissoon   Mohini defines success for Scrum Masters through three distinct lenses. First, she looks for teams that take ownership—of their work, of the Scrum events, of asking questions and challenging each other constructively without waiting for her to intervene. When she can observe from the sidelines while the team self-manages, she knows she has shaped the right conditions for them to thrive.  Second, success means having metrics that demonstrate improvement over time: team happiness, flow, and how individuals have grown in their roles. These metrics aren't just for the team—they're for sharing with leadership to show the positive impact created.  Third, and perhaps most importantly, success is about creating psychological safety where team members feel comfortable disagreeing, engaging in healthy conflict, and being creative without taking things personally.  One powerful indicator Mohini uses is the language of the team: do they say "their sprint goal" or "our sprint goal"? This subtle shift from passive to possessive language reveals the true level of ownership the team has developed. It's an easy thing to observe but often missed by Scrum Masters.   Self-reflection Question: Listen carefully in your next sprint planning or daily scrum—does your team use "we" and "our" language, or do they speak about the work as something external to them? Featured Retrospective Format for the Week: Timeline Retrospective Mohini finds herself returning to the Timeline retrospective more than any other format, especially when a team has been going through something complex—a difficult sprint, a major release, or a quarterly review with a working group. The format helps people pause and reflect on what has happened before jumping into "what do we change next?" In a physical room, she draws a line on the whiteboard and invites people to add sticky notes for key moments that stood out during the period. In virtual settings, she uses a digital whiteboard. The moments can be good, bad, confusing, or stressful—anything significant. The exercise starts silently, giving everyone space to think without being influenced. Then the team walks through the timeline chronologically, sharing stories behind their notes.  What makes this format powerful is that it creates shared understanding before asking for solutions. Team members often realize that others experienced the same event differently. However, Mohini warns that the timeline can feel overwhelming when you see all the stickies on the board. The key is to build a bridge before jumping to actions: have the team identify patterns, vote on items to discuss further, and only then derive concrete actions from the prioritized items.   [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 Mohini Kissoon   Mohini is an Agility Lead with over eight years of experience as a Scrum Master. She is passionate about building high-performing, self-managing teams that delight customers. Mohini improves flow and collaboration across systems, meets teams where they are, and co-creates environments enabling adaptability, meaningful interactions, and continuous improvement and learning.   You can link with Mohini Kissoon on LinkedIn.

Mohini Kissoon: Beyond the AI Fear—Discovering What Makes Scrum Masters Truly Irreplaceable 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 real challenge isn't whether AI will replace Scrum Masters. It's whether we understand what parts of our work are actually irreplaceable—and whether we're spending our time on those things." - Mohini Kissoon   Mohini is wrestling with a challenge that's coming up repeatedly in conversations with Agile coaches and Scrum Masters: the anxiety around AI and what it means for their role. She hears questions like "Will AI replace Scrum Masters?" but believes we're asking the wrong question. The real challenge is understanding which parts of our work are truly irreplaceable and demonstrating value in those areas.  People might think that AI can generate sprint reports and analyze team metrics—so why do we need Scrum Masters? But what's missing is the human touch: reading the room, sensing unspoken tension, building trust through presence, and asking questions that shift perspectives. Mohini and Vasco explore how the Scrum Master role may have accidentally become defined by process and structure rather than impact on teams.  The solution lies in showing value through concrete metrics—demonstrating improvement in team happiness, flow, cycle time, and lead time. Scrum Masters need to use storytelling and create history that shows the before and after. They should leverage champions from teams they've worked with to share testimonials. We are like diplomats: we work through influence and need allies both inside and outside the team to support our work.   Self-reflection Question: If AI could handle all the administrative and mechanical aspects of your Scrum Master role tomorrow, what would you spend your time doing—and are you already investing enough time in those irreplaceable human elements?   [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 Mohini Kissoon   Mohini is an Agility Lead with over eight years of experience as a Scrum Master. She is passionate about building high-performing, self-managing teams that delight customers. Mohini improves flow and collaboration across systems, meets teams where they are, and co-creates environments enabling adaptability, meaningful interactions, and continuous improvement and learning.   You can link with Mohini Kissoon on LinkedIn.