Scrum Master Toolbox Podcast: Agile storytelling from the trenches Skipping the Vision, How Not to Introduce Kanban To An Agile Organization | Richard
Apr 14, 2025
Richard Brenner, a versatile technology leader and Agile Coach, shares his insights on introducing Kanban. He discusses the pitfalls of a top-down approach without a clear organizational vision, leading to resistance from team members. Richard emphasizes understanding the problem before implementing new methodologies and the importance of defining success. He also highlights the necessity of involving team members early in the change process and conducting thorough assessments with client organizations to align goals and foster acceptance.
AI Snips
Chapters
Books
Transcript
Episode notes
Top-Down Kanban Introduction
- Richard Brenner introduced Kanban to a department using a top-down approach, without explaining the reasoning behind the change.
- Team members felt frustrated and questioned the need for change, as they didn't understand its purpose.
Understand the Problem First
- Understand the problem before introducing solutions like Scrum or Kanban.
- Define what success looks like and involve people early in the change process.
Communicate and Contract
- Clearly communicate the "why" behind any change and define what you want to achieve.
- Spend sufficient time on contracting with the organization and the teams involved to ensure alignment.
