The Agile Alliance briefly defines the Kanban Method as “a means to design, manage, and improve flow systems for knowledge work”. Kanban allows organizations to start with their existing workflow and drive evolutionary change. This can be done by visualizing their flow of work, limiting work in progress and embrace the concept of “stop starting and start finishing”.

Kanban is a tool to achieve greater transparency while upholding the agile values and principles. Transparency being one of the pillars of Empiricism, coming up with different ways to visualize the progress of a team have become an inherent need for all Agile teams. This empowers teams to see and assess the current state & pushes to think on what needs to be improved – holding onto the other two pillars of empiricism - Inspection and Adaptation. This has largely benefitted teams in identifying issues and bottlenecks faster, resulting into early resolution of impediments helping into reducing the “Cost of Delay”. Scrum, being the most popular Agile Framework, upholds the pillar of transparency and empowers teams by providing many tools to use within its framework. However, not all teams can best fit into the Scrum ways of working. This podcast includes a case study of how moving away from Scrum and embracing Kanban, with the same spirit of empiricism can help a team in improving delivery and bring a sense of togetherness across dependent teams.