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.
Richard shares an important learning experience from introducing Kanban to teams using a top-down approach. Without clearly articulating why the change was needed, team members questioned what they were doing wrong that necessitated change. Richard found himself unable to connect the organizational vision to the methodology shift, leading to resistance. He emphasizes the importance of first understanding the problem before applying Scrum or Kanban, defining what success looks like, and involving people early in the change process. Richard also recommends thorough contracting with client organizations to assess their current state and understand who is trying to change what, and why.
In this episode, we refer to Kotter’s book Leading Change.
Self-reflection Question: How might your change initiatives be improved by spending more time defining the "why" before introducing new methodologies?
🚀 Global Agile Summit 2025
Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories.
🌍 Connect with global Agile leaders.
💡 Learn practical strategies for impact.
🔥 Break free from Agile fatigue and <strong>become a Pragmatic Innovator</strong>.</p>
About Richard
Richard is a versatile technology leader with experience as a Software Engineer, Product Owner, and Agile Coach. Passionate about building software that excites, he thrives at the intersection of technology, change, and leadership. Lately, he's focused on Collaborative Modeling, bridging disciplines to drive innovation and create meaningful impact.
You can link with Richard Brenner on LinkedIn.