Scrum Master Toolbox Podcast: Agile storytelling from the trenches

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.

Felipe Engineer-Manriquez, a construction practitioner and agile coach who maps Product Owner ideas to the built environment. He explains why the customer voice can live in unexpected roles, how that voice shifts across construction phases, and how military leadership lessons help empower team-level decision makers. He also covers coaching people to think like the owner and timing priorities to reduce waste.

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.

Felipe Engineer-Manriquez, best-selling author and lean-agile builder who trains construction teams, tells a story of failure-turned-breakthrough. He contrasts teaching tools with silently doing them. He explains resisting Gantt culture, NoEstimates thinking, and the “ninja” approach that made work visible and earned trust through delivered promises.

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, an Agile coach known for her insights on product ownership and team collaboration, dives into the pitfalls of prioritizing velocity over meaningful outcomes. She discusses how an obsession with output undermines team growth and effective decision-making. Highlighting the importance of strong partnerships between Product Owners and Scrum Masters, Cristina emphasizes asking questions to foster collaboration. She also shares a powerful framework for conversations that enrich team interactions, drawing from Nonviolent Communication principles.

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.