Kanban is the new Scrum! The Reasons Not to Adopt Kanban
You are in charge of a whole organization or a number of teams. Your ultimate desire is for them to become more productive, which translates into effectiveness and/or efficiency. You would ask yourself which is a golden key here, Kanban or Scrum? Is it an either/or question? Shall you start by practicing Scrum for a while and switch when matured? Is there a golden ratio of Scrum practices v.s. Kanban that make your transformation successful? Do you find yourself in Scrumfalls? Is Kanban the magic solution? You are telling yourself: It's time to switch to Kanban. Others have done it, so it must be the magic solution. If that's you, most probably you are spending now time and money on a new "method" while barely moving the needle. I can assure you It can become successful, it has been done!
Kanban is the new Scrum these days. Let's look at the failure modes of adopting Kanban deeper and together. What are the conditions needed for a Kanban method to flourish and find its roots in an organization? What can lead to a successful Kanban introduction compared to Scrum? Are there any fundamental differences between them? How can you make sure if you are moving from Scrum to Kanban, or having the thought of it, to become successful? What are the pitfalls that you want to avoid?
Join me in this session to share with you my experience as both Scrum and Kanban coach helping organizations transform. I will be sharing lessons learned and coaching techniques to help organizations and leaders realize the true potential of Kanban.
Outline/Structure of the Talk
- Introduction of myself, Kanban and Scrum [5 min]
- Case Study 1 - Scrum fails, let's move to Kanban [10 min]
- Scrum is not working any more at the team level. It used to work, we got matured in it. A good reason to move to Kanban.
- Case Study 2 - Kanban is good for only some type of work [10 min]
- We adopt Kanban based on the nature of the work. That's a good and only reason to adopt Kanban: Nature of the work; for example the production support system. What can go wrong then?
- Case Study 3 - Transformation Failure [10 min]
- Transformation Team run as a Scrum and they failed. They are now thinking of using Kanban. The "head coach" is in favour of moving to Kanban. The rationale is that we don't need to be time-boxed as in Scrum.
- Closing - [5 min]
- A discussion and handout containing Kanban adoption failure modes.
- An introduction to Kanban and Scrum
- An introduction to fundamental differences between Scrum and Kanban, their philosophy and lenses
- Kanban Failure modes, or why not to adopt Kanban
- Requirements for Kanban to flourish (through real life scenarios, and stories of success and failures)
- How to rely on Kanban or Scrum or none, when and how to approach the challenge on hand
Kanban Enthusiasts, Agile Coaches, Scrum Masters, Leaders, Managers
Prerequisites for Attendees
Some knowledge of Scrum and Kanban is helpful. I am going to introduce them at the start as well, but I won't have much time to spend and dig deep.