<ul><li>Richard Brenner shares an important learning experience from introducing Kanban to teams using a top-down approach.</li><li>Without clearly articulating why the change was needed, team members questioned what they were doing wrong that necessitated change.</li><li>Richard emphasizes the importance of first understanding the problem before applying Scrum or Kanban and defining what success looks like.</li><li>Thorough contracting with client organizations is recommended to assess their current state and understand the reasons for change.</li></ul>

Richard Brenner: Skipping the Vision, How Not to Introduce Kanban

Discover more