What’s your reaction to the title of this post? Do you get a sense of relief because you believe Scrum and Kanban can coexist? Or are you annoyed because you believe one approach surpasses the other and are solidly in the Scrum or Kanban camp?
Exploring how Scrum and Kanban might complement one other is, in my opinion, long overdue. My experience as a former Accredited Kanban Trainer and Coaching Professional, as well as my present work as a Professional Scrum Trainer and Scrum.org team member, has led me to this conclusion.
My opinion is that software teams are missing out on approaches that might boost their effectiveness since Kanban and Scrum practitioners have split into distinct camps.
Many of us who promote Scrum and Kanban have gained a better understanding of each technique and recognise that there are more parallels than differences between the two. Rather than wasting energy defending our respective camps, Daniel and I agree that working together on our common aim of assisting enterprises in providing extraordinary value to their consumers will yield greater results.
Why is it the right time to start a new Scrum-Kanban partnership?
Scrum recently celebrated its 21st birthday, which is the age of adulthood in many cultures. It’s a big milestone that typically serves as a catalyst for introspection. Over the last two decades, Scrum has accomplished a lot. Scrum is used by 90% of Agile teams, with a total of 12-15 million practitioners. Our commitment to the Scrum ideals, which were just introduced to the Scrum Guide, will ensure Scrum’s relevance for decades to come. Openness is one of these values. We should accept other good Agile approaches that complement Scrum when we become aware of them. It’s time to understand the benefits of Kanban’s techniques and see how our two approaches may work together to generate greater results.
From Daniel’s perspective, a push within the Kanban community to reconnect to its roots has reawakened a reinvigorated sense of inclusiveness and collaboration. “The Kanban community has drifted from its core goals of inclusivity, learning, and cooperation for a variety of reasons,” he says. “The Kanban community is analysing how we need to reorganise while looking at what makes other communities effective.” As a result, we’ve come to realise that we have a lot more potential in common with other groups than we previously realised.”
Making the Case
Daniel and I are going to see if we can improve our outcomes by combining our two ways. To begin, we’ll start with a blog post series that will teach the fundamentals of Scrum and Kanban, as well as how the various practices may improve each method.