Scrum Master Toolbox Podcast: Agile storytelling from the trenches

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.