What’s the Difference Between Kanban and Scrum?

Which framework should you use for your next project?

Tucker Sauer-Pivonka
Jan 31 · 7 min read

What is Kanban?

Kanban in its simplest form is a way to manage work by weighing requests with capacity. This agile framework originated from lean manufacturing, most widely associated with Toyota.

What is Scrum?

The base level definition of scrum is very similar to Kanban. Scrum, in its simplest form, is a way to manage work, but in a time boxed manner. The time boxes are most commonly referred to as sprints.

  1. What are you working on today?
  2. Do you have anything impeding your progress?

Pros & Cons of Kanban and Scrum

Middle Ground Options

Scrum and Kanban are both viable and successful frameworks to use in product development. However, you should never be afraid to go beyond what is outlined as ‘standard.’ This is why we call them frameworks, because they are inherently flexible.

What does Crema use and why?

Crema uses all of these frameworks! We more commonly use the Scrum framework on our heavy product development work, but use Kanban more commonly with our design and prototyping engagements. Sometimes, we even use the middle ground options listed above. Frankly, we use whatever framework or combination of frameworks that make the most sense for the engagement. Our Product Management team analyzes each and every engagement that comes through our doors to determine the best method to produce the greatest results.

What tools do we like the most for each and why?

Asana

  • Asana doesn’t really have a good way to use it for Scrum, but, it does work GREAT for Kanban style projects. As a product agency, we’ve used Asana for years and only recently had to begin to transition projects out that are prescribed a more Scrum style framework. You can learn more about how we use Asana in this blog post.

Jira

  • Jira is king for both Scrum and Kanban projects (and even projects beyond that). They’re the leading product development software used throughout the globe and there’s a reason for that. It’s incredibly robust and can handle pretty much any type of project you throw at it. That robustness does come at a cost though. Jira can be a lot to manage for newbies, but they’re doing a lot to fix that, including releasing an entirely new UI. I think we’ll see great things to come from Jira in the coming months and years.

Ora

  • Ora is a new player in the realm of digital product management, but they’ve really impressed us with their flexibility in nature. By default, Ora is set to manage projects within Kanban boards. However, their suite of options and features allow for teams with different preferences or goals to run their projects without restriction or prescription.

Summary

We hope you enjoyed this article about Kanban vs Scrum and hopefully come away with some clarity around the topic. If there’s one thing to take away, it would be that flexibility is key. Do what you need to do for your team to produce the best results and you’ll be set!


Ideas by Crema

All of our thoughts and ideas.

Tucker Sauer-Pivonka

Written by

Ideas by Crema

All of our thoughts and ideas.