Scrum vs Kanban - What's the Difference?

Scrum and Kanban have much in common - and some striking differences. Watch the video... and grab your FREE CHEAT SHEET.

= = = = = = = = = = = =

New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"

= = = = = = = = = = = =


If you've been wondering about the differences between Scrum and Kanban, you've come to the right place.

Scum and Kanban are perhaps the best known of a number of Agile software development. They have much in common - and some striking differences.

And don't forget to grab your copy of the Scrum vs Kanban Cheat Sheet.

-------------------
68. Scrum vs Kanban - What's the Difference?
#ScrumVsKanban #AgileScrum #Kanban #DevelopmentThatPays

Scrum and Kanban are perhaps the best known of a number of Agile software development frameworks. Let's break that down: Software Development, in very broad terms, looks like this: The Product Owner decides what to build, The Development Team builds it, and Customers use it, experience it, benefit from it in some way. What makes software development Agile is that value is delivered to the customer in small increments. And - importantly - feedback is gathered from customers and fed back into the process. It's the Product Owner's job to take input from customers - and from various Stakeholders - and organise it into a prioritised list of features and User Stories. The list is known as the Product Backlog. What happens between the Product Backlog and the Customer is what distinguishes Scrum from Kanban. As we'll see, each has its own routines and rituals. It's this person's job (see below) to help the Product Owner and Development Team to adopt and maintain good habits. In Scrum, the role is known as the Scrum Master. In Kanban, the role is known as the Agile Coach. Something that Scrum and Kanban have in common is that both are PULL systems. Without getting into two much detail, a pull system ensures that work gets from Product Backlog to Customer in the shortest possible time. A pull system also helps to uncover bottlenecks in the process, which helps to ensure that work gets from Product Backlog to Customer in the shortest possible time! As you'll see in a moment, Scrum and Kanban implement the pull system in two strikingly different ways. Scrum ----- Scrum teams work in a series of Sprints, most commonly two weeks in length. Each Sprint it proceeded by a Sprint Planning Meeting, run by the Scrum Master and attended by the Product Owner and the Development Team. Together they select high priority items from the Product Backlog that the Development Team believe it can commit to delivering in a single Sprint. This is the "pull" I was talking about earlier. The selected items are known as the SPRINT BACKLOG. For the next two weeks, the Development Team focuses on working through the items in the Sprint backlog - and ONLY those items in the Sprint backlog: in all but the most exceptional circumstances, any new requirements that arise have to wait for the following Sprint. It's common practice for Scum teams to use a board to track the progress of the work. It's called a Scrum Board... or an Agile Board... or even (slightly confusingly) a Kanban Board. Each day during the Sprint there is a Scrum Meeting: it's a stand up meeting where the team takes a maximum of 15 minutes to discuss progress and identify any "blockers". At the end of the Sprint, the work completed during the Sprint is packaged for release, and any incomplete items are returned to the Product Backlog. The Sprint ends with two rituals: The Sprint Review, which is a demonstration of new functionality to Stakeholders. The Sprint Retrospective, which is an examination of what went well, what went badly and what could be improved. The aim of the Retrospective is to ensure that the next sprint is more efficient and effective than the last. And that's Scrum! Kanban ------ Kanban does a few things differently. There's no two-week sprint: Kanban is a continuous process. And there's no Sprint Backlog; the "pull" system in Kanban happens in a different way, via Work In Progress (WIP) limits. If an Agile Board is useful for Scrum, it's a necessity for Kanban. Each column on the Kanban Board has a Work in Progress limit related to the team's capacity. For example, a team with two developers might set a limit between two a

[Kajerman]

After watching this and the "Scrum Vs. Kanban" videos I've probably learned more in these past 20-25min than I did an entire semester.
Amazing what a good teacher can do with the help of some great animations.
Thank you, sir.

[nickfifield]

who on earth is giving this video a thumbs down? As an agile coach and scrum master, i can say it's short, sweet and very clear. great work!

[pickledparsleyparty]

This was really, really good. Not a second wasted, extremely easy to follow, and feels like it's pretty much a complete "talk the talk" lesson. Perfect.

[OgniiDev]

Incredible tutorial. I used to love SCRUM and the name Kanban was interesting to me. However the process of Kaban seems more interesting.

[konatsume]

I work as a Product Analyst and I can confirm this video outlines everything you need to know when differing between Scrum and Kanban
I watched this video with my mother and explained along the way how it all works, your examples and visuals were very helpful!

[nicholasbrown]

Awesome content, between this and the mini series kudos to you! All of my colleagues just received training on Agile + Scrum so it was up to me to educate myself. (since interns don't go to those cool workshops!)You definitely smoothed out the bumps in the road with the flawless story telling.

[omarfessi]

I have worked with both approaches, after coup, watching this tutorial enforces perfectly what I've learned from both of them and gives me more confidence explaining to people why it was better to use what it was decided to be used.
Thanks bro

[natashaelliott]

Finally I understand the key differences between these 2 Agile methodologies! This is the best video ever on this topic! Keep up this great work! Thank you!

[arijitmahalanabis]

This is by far the best, most clear identification of Scrum & Kanban & their resulting difference, & I admire so much is because of the little span of time within which the video encapsulates all this... Beautiful work @DevelopmentThatPays team & the narrator

[adityanambyar]

Thank you for such a brief and near-perfect explanation! I can't believe you covered all the essentials of scrum in less than 4 minutes. Great work!

[Developmentthatpays]

This video (thanks to some unexpected file corruption issues) took some late nights and some early mornings to put together. I hope you like it, and I look forward to reading your comments.

[stuwmcclure]

This was an exceptional video (and I watch hundreds each week)! You were clear, fast, and precise. You have an excellent delivery demeanor. Thanks so much, I will share this with the many Teams I work with...

[dejountaewashington]

By far the best description I've come across thus far. I had never even studied Kanban prior to this and got it almost immediately! Great job with this one.

[georgetirim]

2020 and this still is one of the best videos to learn agile development. Thanks for your contribution!

[pk]

Your videos on Scrum and Kanban are a top quality explanation. Great content and a great job fitting all the information in a short video, thanks!

[loquela]

Except the Cheat Sheet is is only free if you buy the course. The clue is in the name "cheat". Nice work!

[ezekielfrranks]

I can definitely agree on that last point. Over time your Kanban/Scrum process(es) will naturally evolve and may even borrow from both Scrum and Kanban. Excellent video!

[alichi]

I love how you are clear and explained everything simply

[deeptisachan]

I bet this is the easiest demonstration of Scrum vs Kanban on YT, which was short and crisp with covering every point. Thanks a ton for the amazing video and CHEAT SHEET.

[tlingit]

That's the clearest explanation of both Kanban and Scrum that I've yet seen. Thank you. Liked and subscribed.