The difference between Kanban and Scrum

Рет қаралды 18,931

Жыл бұрын

My Scrum Master Certification Guide is now available on Amazon!
Check it out here: amzn.to/3QmUQ0j
************
What's the difference between Kanban and Scrum? How do Scrum and Kanban compare?
In this video we take a look these two popular Agile frameworks and examine not only how Scrum and Kanban are different, but also how they can be used together to enhance the software development process.
We even get a chance to talk to a true expert in the field, David West, the CEO of Scrum.org, and learn how organizations are making the best out of both Scrum and Kanban together.

Пікірлер: 15

@cameronmcnz Жыл бұрын

Great look at the similarities and differences between Scrum and Kanban. Good to know that you can use both Kanban and Scrum together and not have to choose between them.

@ScrumOrg Жыл бұрын

Please note that Scrum is used well beyond software. It started in software and is now used in almost any type of product creation.

@scrumtuous Жыл бұрын

Indeed, as the Scrum Guide says, "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems." And that's any problem, not just the field of software development!

@robertoicardi713 3 ай бұрын

At first sight I tend to think that kanban is well suited for a team mantaining an existing product, while I see scrum more valuable in developing a brand new (and complex) product

@cameronmckenzie7188 Жыл бұрын

The difference between Scrum and Kanban has never been so clear. Thanks!

@scrumtuous Жыл бұрын

Thanks Cameron2. 🤣🤣🤣

@majed5006 5 ай бұрын

Very helpful insights, Thanks so much!!

@Mohika881 Ай бұрын

Good presentation. Thanks.

@vincentcaudo-engelmann9057 6 ай бұрын

My experience is that you can use the differing features of Kanban and Scrum in order to address the situation that you are in. if you are extremely time-strapped or are losing resources, go for Kanban. Kanban does not make you commit to a "sprint goal" (because there are no sprints). if you have a lot of work ahead of you that you know about, and you have a "due date" that is at least 4 weeks away, you might as well chop up that time into actual sprints. The reason WHY is because focusing on incremental goals WILL HELP you move forward at a better pace than just having a giant amorphous backlog, refined or not. It will also HELP THE PRODUCT be more robust as you are then able to deliver on sprint goals (when they are reached) and solicit feedback and test in those sprint increments. Scrum has the overhead of sprint planning. This overhead is easily seen: you need the time for the sprint planning meetings, and you need more relatively consistent development resources. Kanban does not have this overhead. The most important thing to keep in mind is that whether it is Scrum or Kanban, REFINEMENT REMAINS. Refinement is a heavyweight contributor to having a healthy team, a decent pace, and a product aligned with the desires of your stakeholders and the capacity of your team.

@shahid730 Жыл бұрын

Oooooh nice. Kanban is actually not a "framework" like Scrum is...which is why Kanban works well with Scrum. Kanban does have cadences like retros and reviews...but not sprint based as you said...glad to see more and more ppl getting out of that "Versus" mindset!

@scrumtuous Жыл бұрын

Yeah, it's touchy on how exactly you describe it, as some people reject 'process', some reject 'methodology' and some reject 'framework.' I just felt 'framework' was safe. Scrum definitely describes itself as a framework. Thanks for the feedback!

@krumbergify 10 ай бұрын

In reality most Scrum teams don’t follow it slavishly, especially not if a critical bug shows up. Some flexibility is always needed, but I do like that Scrums gives some stability and it is nice when the team is able to come together at the start and the end of the sprint.

@seektruth5750 8 ай бұрын

What’s the difference between a review and retrospective?

@MrDeeyal 7 ай бұрын

A review is where you review the work that's been done in the Sprint, usually along with the Stakeholders, and decide how to proceed next with the work in the backlog. A retrospective is where you look at how to improve as a Team. Are there things that you are doing that are not working, and so you will usually come out of this with some action points. It's also an opportunity to look a things that have gone well and come together as a Team and celebrate success