Kanban vs SCRUM

Categories: Agile | Software Product Development |

Have you ever wondered what the best agile methodology is? Even though you may not need to make a decision right now, you probably want to understand how each methodology can help you.

I wanted to share with you a brief comparison between 2 trending agile methodologies. Each one has its own evangelists dedicated to preach about the advantages and functionalities that makes one better than the other. But… which is the one that fits your needs? What’s the most adopted methodology world-wide?

I’ll start with a brief overview of the differences between them so we can understand each one and choose the one that suits the most with your project.

cuadro Kanban-Scrum

¿Which one is better?

It all depends on the context and needs. Scrum has more restrictions than Kanban because it requires iterations and self-organized teams among others. Kanban is closer to “do whatever you want”, although this seems to be very agile, it’s also true that the lack of limits and clear rules makes team management more difficult.

Shorter iterations lead to Kanban. Once you start talking about doing iterations shorter than a week, you should consider moving off from closed time iterations.

Regarding daily meetings and retrospective meetings, I strongly recommend having them in both methodologies.

This is a hot topic today, with many more discussions needed.  Share your comments and opinions in this post!

For more insights on KANBAN vs SCRUM, read the full whitepaper here. 




    I think Kanban is for continous delivery in pace cadence. If I only talk about Kanban, despite WIP is a “limit” and also a “clear rule”, It would be more manage-able as a process, if we complement it with Scrum abstract estimation (Story-points based).

    Hi Walter,

    Despite using story points in Kanban is a valid option, you also have a Kanban specific metric called Lead Time (time between request and delivery). Both metrics will tell you how much work (in average) can be delivered given a due date. If you divide work into chunks of similar effort, your Lead Time will be more predictable.