5 REASONS WHY KANBAN IS BETTER THAN SCRUM 🤯

preview_player
Показать описание

Here's what we will cover:
- What is Kanban?
- Did Taiichi Ohno create kanban?
- What is the kanban guide and how to download it?
- How does kanban compare to scrum
- Should you use kanban instead of scrum?
- Why kanban is better than scrum
- Do scrum teams use a kanban board?
- Can scrum teams use kanban?
- Why you should use kanban, what are the benefits of using kanban?
- What are the pros and cons of using kanban?
- How to use kanban?
- Kanban tips
- Kanban tricks
- Is kanban agile?

What this channel is about:
The #1 place on YouTube for all things Agile.

This channel explores:
- Agile methodology, principles and value
- Agile advanced scrum masters training
- Scrum developer, scrum product owner
- Kanban, Extreme Programming (XP)
- Agile project management and software development
- Agile SAFe
- etc.

I want to hear from you. Please ask your question, provide feedback and give your point of view on the topic in the comment section below. Thanks for your support
Рекомендации по теме
Комментарии
Автор



I want to hear from you. What topic do you want me to cover next?

agilecoach
Автор

Can you make a video of you using kanban vs scrum in your everyday life outside of work to paint that clear picture. Just random stuff goals or chores that you have to do through our the week/month etc

IlllIlllIlllIlll
Автор

Scrum is a framework, and i often use Kanban like in it?
So i dont use Kanban instead of scrum, is use kanban in some version of Scrum or scrum like / Scrum Lite.

So i wonder what you think Scrum is?

michaelk.jensen
Автор

Ok, my first thought is that a Scrum team is not estimating for itself, but for the stakeholders. Yes I agree, estimations are a waste of time, but what can you do? I am a Scrum Master, and I argue against estimations every time it come up, but I the end of the day it comes down to how much time and energy I/we should spend on fighting it instead of giving the stakeholders "something".

Second: I believe it's said that one of the killers of productivity is WIP (work in progress/process). If you do not practice the Planning meeting in Kanban and "just pick up work" whenever you are available, there isn't a risk that you come to a point in the progress/process where you figure out that you are blocked. So then you put the task aside and start on something new, and therefore build up a huge amount of WIP?

I could be wrong, and I have not worked with Kanban before. :)

StianGlundberg
Автор

I don't see Scrum as an Agile method, It is just a micro waterfall repeated every sprint! I like Kanban because it is easy to use and more flexible (Agile), but the problem is always with managers, they have ruined the Kanban as they did with Scrum, they have mixed Kanban with the bad Scrum and made something worse called Scrumban!

maometos