Podcasts about Scrum

Alex Sloley: When Toxic Leadership Creates Teams That Self-Destruct Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "They would take notes at every team meeting, so that later on they could argue with team members about what they committed to, and what they said in meetings." - Alex Sloley Alex recounts working with a small team where a project manager created such a toxic environment that one new hire quit after just eight hours on the job. This PM would belittle team members publicly, take detailed notes to use as weapons in contract negotiations, and dominate the team through intimidation. The situation became so severe that one team member sent an email that sounded like a suicide note. When the PM criticized Alex's "slide deck velocity," comparing four slides per 15 minutes to Alex's one, he realized the environment was beyond salvaging. Despite coaching the team and attempting to introduce Scrum values, Alex ultimately concluded that management was encouraging this behavior as a control mechanism. The organization lacked trust in the team, creating learned helplessness where team members became submissive and unable to resist. Sometimes, the most important lesson for a Scrum Master is recognizing when a system is too toxic to change and having the courage to walk away. Alex emphasizes that respect—one of the core Scrum values—was completely absent, making any meaningful transformation impossible. In this segment, we talk about “learned helplessness”.  Self-reflection Question: How do you recognize when a toxic environment is being actively encouraged by the system rather than caused by individual behavior? What are the signs that it's time to exit rather than continue fighting? Featured Book of the Week: The Goal by Eliyahu M. Goldratt Alex describes his complex relationship with The Goal by Goldratt—it both inspires and worries him. He struggles with the text because the concepts are so deep and meaningful that he's never quite sure he's fully understood everything Goldratt was trying to convey. The book was difficult to read, taking him four times longer than other agile-related books, and he had to reread entire sections multiple times. Despite the challenge, the concepts around Theory of Constraints and systems thinking have stayed with him for years. Alex worries late at night that he might have missed something important in the book.  He also mentions reading The Scrum Guide at least once a week, finding new tidbits each time and reflecting on why specific segments say what they say. Both books share a common thread—the text that isn't in the text—requiring readers to dig deeper into the underlying principles and meanings rather than just the surface content. [The Scrum Master Toolbox Podcast Recommends]

Alex Sloley: The Sprint Planning That Wouldn't End - A Timeboxing Failure 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. "Although I knew about the steps of sprint planning, what I didn't really understand was the box of time versus the box of scope." - Alex Sloley Alex shares a critical learning moment from his first team as a Scrum Master. After six months in the role, during an eight-hour sprint planning session for a four-week sprint, he successfully completed the "what" portion but ran out of time before addressing "how." Rather than respecting the timebox, Alex forced the team to continue planning for another four hours the next day—blowing the timebox by 50%. This experience taught him a fundamental lesson: the difference between scope-boxing and timeboxing. In waterfall, we try to control scope while time slips away. In Scrum, we fix time and let scope adjust. Alex emphasizes that timeboxing isn't just about keeping meetings short—it's about limiting work in process and maintaining focus. His practical tip: use visible timers to train yourself and your teams to respect timeboxes. This mindset shift from controlling scope to respecting time remains one of the most important lessons for Scrum Masters. Self-reflection Question: How often do you prioritize completing a planned agenda over respecting the timebox? What message does this send to your team about the values you're reinforcing? [The Scrum Master Toolbox Podcast Recommends]

Scrum Theatre and the Agile IllusionImagine your team having a perfect stand-up. Everyone's smiling, and it seems like everything is going smoothly. Everyone says that they do not have any blockers for today and that all's well. Each person on the team is relaxed, and your Scrum Master is grinning from ear to ear.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

BONUS: The Evolution of Agile - From Project Management to Adaptive Intelligence, With Mario Aiello In this BONUS episode, we explore the remarkable journey of Mario Aiello, a veteran agility thinker who has witnessed and shaped the evolution of Agile from its earliest days. Now freshly retired, Mario shares decades of hard-won insights about what works, what doesn't, and where Agile is headed next. This conversation challenges conventional thinking about methodologies, certifications, and what it truly means to be an Agile coach in complex environments. The Early Days: Agilizing Before Agile Had a Name "I came from project management and project management was, for me, was not working. I used to be a wishful liar, basically, because I used to manipulate reports in such a way that would please the listener. I knew it was bullshit." Mario's journey into Agile began around 2001 at Sun Microsystems, where he was already experimenting with iterative approaches while the rest of the world was still firmly planted in traditional project management. Working in Palo Alto, he encountered early adopters discussing Extreme Programming and had an "aha moment" - realizing that concepts like short iterations, feedback loops, and learning could rescue him from the unsustainable madness of traditional project management. He began incorporating these ideas into his work with PRINCE2, calling stages "iterations" and making them as short as possible. His simple agile approach focused on: work on the most important thing first, finish it, then move to the next one, cooperate with each other, and continuously improve. The Trajectory of Agile: From Values to Mechanisms "When the craze of methodologies came about, I started questioning the commercialization and monetization of methodologies. That's where things started to get a little bit complicated because the general focus drifted from values and principles to mechanisms and metrics." Mario describes witnessing three distinct phases in Agile's evolution. The early days were authentic - software developers speaking from the heart about genuine needs for new ways of working. The Agile Manifesto put important truths in front of everyone. However, as methodologies became commercialized, the focus shifted dangerously away from the core values and principles toward prescriptive mechanisms, metrics, and ceremonies. Mario emphasizes that when you focus on values and principles, you discover the purpose behind changing your ways of working. When you focus only on mechanics, you end up just doing things without real purpose - and that's when Agile became a noun, with people trying to "be agile" instead of achieving agility. He's clear that he's not against methodologies like Scrum, XP, SAFe, or LeSS - but rather against their mindless application without understanding the essence behind them. Making Sense Before Methodology: The Four-Fit Framework "Agile for me has to be fit for purpose, fit for context, fit for practice, and I even include a fourth dimension - fit for improvement." Rather than jumping straight to methodology selection, Mario advocates for a sense-making approach. First, understand your purpose - why do you want Agile? Then examine your context - where do you live, how does your company work? Only after making sense of the gap between your current state and where the values and principles suggest you should be, should you choose a methodology. This might mean Scrum for complex environments, or perhaps a flow-based approach for more predictable work, or creating your own hybrid. The key insight is that anyone who understands Agile's principles and values is free to create their own approach - it's fundamentally about plan, do, inspect, and adapt. Learning Through Failure: Context is Paramount "I failed more often than I won. That teaches you - being brave enough to say I failed, I learned, I move on because I'm going to use it better next time." Mario shares pivotal learning moments from his career, including an early attempt to "agilize PRINCE2" in a command-and-control startup environment. While not an ultimate success, this battle taught him that context is paramount and cannot be ignored. You must start by understanding how things are done today - identifying what's good (keep doing it), what's bad (try to improve it), and what's ugly (eradicate it to the extent possible). This lesson shaped his next engagement at a 300-person organization, where he spent nearly five months preparing the organizational context before even introducing Scrum. He started with "simple agile" practices, then took a systems approach to the entire delivery system. A Systems Approach: From Idea to Cash "From the moment sales and marketing people get brilliant ideas they want built, until the team delivers them into production and supports them - all that is a system. You cannot have different parts finger-pointing." Mario challenges the common narrow view of software development systems. Rather than focusing only on prioritization, development, and testing, he advocates for considering everything that influences delivery - from conception through to cash. His approach involved reorganizing an entire office floor, moving away from functional silos (sales here, marketing there, development over there) to value stream-based organization around products. Everyone involved in making work happen, including security, sales, product design, and client understanding, is part of the system. In one transformation, he shifted security from being gatekeepers at the end of the line to strategic partners from day one, embedding security throughout the entire value stream. This comprehensive systems thinking happened before formal Scrum training began. Beyond the Job Description: What Can an Agile Coach Really Do? "I said to some people, I'm not a coach. I'm just somebody that happens to have experience. How can I give something that can help and maybe influence the system?" Mario admits he doesn't qualify as a coach by traditional standards - he has no formal coaching qualifications. His coaching approach comes from decades of Rugby experience and focuses on establishing relationships with teams, understanding where they're going, and helping them make sense of their path forward. He emphasizes adaptive intelligence - the probe, sense, respond cycle. Rather than trying to change everything at once and capsizing the boat, he advocates for challenging one behavior at a time, starting with the most important, encouraging adaptation, and probing quickly to check for impact of specific changes. His role became inviting people to think outside the box, beyond the rigidity of their training and certifications, helping individuals and teams who could then influence the broader system even when organizational change seemed impossible. The Future: Adaptive Intelligence and Making Room for Agile "I'm using a lot of adaptive intelligence these days - probe, sense, respond, learn and adapt. That sequence will take people places." Looking ahead, Mario believes the valuable core of Agile - its values and principles - will remain, but the way we apply them must evolve. He advocates for adaptive intelligence approaches that emphasize sense-making and continuous learning rather than rigid adherence to frameworks. As he enters retirement, Mario is determined to make room for Agile in his new life, seeking ways to give back to the community through his blog, his new Substack "Adaptive Ways," and by inviting others to think differently. He's exploring a "pay as you wish" approach to sharing his experience, recognizing that while he may not be a traditional coach or social media expert, his decades of real-world experience - with its failures and successes - holds value for those still navigating the complexity of organizational change. About Mario Aiello Retired from full-time work, Mario is an agility thinker shaped by real-world complexity, not dogma. With decades in VUCA environments, he blends strategic clarity, emotional intelligence, and creative resilience. He designs context-driven agility, guiding teams and leaders beyond frameworks toward genuine value, adaptive systems, and meaningful transformation. You can link with Mario Aiello on LinkedIn, visit his website at Agile Ways.

Renee Troughton: Analytics From Day One and Four Other Principles of Great POs 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. "Product owners who think about their products as just a backlog that I prioritize, and I get some detailed requirements from stakeholders, and I give that to the team... that's not empowering the team. And it's probably leading you to building the wrong thing, just faster." The Bad Product Owner: The Backlog Manager Without Vision Renee describes a pattern of Product Owners who don't understand product management—they lack roadmaps, strategy, and never speak to customers. These POs focus solely on backlogs, prioritizing detailed requirements from stakeholders without testing hypotheses or learning about their market. Taking an empathetic view, Renee notes these individuals may have fallen into the role without passion, never seeing what excellence looks like, and struggling with extreme time poverty. Product ownership is one of the hardest roles from a time perspective—dealing with legislative requirements, compliance, risk, fail-and-fix work, and constant incoming demands. Drowning in day-to-day urgency, they lack breathing space for strategic thinking.  These POs also struggle with vulnerability, feeling they should have all answers as leaders, making it difficult to admit knowledge gaps. Without organizational safety to fail, they can't demonstrate the confidence balanced with humility needed to test hypotheses and potentially be wrong. The result is building the wrong thing faster, without empowering teams or creating real value. Self-reflection Question: Are you managing your Product Owners' workload and supporting their strategic thinking time, or are you allowing them to drown in tactical work that prevents them from truly leading their products? The Great Product Owner: Analytics from Day One and Market Awareness "They really iterated, I think, 5 key principles quite consistently... the one thing that did really shape my thinking at that time was... Analytics from day one." Renee celebrates a Chief Product Owner who led 13 teams with extraordinary effectiveness. This PO consistently communicated five key principles, with "analytics from day one" being paramount—emphasizing the critical need to know immediately if new features work and understanding customer behavior from launch. This PO demonstrated deep market awareness, regularly spending time in Silicon Valley, understanding innovation trends and where the industry was heading. They maintained a clear product vision and could powerfully sell the dream to stakeholders.  Perhaps most impressively, they brought urgency during a competitive "space race" situation when a former leader left with intellectual property to build a competing product. Despite this pressure, they never allowed compromise on quality—rallying teams with mission and purpose while maintaining standards. This combination of strategic vision, market knowledge, data-driven decision-making, and balanced urgency created an environment where teams delivered excellence under competitive pressure. [The Scrum Master Toolbox Podcast Recommends]

Renee Troughton: From Lower-Order to Higher-Order Values in Scrum 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, as a senior leader, demonstrate vulnerability, it creates real magic in an organization where others can open up and be their authentic self." Renee defines success for Scrum Masters through deeply human values: integrity, holding her truth, being compassionately authentic, caring, open, honest, listening, and vulnerable. She emphasizes that vulnerability as a senior leader creates transformative magic in organizations, allowing others to bring their authentic selves to work. Drawing on Byron Katie's "Loving What Is" and Frederick Laloux's "Reinventing Organizations," Renee explains that many corporate organizations focus on lower-order values like results and performance, while more autonomous organizations prioritize higher-order values rooted in the heart. When having conversations with people, Renee connects with them as human beings first—not rushing to business if someone is struggling personally. Success means seeing people completely for who they are, not as resources to be changed or leveraged. The foundation for collaboration, empowerment, and autonomy is trust, respect, and safety. Renee emphasizes that without these fundamental values in place, everything else implodes. She demonstrates how vulnerability, active listening, and accepting people where they are creates the fertile ground for successful teams and organizations. Self-reflection Question: Do you demonstrate vulnerability as a leader, creating space for others to bring their authentic selves to work, or do you hide behind a professional facade that prevents genuine human connection? Featured Retrospective Format for the Week: Themed Retrospectives (Monopoly, Sports, Current Events) "It gave a freshness to it. And it gave almost like a livelihood or a joyfulness to it as an activity as well." Renee recommends themed retrospectives like the Monopoly Retro or sports-themed formats that use current events or cultural references (aka metaphor retrospectives). While working at a consultancy, they would theme retrospectives every week around different topics—football, news events, or various scenarios—using collages of pictures showing different emotions (upset, angry, happy). Team members would identify with feelings and reframe their week within the theme's context, such as "it was a rough game" or "we didn't score enough goals." The brilliance of this approach is covering the same retrospective questions while bringing freshness, creativity, and joyfulness to the activity. These metaphorical formats allow teams to verbalize things that aren't easily expressible in structured formats, triggering different perspectives and creative thinking. The format stays consistent while feeling completely new, maintaining engagement while avoiding retrospective fatigue. [The Scrum Master Toolbox Podcast Recommends]

Renee Troughton: Managing Dependencies and Downstream Bottlenecks in Scrum 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. "For the actual product teams, it's not a problem for them... It's more the downstream teams that aren't the product teams, that are still dependencies... They just don't see that work until, hey, we urgently need this." Renee brings a dual-edged challenge from her current work with dozens of teams across multiple business lines. While quarterly planning happens at a high level, small downstream teams—middleware, AI, data, and even non-technical teams like legal—are not considered in the planning process. These teams experience unexpected work floods with dramatic peaks and troughs throughout the quarter. The product teams are comfortable with ambiguity and incremental delivery, but downstream service teams don't see work coming until it arrives urgently. Through a coaching conversation, Renee and Vasco explore multiple experimental approaches: top-to-bottom stack ranking of initiatives, holding excess capacity based on historical patterns, shared code ownership where downstream teams advise rather than execute changes, and using Theory of Constraints to manage flow into bottleneck teams. They discuss how lack of discovery work compounds the problem, as teams "just start working" without identifying all players who need involvement. The solution requires balancing multiple strategies while maintaining an experimentation mindset, recognizing that complex systems require sensing our way toward solutions rather than predicting them. Self-reflection Question: Are you actively managing the flow of work to prevent downstream bottlenecks, or are you allowing your "downstream teams" to be repeatedly overwhelmed by last-minute urgent requests? [The Scrum Master Toolbox Podcast Recommends]

Renee Troughton: The Hidden Cost of Constant Restructuring in Agile Organizations 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. "Trust and safety are the most fundamental foundations of a team to perform. And so you are just breaking the core of teams when you're doing this." Renee challenges us to look beyond team dysfunction and examine the "dirty little secrets" in organizations—leadership-driven anti-patterns that destroy team performance. She reveals a cyclical pattern of constant restructuring that occurs every six months in many organizations, driven by leaders who avoid difficult performance management conversations and instead force people through redundancy rounds. This creates a cascade of fear, panic, and victim mindset throughout the organization. Beyond restructuring, Renee identifies other destructive patterns including the C-suite shuffle (where new CEOs bring in their own teams, cascading change throughout the organization) and the insourcing/outsourcing swings that create chaos over 5-8 year cycles. These high-level decisions drain productivity for months as teams storm and reform, losing critical knowledge and breaking the trust and safety that are fundamental for high performance. Renee emphasizes that as Agile coaches and Scrum Masters, we often don't feel empowered to challenge these decisions, yet they represent the biggest drain on organizational productivity. Self-reflection Question: Have you identified the cyclical organizational anti-patterns in your workplace, and do you have the courage to raise these systemic issues with senior leadership? Featured Book of the Week: Loving What Is by Byron Katie "It teaches you around how to reframe your thoughts in the day-to-day life, to assess them in a different light than you would normally perceive them to be." Renee recommends "Loving What Is" by Byron Katie as an essential tool for Scrum Master introspection. This book teaches practical techniques for reframing thoughts and recognizing that problems we perceive "out there" are often internal framing issues. Katie's method, called "The Work," provides a worksheet-based approach to introspection that helps identify when our perceptions create unnecessary suffering. Renee also highlights Marshall Rosenberg's "Nonviolent Communication" as a companion book, which uses language to tap into underlying emotions and needs. Both books offer practical, actionable techniques for self-knowledge—a critical skill for anyone in the Scrum Master role. The journey these books provide leads to inner peace through understanding that many challenges stem from how we internally frame situations rather than external reality. We have many episodes on NVC, Nonviolent Communication, which you can dive into and learn from experienced practitioners.  [The Scrum Master Toolbox Podcast Recommends]

Renee Troughton: How to Navigate Mandatory Deadlines in Scrum 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 said to the CIO at the time, we're not going to hit this. In fact, we'll be... I can actually tell you, we're gonna be 3 weeks late... And he said: ‘Just make it work!'" Renee shares a powerful story from her work on a mandatory legislative compliance project where reality clashed with executive expectations. Working with a team new to Agile, she carefully established velocity over two sprints and projected the delivery timeline. The challenge intensified when sales continued promising bespoke features to clients while the deadline remained fixed. Despite transparently communicating the team would miss the mandatory date by three weeks, leadership demanded she "just make it work" without providing solutions. Renee found herself creating a misleading burn-up chart to satisfy executive confidence, while the organization played a dangerous game of chicken—waiting for another implementer to admit delays first. This experience taught her the critical importance of courage in conversations with leaders and the need to clearly separate business decisions from development team responsibilities. Sometimes the best we can do is provide transparency and let leaders own the consequences of their choices. In this episode, we refer to the seminal book on large projects: The Mythical Man Month, by Frederick Brooks. Self-reflection Question: When faced with unrealistic demands from leadership, do you have the courage to maintain transparency about your team's reality, even when it means refusing to create false artifacts of confidence? [The Scrum Master Toolbox Podcast Recommends]

Scrum Has Become a Nice Term to Hide Bad ManagementOnce a wise man said: Fire all Scrum Masters and your non-technical managers who run your IT departments, and watch your productivity to boost up! In most cases, all you need is to hire highly-experienced Tech Leads and show trust in them. Communicate with them and share your insights, answer their questions, and provide them with what they need, including but not limited to the budget, time, ad-hoc specialist consultants, and coaches who would work for them to improve their non-technical skills. The rest, they will figure out themselves.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

How to Engage Busy Stakeholders - Mike CohnWe often find ourselves reliant on others outside the team.For example, an agile team may get stuck waiting for feedback on the latest features or input on what to build next because a key stakeholder has never shown up for a sprint review. Without that stakeholder's feedback, the team is impeded: unable to determine if what they've created is what's needed.The team nags, pleads, and cajoles. But still they're left waiting because stakeholders are often busy, and they just can't (or won't) find the time.You've tried moving the sprint review meeting to more convenient times. You've sent agendas that make it clear the stakeholder's most desired feature is the one being discussed in the review.But time and time again, something comes up at the last minute and the stakeholder is a no show.In these instances, it's time to take the meeting to them. When a stakeholder won't (or can't) show up for the team, it's time for a different approach: Schedule time on the stakeholder's calendar for a meeting a few days before sprint planning.Use that block of time to work together on what the team needs.Schedule a Non-Meeting Meeting Tip within the Tip: Want more help with team dynamics and stakeholder management? Try my free Scrum Team Reset training. It's three videos from me that will help you find new ways to take your team from good to great. When I schedule the meeting, I'll sometimes be very clear what the meeting is about: “I want to go over such-and-such with you before the review.” Other times, I'll be more vague: “I need to chat about the project.”Use whatever language you need to secure time on the person's calendar. Why? Because we are all more willing to cancel appointments with ourselves than we are to cancel an appointment with someone else. By putting time on their calendar that they're reluctant to cancel, you've secured enough time for them to actually do the work. Get the To-Do to DoneDuring the meeting, explain to them the work you need them to do (look at the feature and give feedback or clarify how the feature should work.) Then, use the time to step through the implementation (or plan) with them.This results in two things: the team gets the information it needs. The stakeholder finds that the thing they've been putting off really wasn't so bad once they focused on getting it done. Why This WorksWhen stakeholders show an inability to get work or answers to you at appropriate times, it's time to intervene. Maybe they're worried their time will be wasted in a review where their feature is one of many being discussed.Maybe “review the xyz feature” has been on their to-do list and keeps getting bumped down. Or maybe they haven't actually scheduled a specific time to work on it.No matter the reason, the work the team needs done is not happening. And your best chance of helping the stakeholder do that work is to schedule time with the stakeholder directly. And then use that time to make it happen.Should stakeholders be able to do this on their own?Sure.But we all struggle at times. My experience is that after doing this a handful of times with a stakeholder, most stakeholders will form a new habit and be able to continue without you.In other cases, you and the stakeholder will discover it actually is more efficient when done together, and you'll keep a recurring meeting on their calendar that isn't the review. That's perfectly fine, too.Stakeholders are often busy. And that can cause them to take longer to respond than a fast-moving agile team might like. Finding creative solutions that keep the team moving (even if it's not something Scrum prescribes) is the best way to help advance a team from good to great,How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Happy 125 episodes. To celebrate, we aren't talking games, we're talking anime. Not just talking anime but getting mad at each other over each other's takes on anime. Except Brody. He got off scotfree, somehow. MORE PLACES TO FIND USCrubscribe ► https://bit.ly/CrubcastGet the show early and get exclusive content at our Patreon ► https://www.patreon.com/crubOur Crubcasts are recorded LIVE at https://www.twitch.tv/crub_official every Tuesday at 7pm Eastern, with EXCLUSIVE Pre- and Post-ShowsJoin our Discord ► https://crub.org/joinBlueSky ► https://bsky.app/profile/crub.orgCome join our Steam group ► https://steamcommunity.com/groups/crubclubPodcasts are available on Apple, Google, Spotify, and other platforms are available at ► https://crub.orgSHOW NOTESBe warned, we are going to talk random spoilers about the anime series we bring up. Warning!Here are our lists:https://myanimelist.net/profile/Jtart9https://myanimelist.net/profile/Wolfkaosaunhttps://myanimelist.net/profile/RACROXAnd he wasn't here, but he is taking recommendations:https://myanimelist.net/profile/MykonosFanWhile we're plugging, Justin and Chris went through pretty much all of Makoto Shinkai's works on our Patreon:https://www.patreon.com/collection/320851?view=expandedTODAY'S CRUBCAST HOSTSBrody: https://www.youtube.com/@RACROXJustin: https://www.youtube.com/@WorldFamousJtart9Sean: https://www.youtube.com/@WolfkaosaunCHAPTERS00:00 Don't tell Scrum that he sounds like Narduar04:40 The opening salvo begins against Justin and Sword Art Online09:52 Justin DARED to only give Gurren Lagann an 8. An eight!!!18:10 Sean takes aim at Justin's other 10/1024:41 Wolfkaosaun explains and defends Wolf's Rain (tumblrcore)29:52 Sean has seen FMA but not FMA Brotherhood...and Jojo dissection37:56 Echoes of Justin's Sin44:04 Brody HATES modern anime fans!!! (not real, clickbait)51:45 "Brody is a lot more liberal" - Justin (with his 10/10s)53:30 Is Death Note actually a good intro to anime?1:06:30 Would our most recent game be easier or harder if Sonic was the main character? ★ Support this podcast on Patreon ★

Tom Molenaar: When Product Owners “Eat the Grass” for Their 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. The Great Product Owner: The Vision Catalyst "This PO had the ability to communicate the vision and enthusiasm about the product, even I felt inspired." Tom describes an exceptional Product Owner who could communicate vision and enthusiasm so effectively that even he, as the Scrum Master, felt inspired about the product. This PO excelled at engaging teams in product discovery techniques, helping them move from merely delivering features to taking outcome responsibility. The PO introduced validation techniques, brought customers directly to the office for interviews, and consistently showed the team the impact of their work, creating a strong connection between engineers and end users. The Bad Product Owner: The Micromanager "This PO was basically managing the team with micro-managing approach, this blocked the team from self-organizing." Tom encountered a Product Owner who was too controlling, essentially micromanaging the team instead of empowering them. This PO hosted daily stand-ups, assigned individual tasks, and didn't give the team space for self-organization. When Tom investigated the underlying motivation, he discovered the PO believed that without tight control, the team would underperform. Tom helped the PO understand the benefits of trusting the team and worked with both sides to clarify roles and responsibilities, moving from micromanagement to empowerment. In this segment, we refer to the book “Empowered” by Marty Cagan. Self-reflection Question: How do you help Product Owners find the balance between providing clear direction and allowing team autonomy? [The Scrum Master Toolbox Podcast Recommends]

Tom Molenaar: Purpose, Process, and People—The Three Pillars of 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. "I always try to ask the team first, what is your problem? Or what is the next step, do you think? Having their input, having my input, bundle it and share it." Tom defines success for Scrum Masters through three essential pillars: purpose (achieving the team's product goals), process (effective Agile practices), and people (team maturity and collaboration). When joining new teams, he uses a structured approach combining observation with surveys to get a 360-degree view of team performance. Rather than immediately implementing his own improvement ideas, Tom prioritizes asking teams what problems they want to solve and finding common ground for a "handshake moment" on what needs to be addressed. Featured Retrospective Format for the Week: Creative Drawing of the Sprint Tom's favorite retrospective format involves having team members draw their subjective experience of the sprint, then asking others to interpret each other's drawings. This creative approach brings people back to their childhood, encourages laughter and fun, and helps team members tap into each other's experiences in ways that traditional verbal retrospectives cannot achieve. The exercise stimulates understanding between team members and often reveals important topics for improvement while building connection through shared interpretation of creative expressions. Example activity you can use to “draw the sprint”.  [The Scrum Master Toolbox Podcast Recommends]

Is Scrum Dying? Or Are We Just Doing It Wrong?Scrum used to be king. Now people don't even want it on their CV.Remember when being a Product Owner was cool? When Scrum Masters were change agents, not glorified note-takers?When saying “we use Scrum” signalled progressive, Agile thinking?Fast forward to now, and you'll find Product Owners ashamed of the title, Scrum Masters sidelined, and developers stuck in factory-mode delivery.Teams are jumping ship to SAFe, Kanban, or “whatever Spotify did,” chasing results Scrum couldn't deliver.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Tom Molenaar: Systemic Change Management—Making the Emotional Side of Change Visible Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "We tend to skip the phase where we just give the person the space to grieve, to not know, instead of that, we tend to move to solutions maybe too quick." Tom faces a significant challenge as he prepares to start with new teams transitioning between value streams in a SAFe environment. The teams will experience multiple changes simultaneously - new physical locations, new team dependencies, and organizational restructuring. Tom applies systemic change management principles, outlining five critical phases: sense of urgency, letting go, not knowing, creation, and new beginning. He emphasizes the importance of making the emotional "understream" visible, giving teams space to grieve their losses, and helping them verbalize their feelings before moving toward solutions. In this episode, we refer to Systemic Change Management, an approach that views organizations as complex, interconnected systems—rather than collections of independent parts. Instead of focusing only on individual skills, isolated processes, or top-down directives, SCM works with the whole system (people, structures, culture, and external environment) to create sustainable transformation. Self-reflection Question: How comfortable are you with sitting in uncertainty and allowing teams to process change without immediately jumping to solutions? [The Scrum Master Toolbox Podcast Recommends]

Is it ever OK to deviate from the Scrum Guide? - Mike CohnI'm out there on social media and I see all the same posts you do about the sanctity of the Scrum rules. And I get it. There are many rules of Scrum that teams break when they shouldn't. But I don't think it does anyone any good to be so hung up on rules that you throw practicality out the window.Here's the thing: No team should break a Scrum rule before they've tried to do it by the book for a while, and given themselves a chance to understand why each rule exists in the first place.But teams that have been doing Scrum together for a while sometimes need to bend a few Scrum rules to fit their specific circumstances and situation. And in most cases no one needs to start calling foul if they do!Here are a few common rules most teams can safely break or bend:Never extending a sprint is a great rule. Usually. Can it be broken? Yes—not often and always for a good reason (such as a holiday that makes a longer sprint sensible).It's ideal to have a dedicated Scrum Master–it's the best way to build high-performing teams. But having a dedicated Scrum Master is an economic decision and it may not always be justified, especially once the team can take on some responsibilities for itself.Having a retrospective every sprint is a wonderful way to put improvement front and center. But if a team is running one or two-week sprints and things are going well, I think it's OK for them to only do a retrospective every four weeks (or every other sprint).Teams that are new to Scrum should do Scrum by the book. But it's unrealistic to expect teams to never bend or break a rule to better fit their context.Knowing when to follow the rules, and when to break them, helps teams succeed,How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Enrollment for the Focus Room October Sprint closes tomorrow!

Tom Molenaar: How to Spot and Fix Lack of Trust in Scrum 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 people don't speak up, it's because there's no trust. The team showed that they did not feel free to express their opinions." Tom describes working with a team that appeared to be performing well on the surface - they were reaching their goals and had processes in place. However, deeper observation revealed a troubling dynamic: a few dominant voices controlled discussions while half the team remained silent during ceremonies. Through one-on-ones, Tom discovered team members felt judged and unsafe to express their ideas. Using the Lencioni Pyramid as a framework, he helped the team address the fundamental lack of trust that was preventing constructive conflict and genuine collaboration. Featured Book of the Week: Empowered by Marty Cagan Tom recommends "Empowered" by Marty Cagan as a book that significantly influenced his approach to team coaching. The book focuses on empowering teams and organizations to deliver great products while developing ordinary people into extraordinary performing teams. Tom appreciates its well-structured approach that covers all necessary elements without getting lost in details. The book provides practical tools for effective coaching, including techniques for regular one-on-ones, active listening, constructive feedback, setting clear expectations, celebrating success, and creating a culture of learning from failure. [The Scrum Master Toolbox Podcast Recommends]

Tom Molenaar: When To Stop Helping Agile Teams To Change—A Real Life Story 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. "Instead of slowing down and meeting the team in their resistance, I started to try and drag them because I saw the vision of the possible improvement, but they did not see it." Tom shares a powerful failure story about a team that didn't feel the urgency to improve their way of working. Despite management wanting the team to become more effective, Tom found himself pushing improvements that the team actively resisted. Instead of slowing down to understand their resistance, he tried to drag them forward, leading to exhaustion and ultimately his decision to leave the assignment. This episode explores the critical lesson that it's not our job to save teams that don't want to be saved, and the importance of recognizing when to step back. Self-reflection Question: When you encounter team resistance to change, how do you distinguish between healthy skepticism that needs addressing and fundamental unwillingness to improve? [The Scrum Master Toolbox Podcast Recommends]

Tony Squires is joined by Wade Graham, Nathan Hindmarsh and Brent Read who dissected the Melbourne Storm's win over the Cronulla sharks to be first team through to the 2025 NRL Grand Final. Wade had some strong comments on who should be officiating the Grand Final and we looked ahead to see if the Broncos can end the Panthers run in the second Preliminary Final. Plus, new London Broncos coach Jason Demetriou joined the team to discuss his new role and Ready's Mail, Tony's Quiz, Believe It Or Not along with plenty more!See omnystudio.com/listener for privacy information.

Tony Squires is joined by Wade Graham, Nathan Hindmarsh and Brent Read who dissected the Melbourne Storm's win over the Cronulla sharks to be first team through to the 2025 NRL Grand Final. Wade had some strong comments on who should be officiating the Grand Final and we looked ahead to see if the Broncos can end the Panthers run in the second Preliminary Final. Plus, new London Broncos coach Jason Demetriou joined the team to discuss his new role and Ready's Mail, Tony's Quiz, Believe It Or Not along with plenty more!See omnystudio.com/listener for privacy information.

Terry Haayema: The Product Owner Who Made Retros Unsafe (And How We Fixed It) 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 biggest anti-pattern was that he made the retro unsafe... he would come to the retro and called people out for things that had not been done." The Bad Product Owner: The PO Who Made Retros Unsafe Terry describes a product owner who came from a management background focused on widgets and KPIs, completely unprepared for the collaborative nature of the product owner role. This person's biggest anti-pattern was making retrospectives unsafe by calling out individual team members for things not completed or not done to his satisfaction. When gentle coaching interventions failed, Terry took the dramatic step of excluding the PO from retrospectives entirely. Surprisingly, this shock treatment worked - when the PO asked why he wasn't invited, Terry used SBI feedback (Situation, Behavior, Impact) to help him understand how his actions were destroying team dynamics. The story has a positive ending, with the PO eventually understanding and changing his approach. In this segment, we refer to the Retrospective Prime Directive, and the SBI feedback framework. The Great Product Owner: The Customer Connector Terry's best product owner example saw their role not just as the voice of the customer, but as the connector between team and customers. Instead of relying solely on user stories and personas, this PO organized regular informal events where real customers and team members could meet, share pizza and beer, and have genuine conversations. These social connections led to deep customer understanding and resulted in their best feature ever - a simple addition that showed customers their last six orders for easy reordering. This feature increased both order frequency and size while dramatically improving the team's ability to empathize with their users. Self-reflection Question: How might you help your product owner move from being the voice of the customer to being the bridge that connects your team directly with real users? [The Scrum Master Toolbox Podcast Recommends]

Terry Haayema: Why "Working Myself Out of a Job" Is Wrong for Scrum Masters Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "Success for a Scrum Master is to do myself out of a job... which I don't buy into at all, because a team will always need a coach." Terry challenges the common belief that Scrum Masters succeed by working themselves out of a job, arguing instead that teams always need coaching as they continuously improve. He emphasizes the importance of separating his outcomes from the team's success to avoid becoming part of the system he's trying to help. For Terry, success is measured by the visible joy he can create in people - when leaders approach him with happiness, when team members are excited to see him, when absenteeism drops because people actually want to come to work. He shares a powerful story of how helping teams find joy not only improved their performance but reduced their stress-related sick days from the highest to the lowest in their division. Featured Retrospective Format for the Week: Drawing Retrospectives Terry loves retrospective formats that use drawings and visual metaphors, like Draw Your Feelings, or the Sailboat retrospective. He explains that when teams draw pictures instead of immediately processing thoughts through language, they generate much richer and deeper insights. The approach works by having people first draw their thoughts, then asking "What led you to draw that picture?" This method bypasses the analytical mind and taps into more intuitive understanding. For longer-term retrospectives, Terry recommends Open Space Technology, which allows groups to self-organize around the most important questions they need to answer. Self-reflection Question: How do you measure your own success as a Scrum Master, and does that measurement inspire you to do your best work? [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Scrum.org Community Podcast, Patricia Kong hosts a discussion with Elaine Lin Hering, author of  USA Today Best Selling Book "Unlearning Silence," and Ravi Verma, a Professional Scrum Trainer. They examine how workplace culture and cultural norms influence who speaks up and why intentional communication matters.Elaine explains that silence can be strategic or damaging, depending on context, and emphasizes the need for leaders to create environments where all voices are heard. Ravi shares his experiences with reactive versus reflective decision-making and the importance of transparency. They discuss practical strategies for encouraging voice and the significance of designing inclusive meeting practices.Tune in to this inspiring episode that anyone can relate to!Get more insights about Unlearning Silence in this article on the Professional Scrum Unlocked Substack!About Elaine Lin Hering:Elaine Lin Hering a facilitator, writer, and speaker. She works with organizations and individuals to build skills in communication, collaboration, and conflict management. She has worked on six continents and facilitated executive education at Harvard, Dartmouth, Tufts, UC Berkeley, and UCLA. She is the former Advanced Training Director for the Harvard Mediation Program and a Lecturer on Law at Harvard Law School. She has worked with coal miners at BHP Billiton,micro-finance organizers in East Africa, mental health professionals in China, and senior leadership at the US Department of Commerce. Her clients include American Express, Chevron, Google, Nike, Novartis, PayPal, Pixar, and the Red Cross. She is the author of the USA Today Bestselling book Unlearning Silence: How to Speak Your Mind, Unleash Talent, and Live More Fully (Penguin, 2024).About Ravi Verma:Ravi Verma is a Public Speaker, Agile Coach, Scrum.org Professional Scrum Trainer, Evidence Based Management Consultant and Blogger with a passion for helping teams recapture the magic of making I.T. As the Founder and Chief Org Whisperer at The Org Whisperers, Ravi blends ideas from the world of Technology, Entrepreneurship and Organizational Development to develop strong teams and inspiring leaders at all levels of an organization. He recently co-founded his second startup - Al Dente, a platform that helps Agile Coach's and organizations empirically improve business outcomes in tandem with Agile delivery frameworks like Scrum. 

James Graham, Wade Graham and Charlie White are in to preview the Week three of the NRL Finals. Is Nathan Cleary the greatest player of all time? What will Madge do with the Broncos game day lineup, with Mam ready to strike. Wade shares the deep rivalry between Cronulla and the Storm and we look at the ways the Sharks will be able to target Hughes.See omnystudio.com/listener for privacy information.

James Graham, Wade Graham and Charlie White are in to preview the Week three of the NRL Finals. Is Nathan Cleary the greatest player of all time? What will Madge do with the Broncos game day lineup, with Mam ready to strike. Wade shares the deep rivalry between Cronulla and the Storm and we look at the ways the Sharks will be able to target Hughes.See omnystudio.com/listener for privacy information.

Terry Haayema: When Consensus Becomes Paralysis—The Nemawashi Challenge For Agile Software Development 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 problem I'm facing is 'too much consensus'... we talk, bounce ideas, but we don't get going." Terry shares his current coaching challenge in a Japanese company where their cultural practice of Nemawashi (consensus building) has become a barrier to progress. While working across the entire organization, he's discovered that quality is suffering because teams aren't clear about desired outcomes before starting work. The excessive focus on building consensus means initiatives bounce between stakeholders without ever gaining momentum. Terry explains how he's experimenting with delaying detailed refinement to build shared understanding as teams progress, rather than trying to achieve perfect consensus upfront. He uses the metaphor of flying a plane - pilots don't stick rigidly to flight plans but constantly make small course corrections based on real-time feedback. Self-reflection Question: In your organization, what well-intentioned practices have become obstacles to the very outcomes they were designed to achieve? [The Scrum Master Toolbox Podcast Recommends]

Setting and Managing Expectations - Mike CohnMy first Scrum project was incredibly successful, yet it was almost a failure.All of the technical aspects of the project were going extremely well. We were ahead of schedule, stress and scalability tests showed that we'd exceed uptime and reliability goals. Everyone on the team was having fun and doing their best work.The problem was that user expectations had been growing faster than the functionality being developed.The project was call center software to be used by hundreds of nurses initially, scaling to thousands. Nurses would use the system to triage patients, provide advice, dispatch emergency personnel when needed and so on.In monthly sprint reviews with the nurse users, I was routinely shocked by what they'd come to expect, some of which wasn't even technically feasible. With about three months left on the year-long project, I realized my focus had to change. From then on, I spent almost all of my time on expectations management.I met with nurses in each of the call centers and described exactly what would and would not be in the delivered system. I toned down their expectations about the system's impact on world peace, global warming, and personal weight loss.Had I not done this, the product would have been perceived as a failure.Since that project, I have been acutely aware of the importance of expectations management to the overall success of any project. Setting and managing expectations is perhaps even more important when an organization seeks to adopt or improve its agility.With agile improvement efforts, I find it helpful to set and manage expectations about four things: How quickly teams will improveHow long it will take to gain additional predictability from the team's new way of workingHow there will almost always come a time when turning back looks easier than sticking with itThe level of involvement in the transition that will be necessary from various stakeholders and organization leadersBy properly setting expectations you can avoid the problem of having an otherwise successful transition or project sunk by unrealistic expectations,How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

“Too many meetings” is one of the most common complaints in Scrum teams, but is it really the meetings, or what’s (not) happening in them? In this episode, Brian and Lance Dacy dig into the events of Scrum to uncover what works, what doesn’t, and how to make each one actually add value.

Terry Haayema: The High Cost of Unsafe Agile Retrospectives 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. "She was kind of like the mum for the team... she was actually the glue that held the team together." Terry tells the story of a team that was functioning like a feature factory until a business analyst became their champion and "team mom." This BA supported everyone through agile transformation and helped build trust and healthy conflict. However, when she mentioned something in a retrospective that led to her being put on performance management and eventually leaving, the team rapidly self-destructed. They lost their sense of belonging and teamness, retreating back to working as independent professionals rather than collaborating. The story illustrates how leadership actions can instantly destroy weeks or months of trust-building work, and how critical psychological safety is for sustainable team performance. For more critical points on how to be a great leader, check this episode with Captain David Marquet, a thought leader in the leadership space who wrote Turn the Ship Around!  Featured Book of the Week: The Five Dysfunctions of a Team by Patrick Lencioni Terry credits The Five Dysfunctions of a Team by Patrick Lencioni as massively influential in his career, particularly praising how Lencioni demonstrates that without trust as a foundation, teams cannot achieve anything else. The book's framework shows how lack of trust prevents healthy conflict, which prevents commitment, which prevents accountability, which prevents results. Terry found the way Lencioni illustrates these dysfunctions and their cascading effects to be incredibly valuable for understanding team dynamics and what's needed to build high-performing teams. In this segment, we also refer to Agile Software Development with Scrum, by Schwaber and Beedle. Self-reflection Question: What would happen to your team's dynamics if your most supportive, trust-building team member suddenly left tomorrow? [The Scrum Master Toolbox Podcast Recommends]

Terry Haayema: When Scrum Practices Aren't Enough - Learning to Sense the System 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 didn't know how to 'sense' the system. I was focused on the scrum practices, I thought when practices were there all would be fine." Terry shares a powerful failure story from his second engagement as a Scrum Master, where he discovered that implementing Scrum practices isn't enough if you don't understand the underlying system driving team behaviors. He describes how individual KPIs were causing conflict between developers and testers - developers were measured on fewer defects while testers were measured on finding more defects. This systemic issue created dysfunction that no amount of daily standups or retrospectives could fix. Terry learned the hard lesson that Scrum Masters must be coaches for both the team and the organization, understanding how metrics and structures shape behavior before trying to implement agile practices. Self-reflection Question: What systemic forces in your organization might be working against the collaborative behaviors you're trying to foster in your teams? [The Scrum Master Toolbox Podcast Recommends]

Scrum IS a Delivery Framework - NOT a Ceremonial CultThey say Scrum is easy to understand, hard to master.I'd say it's easy to misunderstand, and even easier to fake.Let's not talk about standups, reviews, or retrospectives just yet.Let's start deeper — from the inside out.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Tony Squires is joined by Wade Graham, Nathan Hindmarsh and Brent Read who previewed the game tonight between the Raiders and the Sharks with the news of Ethan Strange being ruled out. Plus, the latest coming out of the Roosters with Victor Radley's ban and can the Dogs cause as an upset against the Panthers? Plus, Ready's Mail, Tony's Quiz, Believe It Or Not along with plenty more!See omnystudio.com/listener for privacy information.

Shawn Dsouza: Beyond Product Knowledge—The Hidden Skills Every Product Owner Needs 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. Shawn explores both ends of the Product Owner spectrum through real experiences. On one side, he addresses the "Forced" or "Accidental" Product Owner—a common but problematic pattern where organizations appoint someone based solely on product knowledge. He shares the story of a QA professional thrust into the PO role who knew the product inside out but lacked other essential PO skills, frustrating the team with inadequate responses. Through coaching questions inspired by "The Advice Trap," Shawn helped this reluctant PO reflect on responsibilities and develop confidence beyond technical knowledge. The Great Product Owner: The Story-Crafting Superstar Shawn celebrates a Product Owner who elevated user story writing to an art form—"the Picasso of writing user stories." This exceptional PO co-crafted clear, well-structured stories with the team and used AI to refine stories and acceptance criteria. Her meticulous preparation included intensive refinement sessions before vacations and expert story slicing techniques. By handling requirements clarity superbly, she freed the team to focus entirely on problem-solving rather than deciphering what needed to be built. The Bad Product Owner: The Forced/Accidental Product Owner Organizations frequently make the mistake of appointing the person with the highest product knowledge as Product Owner, assuming technical expertise translates to PO effectiveness. However, the Product Owner role requires diverse skills beyond product knowledge—stakeholder management, prioritization, communication, and strategic thinking. When a QA professional was thrust into this role, their deep product understanding couldn't compensate for underdeveloped PO competencies, leading to team frustration and project complications. In this segment, we refer to the Coach Your PO e-course published by your Scrum Master Toolbox Podcast! Self-reflection Question: What skills beyond domain expertise should you develop or look for when transitioning into or selecting someone for the Product Owner role? [The Scrum Master Toolbox Podcast Recommends]

                                          Listen in as Erin and Jeff discuss: How Jeff's career as a fighter pilot, cancer researcher, and tech leader shaped the creation of Scrum. Why breaking work into small, prioritized pieces can eliminate 75% of wasted effort. The importance of “working with the willing” and creating a culture of commitment. How Scrum teams can quickly identify performance gaps and self-correct. Why adaptability and short feedback cycles are critical in the AI era … and much more.                                                  About Dr. Jeff Sutherland, co-creator of Scrum, is a global pioneer in agile methodologies. A West Point graduate and former U.S. Air Force fighter pilot, he flew over 100 missions in Vietnam, honing skills in adaptability and teamwork. After earning a Ph.D. in Biometrics and working as a cancer researcher, Jeff transitioned to technology, starting the first Scrum team in 1993 at Easel Corporation, naming it after Takeuchi and Nonaka's rugby-inspired concept. A signatory of the 2001 Agile Manifesto, he developed Scrum@Scale and founded Scrum Inc., training thousands to achieve double the productivity in half the time. His books, including Scrum: The Art of Doing Twice the Work in Half the Time and First Principles in Scrum, share his insights on building high-performing teams. How to Connect With Jeff Website: https://www.scruminc.com/ LinkedIn: https://www.linkedin.com/in/jeffsutherland Facebook: https://www.facebook.com/ScrumInc/ X profile: https://x.com/jeffsutherland YouTube: https://www.youtube.com/scruminc Recommended Resources  Book: Scrum: The Art of Doing Twice the Work in Half the Time: https://www.amazon.com/Scrum-Doing-Twice-Work-Half/dp/038534645X Book: First Principles in Scrum: Advanced Strategies and Reflections: https://leanpub.com/firstprinciplesinscrum Scrum Guide: https://scrumguides.org/

Shawn Dsouza: The Marathon Mindset—Building Agile Teams That Last Beyond Sprint Deadlines 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. Shawn defines himself as a "people-first Scrum Master" who measures success not through metrics but through daily interactions and team growth. He contrasts two teams: one that hit deadlines but lacked collaboration (unsustainable success) versus another that struggled with deadlines but excelled in conversations and continuous improvement (sustainable growth). For Shawn, protecting deep work and fostering genuine team collaboration indicates true success. He emphasizes that product development is a marathon, not a sprint, and warns that lack of meaningful conversations will inevitably lead to team problems. In this segment, we refer to the book Clean Language by Sullivan and Rees.  Featured Retrospective Format for the Week: Sprint Awards Shawn champions the Sprint Awards retrospective format, moving beyond viewing retrospectives as just another Scrum event to recognizing them as critical team development opportunities. In this format, team members give awards to colleagues for various contributions during the sprint, with each award recipient explaining why they were chosen. Shawn prefers face-to-face, offline retrospectives and always starts with ice breakers to gauge how the team feels—whether they feel heard and connected. He believes in experimenting with different retrospective formats since no single approach works for every situation. Self-reflection Question: How do you balance achieving deliverable outcomes with building sustainable team relationships and collaboration patterns? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach 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. Shawn faces the massive AI transformation currently reshaping the tech industry, acknowledging both its benefits and the fear it creates among professionals questioning their relevance. In his organization, he witnesses AI delivering wonders for some teams while others struggle and lose projects. Rather than viewing AI as an overwhelming wave, Shawn advocates for experimentation. He shares practical examples, like helping a Product Owner streamline story creation from Excel to JIRA using AI tools, and leveraging MIRO AI for team collaboration. His approach focuses on identifying friction points where AI experiments could add value while keeping conversations centered on possibilities rather than fears. Self-reflection Question: Instead of fearing technological changes like AI, how can you create small experiments to explore new possibilities and reduce friction in your current work processes? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: The Database Migration Disaster— Why Software Development Teams Need Psychological Safety Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Shawn worked with a skilled team migrating a database from local to cloud-based systems, supported by a strong Product Owner. Despite surface-level success in ceremonies, he noticed the team avoided discussing difficult topics. After three months of seemingly smooth progress, they delivered to pre-production only to discover 140 critical issues. The root cause? Unspoken disagreements and tensions that festered beneath polite ceremony facades. The situation deteriorated to the point where a senior engineer quit, teaching Shawn that pausing to address underlying issues doesn't cost time—it builds sustainability. In this segment, we refer to the episodes with Mahesh Jade, a previous guest on the Scrum Master Toolbox podcast. Featured Book of the Week: The Advice Trap by Michael Bungay Stanier Shawn discovered this transformative book when he realized he was talking too much in team meetings despite wanting to add value. The Advice Trap revealed how his instinct to give advice, though well-intentioned, was actually self-defeating. The book taught him to stay curious longer and ask better questions rather than rushing to provide solutions. As Shawn puts it, "The minute you think you have the answer you stop listening"—a lesson that fundamentally changed his coaching approach and helped him become more effective with his teams. Self-reflection Question: When working with teams, do you find yourself jumping to advice-giving mode, or do you stay curious long enough to truly understand the underlying challenges? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation 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. Shawn shares a powerful lesson about the importance of listening before implementing. Working with a young, talented team drowning in firefighting, he rolled out Scrum in "full" without taking time to understand the team's context. Going through the motions of Scrum ceremonies without genuine team ownership led to dropping energy levels and lost trust. The turning point came when Shawn realized the team had lost faith in his approach, prompting him to rebuild the process collaboratively with team ownership at its core. This story highlights how good intentions can backfire when we prioritize frameworks over people. Self-reflection Question: Before implementing any new process or framework, how do you ensure you truly understand your team's current challenges and context rather than jumping straight to solutions? [The Scrum Master Toolbox Podcast Recommends]

Bernie Maloney: Problems vs. Solutions: The Great Product Owner Distinction 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 Great Product Owner: The Strategic Problem Solver Bernie describes an exemplary Product Owner from a stealth program sponsored by a CTO, where the company needed to create new intellectual property. This Great Product Owner understood that Agile operates in three dimensions: most organizations only focus on outputs and delivery (first dimension), some reach outcomes (second dimension), but the truly great ones operate in the third dimension of strategic or business agility - defining problems worth solving. This Product Owner knew that high-performing teams need to understand what problem is worth solving rather than just receiving solutions to build. They embraced the Mobius loop approach, focusing on discovering the right problems rather than jumping straight to solutions. In this segment, we refer to the Mobius Loop, and to Steve Blank's work on the job of a startup.  We also refer to the episode with Elliott Parker on the critical importance of the “startup mindset” to foster innovation in larger organizations.  The Bad Product Owner: The Backlog Jockey with Authority Issues Bernie identifies the anti-pattern of Product Owners being treated as mere "backlog jockeys" by their organizations, which forces them into solution-building mode rather than problem-solving mode. These Product Owners don't understand the importance of saying "no" and lack clarity about intent and goals. The worst case Bernie encountered was a team manager who also served as Product Owner, wielding positional authority that shut down team communication. This person would interrupt daily scrums, causing teams to revert to waiting for direction rather than self-organizing. The combination of unclear intent and positional authority creates a toxic environment that destroys team autonomy and psychological safety. Self-reflection Question: Is your Product Owner focused on defining problems worth solving, or are they primarily managing a backlog of predetermined solutions? [The Scrum Master Toolbox Podcast Recommends]

Bernie Maloney: From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-Management 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. Bernie defines success for Scrum Masters as creating teams that can thrive and do their best work independently. His ultimate goal is to make himself unnecessary - developing self-directing teams that step out of waiting for direction and instead seek permission or even beg forgiveness when needed. Using the "Circles and Soup" framework, Bernie helps teams stretch their circles of influence and control. He recognizes that every manager wants teams to succeed but may lack the necessary tools, making it crucial for Scrum Masters to coach managers as well. Bernie recommends building a backlog of organizational impediments and focusing on the top priority that will move the ball forward most effectively. Featured Retrospective Format for the Week: Sailboat Bernie champions the Sailboat retrospective format for its simplicity and adaptability. While the basic format is straightforward, he appreciates that you can add layers of complexity as needed. Bernie tends to keep retrospectives simple and also mentions the "What the Duck?" technique as another valuable retrospective tool. He suggests incorporating creative elements like having people build LEGO representations of what they're discussing, which helps teams visualize and engage with concepts more effectively. To know more about LEGO Serious Play, check out the Serious Play book.  In this segment, we also refer to Dissociation in Psychology, which helps with "third position" coaching/thinking, and Bernie's video on creative retrospective formats.  Self-reflection Question: How are you measuring whether your teams are becoming more self-directing, and what specific behaviors indicate they're ready to operate with less guidance? [The Scrum Master Toolbox Podcast Recommends]

Bernie Maloney: Mastering Complexity Through Systems Thinking and NLP Coaching 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. Bernie addresses the constant challenge of mid-sprint changes by asking the crucial question: "what do you want to trade in for that new request?" His approach centers on recognizing that everyone is trying to do their best with what they have, using techniques from NLP and the three coaching positions to help people see the whole system. Bernie emphasizes rapport building as a key skill for Scrum Masters and warns against the anti-pattern of becoming judgmental when challenges arise. He advocates for moving from a plan-and-predict mentality to sense-and-respond thinking, highlighting the importance of conducting retrospectives once challenges are solved. Bernie's coaching philosophy revolves around helping people step into the "third position" - a dissociated perspective that enables better problem-solving and systems thinking. In this episode, we refer to Neuro-linguistic Programming (NLP), and to Instant Rapport by Michael Brooks, a primer on NLP. We also refer to the plan-and-predict vs sense-and-respond mentality. Self-reflection Question: How effectively are you helping your teams and stakeholders see the whole system when challenges arise, rather than just focusing on individual pain points? [The Scrum Master Toolbox Podcast Recommends]

In this episode, Adam and Cole go deep into their memory banks to give you the full experience by reliving the first time either of them did a studio scene. The assignment: Each of them will watch the other's scene, comment and review, and ask questions. What it was like, what happened, how it happened, and all surrounding circumstances. Simple, right? Of course, nothing is ever simple on set, especially when you've never done it before! First, Cole gives us a run down of Adam's debut in Hole 2, Adam completes the picture, and then Adam returns the favor by getting into Cole's introduction to the studio world in Scrum. Both Raging Stallion productions, both directed by the legendary Tony Dimarco. Every day in the industry is a story. Here are two pretty hot ones. Enjoy!Become a supporter of this podcast: https://www.spreaker.com/podcast/sorry-for-asking-with-adam-ramzi-and-cole-connor--5773495/support.

Bernie Maloney: The Triangulation Technique—Coaching Agile Teams Through Challenges 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. Bernie identifies critical patterns that cause teams to self-destruct, with lack of clarity about intention being the most common culprit. When teams are treated as mere "task workers" without clear vision, strategy, or goals, they become depressed and directionless. Some teams seek forgiveness after failed experiments, while others get stuck seeking permission without taking enough self-leadership. Bernie emphasizes that waiting for direction is fundamentally self-destructive behavior, and Scrum Masters must create safety for teams to reach high performance. He introduces the coaching technique of triangulation, where problems become a third point that coach and coachee examine together, side by side, rather than facing each other in opposition. In this segment, we talk about “What the Duck”, a Lego Serious Play workshop. Featured Book of the Week: Start with Why by Simon Sinek Bernie champions "Start with Why" by Simon Sinek as essential reading for Scrum Masters working to transform team culture. He explains that compelling stories are how leaders truly influence others, following the sequence of Attention-Emotion-Reason. This book helps Scrum Masters understand that their job fundamentally involves changing culture, and leaders must demonstrate the change they want to see. Bernie connects this to the broader leadership challenge of developing coaching and mentoring skills within organizational structures. During this segment, we also refer to the following books:  Drive, By Dan Pink Change the Culture, Change the Game, by Connors et al. The Secret Language of Leadership, by Denning Too Many Bosses, Too Few Leaders, by Peshawaria The Geek Way, by McAfee Right Kind of Wrong, by Edmondson   Self-reflection Question: What patterns of self-destructive behavior might your teams be exhibiting, and how could you help them move from seeking permission to taking ownership? [The Scrum Master Toolbox Podcast Recommends]

Bernie Maloney: The Power of Psychological Safety in Agile Teams Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Bernie shares a powerful story about learning what psychological safety truly means through both success and failure. Working in a high-pressure division with tight timelines and margins, Bernie discovered the transformative power of the mantra "always make a new mistake." When he made a significant error and was met with understanding rather than punishment, he experienced firsthand how psychological safety enables teams to thrive.  Later, facing a different challenge where mistrust existed between management and teams, Bernie had to navigate the delicate balance of maintaining psychological safety while addressing management's desire for transparency. His solution was innovative: conduct retrospectives with the team first, then invite managers in at the end with anonymized contributions. Bernie's approach of framing changes as experiments helped people embrace newness, knowing it would be time-bound and reversible. In this episode we refer to Neuro-linguistic Programming (NLP).  Self-reflection Question: How might your current approach to mistakes and experimentation be either fostering or undermining psychological safety within your team? [The Scrum Master Toolbox Podcast Recommends]

Mariano Gontchar: The Micromanagement Trap—When PO's Good Intentions Harm Agile Team Performance 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 Great Product Owner: The Visionary Leader During an agile transformation project modernizing a build system with multiple stakeholders, Mariano worked with an exceptional Product Owner who demonstrated the power of clear vision and well-defined roadmaps. This visionary Product Owner successfully navigated complex stakeholder relationships by maintaining focus on the product vision while providing clear direction through structured roadmap planning, enabling the team to deliver meaningful results in a challenging environment. The Bad Product Owner: The Task-Manager Micromanager Mariano encountered a well-intentioned Product Owner who fell into the task-manager anti-pattern, becoming overly detail-oriented and controlling. This Product Owner provided extremely detailed story descriptions and even specified who should do what tasks instead of explaining why work was needed. This approach turned the team into mere task-handlers with no space to contribute their expertise, ultimately reducing both engagement and effectiveness despite the Product Owner's good intentions. Self-reflection Question: Are you empowering your team to contribute their expertise, or are you inadvertently turning them into task-handlers through over-specification? [The Scrum Master Toolbox Podcast Recommends]