Should your team do Kanban instead of Scrum?

So your team wants to use Kanban instead of Scrum?

Here is what you need to know!

◻◻◻◻◻

Subscribe to my YouTube channel to never miss another video!

◾ ◾ ◾ ◾ ◾

◾ ◾ ◾ ◾ ◾

✨ MY FAVORITE TOOLS ✨

◾ ◾ ◾ ◾ ◾

👋 Follow me and ScrumMastered on social media:

❗ DISCLAIMER
If you are using my affiliate links I will make a small commission on the sales made. This has no additional cost to you.

[scoogsy]

We use Kanban at work, and I really enjoy it’s focus on the clear visualisation of value delivery. However, you are right. Introducing WIP limits was shocking to the team, as well as the “pull “ mechanism.

- “Hold on I can do ten things at once”
- “wait, I’ll never get anything done if you only limit me to three things in progress”
- “oh no you can load our guys up with heaps of work, that is normal”
- “oh yeah that thing is almost done, but other priorities have come up so we’ll get back to that item some day”
- “once I’m done, I just drop it in that guys queue, and that means he’s doing it now”

Wrong wrong wrong wrong wrong! 😂

It takes a big mind shift to go Kanban (properly). It’s great to do it, and there are good reasons why Kanban is done the way it’s done, but it has very clear rules.

[TheAgileBroadcast]

Great little tip! Love it!

oh you want to do Kanban because it's "easier"... alright let me teach it to you and show you how "easy" it really is (not).... brilliant ;-)

[factormovil]

I don’t agree. If a team wants to switch to Kanban from Scrum, a training session, per se, may not work, just start introducing them to the method slowly, take baby steps.