Scrum and kanban are both agile practices/frameworks. They have evolved over the years to address specific challenges around organizing work.
Related Article: The Key Values and Principles of the Agile Manifesto
Many teams and organizations have often leveraged a combination of practices from both scrum and kanban, sometimes to work to their advantage, sometimes not so much. So, the questions often arise: When should we use scrum versus when should we use kanban? Can scrum and kanban be used interchangeably for any and every project? Or are there complimentary practices in both that can be leveraged as a combination?
First of all, if we combine practices from scrum and kanban but do not apply the entire framework, we are neither doing scrum nor kanban. We are doing something, but it is neither of the two. We may also reap some benefits of the practices, but not what we will get from complete implementation of scrum or kanban.
Having said that, let's compare scrum vs kanban against various attributes to understand the types of projects in which each may be used. The table on the next page summarizes the attributes of both scrum and kanban and highlights the types of projects in which they may be used based on that attribute.
Related Article: Collaboration Between Teams Using Different Process Models
About the Author
Scrum Alliance Certified Scrum Trainer® Punita Dave has been working with scrum and other agile practices for almost 20 years and has successfully transformed more than 100 large, mid-size, and small companies and has trained more than 6000 people. She has pushed the boundaries of agile and scrum beyond software: hardware, data centers, finance, marketing, medical, food, and real estate industries. She remains passionate about changing the way organizations, businesses, and people work.