Kanban VS Scrum // Definitions, Pros & Cons || Crema

----
#Technology #BusinessStrategy #Workshops #UXDesign

Find us almost anywhere:

🚀 Crema is a design & technology consultancy that partners with global brands like Adidas, H&R Block, Miro, and Callaway. Headquartered in Kansas City.

[psgambat]

Best Kanban vs. Scrum explanation I have found to date! Thank you for just discussing the two vs. doing a tutorial.

[barbaraverlich]

This is one of the best, straightforward explanations of the two that I have come across. I would just add that organizations new to agile and lean methodologies most often need to work up to scrum by using incremental hybrid models; otherwise, organizational resistance to the change could be debilitating. For example, begin by using waterfall for overall project design, creating team Kanban boards with daily 10-15 min standup meetings, and then use the information from both to inform development of scrum stories and teams. I’ve found that people accustomed to using waterfall become very frustrated when thrown into a scrum environment as well as have trouble with forecasting and time management, so starting with a hybrid model helps them to better understand and acclimate to scrum while nurturing their ability to forecast as well as recognize the best approach for individual projects and/or stories.

[evelyndieppa]

Hi I'm a Scrum Master. I manage one dev team using Scrum and another one in Kanban. I really enjoyed your explanation! Great job!

[georgeabraham]

Wish I had as much confidence and vocabulary as them, especially Tuck!

[ryancroon]

I'm a little late with my comment, but you two did a fantastic job explaining. As a PM in the construction field, i have always struggled with explaining what methodology i have chosen for any given project, to the team. Your video helps bring those onboard. Cheers!

[slavanozhnik]

Thank you for this overview, a lot of good points. I would add that the most important aspects of Kanban are: being able to control WIP and identify bottlenecks. Also, while Scrum is an Agile methodology, Kanban is Lean, this is why they have fewer ceremonies and often do not bother estimating. However, it can only be beneficial if either the team is self-sufficient and knowledgable about the product and is able to communicate with each other well enough without daily ceremonies OR the workflow is unpredictable, like production support and priorities often change daily. That said, when I have Kanban teams, I do like to incorporate some aspects of Scrum, like standup, perhaps 2-3 times a week, retros about once a month.

[interestedbystander]

Thanks both for your clear knowledge and obvious enthusiasm for the topic(s). Very insightful and helpful points of view here, and great to hear some practical thoughts on how the frameworks work individually, and how they might complement each other together. I appreciate you taking the time.

[ghosty_w]

I'm in a Technical Project Management course and this was extremely helpful.

[RichardDavenport]

Really nice breakdown. And I love the wine theme, ha! I have a couple of suggestions for the kanban side of things (even though I'm currently a scrum bag...I mean master...). Kanban can actually give you more accurate projections, given it's a pull based system. It lends itself well to cumulative flow diagrams, how have things gone, and scatter plots, how will things go. Suggestion 1) One of the core properties of Kanban is that Work in Progress is limited. (this eliminates most of the "cons" for kanban). Suggestion 2) It's always easier to start work than it is to finish work (this reinforces why you have WIP limits). In Kanban, you shouldn't start work until the work in front is finished.

[maryb]

This video was super helpful! Thank you!

[Ennikvlogs]

an excellent way to explain KANBAN vs SCRUM.

[goksy]

Superb practical application and approach advices and recommendations. Appreciate what you guys are doing in a simple way. Thanks 😊

[jasonkelleher]

Great overview folks! Love the pros and cons of each and the comments left below. A nice slick production too.

[ProjectMgmtMadeSimple]

I see the education of Scrum or Kanban as the responsibility of the Scrum Master/Agile Coach. The Product Manager from my experience is more focused on the client relationship and priorities of work. The Scrum Master/Agile Coach is a neutral party that aides the team in improving their chosen process.

[artit]

You can also measure performance and velocity in Kanban.

select sum(points) from tickets where state = done and the date is between Monday and Friday.

This is it.

I don’t see scrum as the future of agile development, it’s more like a gamification thingy that leads to exhausted developers.

I personally prefer 6 hour working days with a Kanban board and select tickets from the top 10 of the backlog if you run out.

[krekoz]

Thank you so much for this. I work in QA and this is the best explanation so far.

[radharajagopalan]

A well-explained video, particularly liked your choice of words. Cheers!

[prynnuy]

By far the best video about the topic. Keep up the good work!

[sethwernick]

This is an excellent video. Very very helpful. Thank you both!

[MegaMuzak]

Kanban does allow teams to forecast by using throughput and cycle counts