Turbocharge your Scrum with Kanban

Has your Scrum implementation failed to reach the expected benefits or stalled out? You’re not alone – Jeff Sutherland, co-founder of the Scrum Framework has stated that 58% of Scrum implementations fail. The Kanban Method can help.

Too often I hear people ask whether they should use Scrum or Kanban, or they try to make a comparison between Scrum and Kanban. This is a flawed comparison seeing each as a competing framework. Scrum is a framework that provides intentionally incomplete guidance for product development. In contrast, the Kanban Method is a management method for evolutionary change, or an unframework. While Scrum usually involves a transformation and a reorganization to create the teams and roles, the Kanban Method starts with what you do now and provides management guidance on continuous improvement through evolutionary change. The Kanban Method can be applied regardless of whether you are starting from waterfall, Scrum, SAFe, or chaos.

If you have already transformed to Scrum, then applying the Kanban Method simply means starting with Scrum and applying the 3 change management principles, the 3 service delivery principles and the 6 general practices to your Scrum. These principles and practices have significant overlap with the Scrum Framework.

Join Todd as he shares how these principles and practices of the Kanban Method look from a Scrum perspective and what a Scrum team can do to utilize the Kanban Method to improve their Scrum. Through a case study Todd will show the Kanban Method can turbocharge your Scrum.