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

Подписаться 99 тыс.

Просмотров 420 тыс.

50% 1

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

Опубликовано:

22 июн 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 110

@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?

@RobbyRobinson1 Год назад

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

@Brain_quench 2 года назад

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

@peosjohn2935 День назад

One of the best videos I have come across on this Topic. Great work, thank you!

@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!

@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.

@ianpatrick23 2 года назад

This is such a great explanation. Thank you!

@MirkoMicheleDimartino 2 года назад

Loved this. Thank you for sharing!

@alokjha780 3 года назад

Many thanks for this video!

@waniusza2 3 года назад

Awesome, thank you for this video!

@vikashparihar8840 2 года назад

Thanks for the detailed information.

@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)

@SwapnilDhabekar 2 года назад

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

@dafyc6298 Год назад

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

@stillpickinganame5350 2 года назад

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

@minederien4194 11 месяцев назад

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

@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)

@hainam1983 2 года назад

Many thanks for great video.

@dianacb4965 Год назад

Thank you, great video!

@marleenlewis2578 3 месяца назад

Excellent video on the differences. Thanks for sharing.

@zenagebrelmulunehbayleyegn3895 2 года назад

Very Good Lecture

@Sara.Saavedra Год назад

your video helped a lot, Thank you.

@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.

@Lt.WalterTull Год назад

Very good. Thanks for this

@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??

@wajahatshah9489 Год назад

Brilliant you explained it so simple. Impressive...

@invensislearning9099 Год назад

Glad you liked it

@WildTraderAppeared 2 года назад

excellent !

@pamelangu9910 Год назад

Very helpful video.

@visualpmpacademy2230 2 года назад

Great Job

@rummanchowdhury3807 Год назад

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

@fordford514 2 года назад

One of the best if not the best video I've seen on Kanvan vs Scrum. Learned 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.

@jhessicalmoreira 2 года назад

Excellent explanation. Thanks a lot!

@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.

@babyit1982 Год назад

Great videos that assisted me much

@invensislearning9099 Год назад

Glad to hear it!

@zizi5721 2 года назад

Same voice as movie recaps! Nice!

@eugenechene1144 Год назад

This is great

@invensislearning9099 Год назад

Thank you for the feedback

@malahe2006 2 года назад

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

@marcocoratella1556 Год назад

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

@ericli126 Год назад

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

@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

@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.

@alii4334 Год назад

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

@prisinha 2 года назад

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

@bichoron3603 Месяц назад

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

@rics6035 2 года назад

Story recap here… I mean, nice voice!

@erictsang789 Год назад

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

@adreyeveson7900 Год назад

How can I download yet am not using WiFi

@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.

@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.

@mmohan1234 3 года назад

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

@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.

@nataliamanoura3052 Месяц назад

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

@Seelenverheizer 2 года назад

more like ad for scrum.

@jayleimer3836 2 года назад

Love how the thumbnail is wrong

@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!!

@TheSpaceVoid 5 месяцев назад

Kanban is not an agile methodology

@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

@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.

@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

@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?

@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 😫

@shanksmare8 Год назад

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

@mohieali7317 2 года назад

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

@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.

@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?

@PaddyFullyRandom Год назад

Please no more computer-generated voices. It's so hard to listen to and keep paying attention. You can pay a narrator. Or become one.

@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 RU-vid 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.