Scrum vs Kanban | Differences & Similarities Between Scrum & Kanban

Scrum vs Kanban | Differences & Similarities Between Scrum & Kanban | Invensis Learning

Рет қаралды 419,293

Күн бұрын

This video on "Scrum vs Kanban" explains what is Scrum & Kanban. Then you will understand the differences and similarities between Scrum & Kanban. Areas covered:
1. What is Agile Software Development?
2. Agile Frameworks
3. Understanding Scrum & Kanban
4. Similarities Between Scrum & Kanban
5. Differences Between Scrum & Kanban
6. Applications of Scrum & Kanban
#ScrumVsKanban #ScrumAndKanban #InvensisLearning
Subscribe to our channel: bit.ly/3dmqNQS
Click here to check upcoming webinars on Agile Scrum: goo.gl/M9v8oP
About Invensis Learning:
Invensis Learning is a pioneer in providing globally-recognized certification training courses for individuals and enterprises worldwide. We have trained and certified 15,000+ professionals from 50+ courses through multiple training delivery modes.
Invensis Learning provides live online certification training on Certified ScrumMaster (*** www.invensislearning.com/csm-... ***)
Participants attending this CSM certification training will be eligible for 16 PDUs/SEUs and 2 year free membership with Scrum Alliance. They will also get a lifetime access to a Learning Management System which will contain all class resources like recordings and Ppts, along with access to Scrum Master webinars.
For more information please visit our website: www.invensislearning.com
Follow Us on:
Facebook: / invensislearn
LinkedIn: / invensis-learning
Twitter: / invensiselearn

Пікірлер: 109

@invensislearning9099 3 жыл бұрын

If you have any questions related to the topic mention it in the comments, our experts will reply back soon. If you want to become a Certified Scrum Master, checkout out our CSM Certification Training course: bit.ly/3qaUBrj

@popgugu 3 жыл бұрын

I do not see you mention SRM and SDM roles in Kanban. While you may think they are not required, wouldn't it better to mention them a bit? When I do some research I see many different articles mention about these roles.

@AmericaDreamUSA Жыл бұрын

In many of your videos you mentioned that Scrum is a methodology even though scrum is actually a framework not a methodology and this is actually one of the exam question if I'm not mistaking. Can you clarify?

@Brain_quench 2 жыл бұрын

This guy should get a medal. This was by far the most concise and clear PM content I have seen yet!

@RobbyRobinson1 Жыл бұрын

Couldn't handle the robo voice although it's one of the better ones that I've heard.

@davidowens9597 3 жыл бұрын

Another application difference is that Kanban tends to be better for small development teams than Scrum due to the required roles such as Product Owner and Scrum Master.

@tomiwasodeinde5107 Жыл бұрын

Thank you so much. I was really confused before watching this, you don't know how much you've helped.

@MukundVerma 2 жыл бұрын

Very clear and appropriate information. Thanks, it helped me a lot!

@GuiPurri 2 жыл бұрын

I so needed to learn this. I've been trying to do Scrum while learning what to do (and therefore adding new things in the middle of the workflow, causing Scope Creeping and driving myself insane)

@ianpatrick23 2 жыл бұрын

This is such a great explanation. Thank you!

@MirkoMicheleDimartino 2 жыл бұрын

Loved this. Thank you for sharing!

@minederien4194 11 ай бұрын

This must be the best learning video ive seen in my life. Thumbs up!

@alokjha780 3 жыл бұрын

Many thanks for this video!

@waniusza2 2 жыл бұрын

Awesome, thank you for this video!

@engineeringtips6520 2 жыл бұрын

i have been using Kanban in Automotive product development with Start up companies (recently a lot of them pup up in electromobility market)

@dafyc6298 Жыл бұрын

excellent video, clear and very ilustrative of the diferences. Thanks!

@MaryTheBIoodiest Жыл бұрын

My ADHD mind is floating away while I'm trying to listen this monotone voice... I get the concept of this vocalisation but I don't think it's natural or adapted to teach someone anything.

@LearningToCodeAndDesign Жыл бұрын

It works with people who are on the spectrum. They don’t precoces emotions in conversation well, so they like monotone.

@janemaschino8350 Жыл бұрын

In my opinion, this monotone voice is conducive for my method of learning (I get distracted easily). This is actually one of the better presentations I’ve seen in awhile … very concise. My time is valuable, and I came hear to get effective information. When I want to be entertained I choose entertainment.

@jeevan288 5 ай бұрын

It's an 'you' problem. For me , this audio has a calming effect.

@SwapnilDhabekar 2 жыл бұрын

Thanks for making this informative video.. in easy to understand way

@dr.dineshseth9518 2 жыл бұрын

Excellent comparison, it is short , to the point and offers a very good comparative picture. Please share videos -- how to apply in engineer to order environments ( engineering products situation) and how to apply in HMLV ( High mix and low volume) environments.

@vikashparihar8840 2 жыл бұрын

Thanks for the detailed information.

@fordford514 2 жыл бұрын

One of the best if not the best video I've seen on Kanvan vs Scrum. Learned a lot

@stillpickinganame5350 2 жыл бұрын

Thank you so much!! It was very helpfull!!

@marleenlewis2578 3 ай бұрын

Excellent video on the differences. Thanks for sharing.

@deepshaforlife 3 жыл бұрын

Thank you so much for this video, I have been working on agile environment from quite a long time now but today i came to know that we are using srcumban framework in our project 😂

@invensislearning9099 3 жыл бұрын

Glad it was helpful!

@Abhinav-ib2er 2 жыл бұрын

Heyy, can you help me??

@dianacb4965 Жыл бұрын

Thank you, great video!

@hainam1983 2 жыл бұрын

Many thanks for great video.

@rummanchowdhury3807 Жыл бұрын

The effectiveness of each method ultimately depends on the quality of the team members

@Sara.Saavedra Жыл бұрын

your video helped a lot, Thank you.

@Lt.WalterTull Жыл бұрын

Very good. Thanks for this

@zenagebrelmulunehbayleyegn3895 2 жыл бұрын

Very Good Lecture

@jhessicalmoreira 2 жыл бұрын

Excellent explanation. Thanks a lot!

@nelsonliew84 3 жыл бұрын

13:30 I have to point out that according to Scrum framework adheres to Agile Manifesto in which Scrum welcomes changes of requirements. Whether to pull the new requirements into the current sprint backlog is solely up to the developers.

@pm71241 2 жыл бұрын

Yet... the way scrum presents it self make it very easy for people to end up practicing it in a non-agile way. There are made rules about way too much in Scrum - and often they (unfortunately) are encoded in the tools you use (like JIRA) which makes any attempt to be pragmatic about it make your numbers be useless in the end. That said ... Kanban has it's weird rules too. The limit on WiP isn't a one-size-fits-all. I've seen project managers come in and demand that no-one can be assigned to more than 1 task at any time ... totally ruining the ability for developers to have an overview of the situation and fill in time where they are block by waiting for external feedback. Most of these frameworks have their own non-agile dogma ... and unfortunately they also build a culture around them where there's so much personal investment in the framework principles that stepping back and looking at it objectively becomes a personally sensitive exercise.

@MichoAngelos 2 жыл бұрын

@@pm71241 Just to respond to the WiP issue you have stated. In my team, we have 2 devs. The WiP is set to 2 items max (one for each dev), if they are blocked or wont be working on the item for some time, the item is moved over to the "blocked" column until unblocked. That way they can move to another task while waiting for the response etc. Also the "blocked" column has a limit of 6 items so that you cant "shove stuff under the carpet" indefinitely but would sound the alarm if something is wrong (e.g. the team is blocked on too many items). Agreeing with you on everything else you said.

@pm71241 2 жыл бұрын

@@MichoAngelos Well ... it can end up being a matter of definitions. Do the devs then unassigned themselves from "blocked" issues? (I'd find that a bit absurd). ... or do you just flag the issue as waiting for some external resolution and pick up something to work on in the meantime? ... in which case you haven't really a WiP of 1/dev, right?

@MichoAngelos 2 жыл бұрын

@@pm71241 Kanban is lot about visualisation. It's important for the team and stakeholders to quickly understand the state of the project / board and individuals' focus of the day. If you have 10 items in "In progress" column while actually just working on 2 while the other 8 are waiting for external resolution or info, what does that column differentiate from e.g. "Backlog" or "ToDo" column. It's unclear and misleading, to be honest. Kanban doesn't prescribe 1 dev 1 task per se (whatever the team is comfortable with), but points to a potential pain of not setting any WiPs where visually you cannot identify bottlenecks, priorities etc. There's also a functional issue of not having any WiPs e.g. if you work on 5 things in the same time and then push them all at once your QA will be smashed and the whole "factory" stops, work become unpredictable, pressure unbearable. Our WiP isn't set by PMs/POs but by the team themselves, they try and adapt to what works for them. 1 dev/1 task works for us atm, may not work for some other team, but having no WiPs won't work for anyone.

@pm71241 2 жыл бұрын

@@MichoAngelos Not sure that was a steelman of my position, ... but anyway - if you need something to visualize the state of things (and I deliberately don't write "the project", since that would assume there's only 1 project. That's not true everywhere). ... then it just highlights that that visualization tool is not the same as the tool a developer needs to keep track on the state of his things. I need to not unassigned myself from tasks just because I have to wait for someone to open a firewall somewhere. ... and I will find something else to do while waiting. ... and it might not even be on the same project.

@wajahatshah9489 Жыл бұрын

Brilliant you explained it so simple. Impressive...

@invensislearning9099 Жыл бұрын

Glad you liked it

@WildTraderAppeared 2 жыл бұрын

excellent !

@zizi5721 2 жыл бұрын

Same voice as movie recaps! Nice!

@visualpmpacademy2230 2 жыл бұрын

Great Job

@pamelangu9910 Жыл бұрын

Very helpful video.

@babyit1982 Жыл бұрын

Great videos that assisted me much

@invensislearning9099 Жыл бұрын

Glad to hear it!

@eugenechene1144 Жыл бұрын

This is great

@invensislearning9099 Жыл бұрын

Thank you for the feedback

@marcocoratella1556 Жыл бұрын

Amazing Kanban.... And how recycle scrum master PO and so on then?

@malahe2006 2 жыл бұрын

16:26 how do you apply Scrum to the construction industry?

@AnimeEmpress1 2 жыл бұрын

Kanban is better for continuous work that isn't project based. Eg kanban is better for BAU, esp when the work is volatile and new asks arise all the time

@ericli126 Жыл бұрын

7. KPI slide, for the Kanban chart, it should say 'Lead Time' instead of 'Lean Time'.

@farhanbachav4856 2 жыл бұрын

Based on this understanding, if I am dealing with CRs in telecom BSS stack.. Kanban would be more suitable?

@ronsmith745 Жыл бұрын

depends on the size / scope of the CR - it might start off as a simple /small change (kanban appropriate) - but morph into a larger scale (takes months and/or rely on external vendors / suppliers) - be more of a project.

@prisinha 2 жыл бұрын

Is it conflicting 13:00 About Kanban vs 13:14 about Scrum, if not, how

@rics6035 2 жыл бұрын

Story recap here… I mean, nice voice!

@alii4334 Жыл бұрын

is there a way to download the slides as a PDF?

@bichoron3603 Ай бұрын

Can i get any powerpoint of pdf of this conversation ??

@erictsang789 Жыл бұрын

I would like to ask "Agile Software development "it refers to Software as in IT field.

@RU-qv3jl Жыл бұрын

So apart from that you described scrum with using a kanban system for the sprint board, which by common nomenclature would make it scrumban and didn’t actually explain what the fundamental difference is you’re not far off. Scrum is an empirical process management methodology and Kanban is a change management system. There is a difference and whilst both can be used to run a project like you described that’s not actually what they are. Kanban makes the most sense when combined with something like lean/systems thinking. Kanban is also far more adaptable than scrum.

@rogeriopenna9014 9 ай бұрын

When you only show Kanban as "todo, in Progress and Done", you lose the main difference of Kanban, which is using it to visualize all the tasks in a process. You can have kanban boards with 7, 8 or more columns, each representing a task in the process.

@adreyeveson7900 Жыл бұрын

How can I download yet am not using WiFi

@Seelenverheizer 2 жыл бұрын

more like ad for scrum.

@marsolinantonio8966 2 жыл бұрын

I’m in construction industry trying to get PMP Certified. This is sooo confusing.

@questtech2698 2 жыл бұрын

Are scrum and agile included in the scope of PMP? They are for PMI-ACP certification as far as I'm concerned.

@jayleimer3836 2 жыл бұрын

Love how the thumbnail is wrong

@mmohan1234 3 жыл бұрын

So many spelling mistakes in "Scrum vs Kanban" slide . Pls correct them . Except this all the other content is well organized.

@nataliamanoura3052 Ай бұрын

Wow! One of the best videos I’ve seen to describe the difference. Thank you

@turkosmopolit633 2 жыл бұрын

Scrum is a framework of proccesses. Kanban is used to be a part of SCRUM. Its like comparing tires with Cars.

@hivee3044 2 жыл бұрын

Wrong kanban is not a part of scrum at all...

@turkosmopolit633 2 жыл бұрын

@@hivee3044 Scrum is an agile process that allows us to focus on delivering business value in the shortest possible time. Kanban is a visual system for managing software development work. ... Scrum prescribes iterations in time windows. Kanban focuses on planning a different duration for each iteration. Thus, Kanban can be described as a subset of Scrum.

@hivee3044 2 жыл бұрын

@@turkosmopolit633 right until the last sentence... Kanban is clearly not a subset of scrum for many reasons. It doesn't work the same at all nor does it aims at working with the same objective in mind. Kanban precede scrum by far in its creation and it comes from lean methodologies, made up in Toyota's factory and adapted for IT... Kanban is used in scrum for its visualisation which scrum lack in its native form and even that is called scrumban... It's nice to want to look smart but you should read about the subject and not just go on think about stuff and building wrong opinions out of your thoughts.

@hivee3044 2 жыл бұрын

@@turkosmopolit633 also, one more thing, kanban is not a subset of scrum, it's quite the opposite, scrum is a subset of kanban as you can parameter your kanban system and make a scrum with it. Scrum is one way to do kanban, not the best at all though but kanban is much broader than scrum.

@hivee3044 2 жыл бұрын

@@turkosmopolit633 and again just to show that you should really read up on kanban, there's no time window. It's wip is definef by the number of task an activity can handle and the whole system cannot be faster than the slowest activity. Its wip can also be defined with time, which is where you can implement scrum with kanban, but it is rarely done.

@dmitryzvorikin Жыл бұрын

7:25 and 8:20 why do you say the same twice?

@jenglong7826 2 жыл бұрын

Is this the same guy that voices Movie Recaps?

@zizi5721 2 жыл бұрын

I was about to say!!

@codehorror8076 Жыл бұрын

Nobody going to cater for the solo developer? We don't all work in teams you know, and we would love to manage our projects in an organized way.

@simphiwentshangase8322 Жыл бұрын

I have a similar issue but I think Kanban is the way for smaller teams

@hivee3044 2 жыл бұрын

Scrum is not a pull system... It's a push system... 1st thing you say in the video is dead wrong... Can't wait to see the rest.

@MarkUKInsects 2 жыл бұрын

It is a pull system. You need to look at push and pull from a Lean prospective.

@hivee3044 2 жыл бұрын

@@MarkUKInsects wrong it's a push system, you need to open a book about kanban for example that tell you kanban is a pull system vs scrum that is a push system...

@MarkUKInsects 2 жыл бұрын

@@hivee3044 So make something no one wants? Or is there a customer waiting for it?

@hivee3044 2 жыл бұрын

@@MarkUKInsects what?

@mboehmer Жыл бұрын

The content seems to be good, but I couldn't stand the computer voice. So I had to stop the video. A real voice (or two) would really make this a good video

@TheSpaceVoid 5 ай бұрын

Kanban is not an agile methodology

@dmitryzvorikin Жыл бұрын

What is Scrum, what is Kanban? 4:34 I am sure you guys know what Scrum is. Hey, if I knew that I would not come here.

@ramonbs6075 2 жыл бұрын

Scrum is more likely a religion, too much of their own words. I prefer Kanban.

@foodnstuffz 2 жыл бұрын

The content of your videos is good but please, please stop using the annoying voice 😫

@mohieali7317 2 жыл бұрын

Reading from paper is NOT a presentation !!!!! it sucks !!!!!!!!

@shanksmare8 Жыл бұрын

You should have an English speaker reading this and not TTS software

@tenminutetokyo2643 3 жыл бұрын

Agile creates chaos. Don’t drink the Kool-Aid.

@LearningToCodeAndDesign Жыл бұрын

So what’s better than agile?

@tenminutetokyo2643 Жыл бұрын

@@LearningToCodeAndDesign write down a list of features, assign tasks, get shit done.

@LearningToCodeAndDesign Жыл бұрын

@@tenminutetokyo2643 And that's the point of Kanban. So how is that any different?

@Moufosboufos 5 ай бұрын

The critical points on KanBan are completely biased and unfounded. KanBan can incorporate a scrum master, product owner and cross functional roles just like Scrum and then it becomes a super powerful framework where needed. Very poor and shallow misrepresentation of the process.

@B0r0d4Mik 2 жыл бұрын

Bullshit. No WIP concept is in the Scrum guide. It is unnecessary practice for scrum. You didn’t mention some of the crucial concepts of scrum. They are product goal and sprint goal. You described planning process as just pulling some items from a product backlog. But firstly a scrum team has to define a sprint goal. And only after that the team can pull needed items. As for Kansan it is a bad idea to visualize work in those three columns you showed. To do - In progress - Done. The main idea of WIP concept is to find bottlenecks in a workflow. For that purpose it makes sense to split all flow into typical development steps. For example: To Do - Design - Programming - Testing - Delivery - Done. In that approach you will clearly see where problems take place. If a QA department can’t handle current volume of work? If programmers aren’t able to develop all written designs? And understanding of it will help you to act and to solve problems. Not yours “in progress” column. 14:48 Lead time, lean time: never mind, you don’t want to be precise. These idiots on KZfaq will be happy anyway. I don’t understand why people who don’t get the core ideas of any methodologies or frameworks just fool other people.