You are in charge of a whole organization or several teams. Your ultimate want is for them to become more productive, which translates into effectiveness and/or efficiency for your organization. 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 a magic solution. If that describes you, most probably you are investing time and money on a new "methodology" while barely moving the needle.

Kanban is the new Scrum these days, or is it? Join me on this session and let's look at the failure modes of adopting Kanban deeper. 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?

I will share with you my experiences and perspective as both Scrum and Kanban coach helping organizations with their Agile Transformation. I will be sharing lessons learned and coaching techniques to help organizations and leaders realize the true potential regardless of which you chose.


Outline/Structure of the Experience Report

  • Introduction of myself, Kanban and Scrum [5 min]
  • Case Study 1 - Scrum fails, let's move to Kanban [10 min]
    • Scenario: 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]
    • Scenario: 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]
    • Scenario: 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.

Learning Outcome

  • 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

Target Audience

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.

schedule Submitted 1 year ago

  • 90 Mins

    Today, product teams are under pressure to be more creative, innovative and delight customers sooner, but lack the knowledge and skills to know where to start. Agile product teams have frameworks and methods for rapid feedback, but generally lack real data from real users to make good business decisions. As product release cycles run long, team members lose enthusiasm and their focus on the customer.

    As a tool, design sprints offer Agile teams an effective and transformative formula for testing ideas with real people, whether you're on a small team at a startup, or inside a large portfolio of projects at an enterprise organization. Within five days, teams move from idea to prototyping to better business decisions, ultimately saving time, effort, and energy over the long-run. Join Carlos Oliveira as he introduces design sprints for product teams, a process for rapid experimentation and learning that helps teams solve big problems and test new ideas in less than five days.

    Originally created by three partners at Google Ventures, the process has been proven at hundreds of companies. Carlos has run dozens of design sprints for the Fortune 500 and firmly believes that product teams can benefit and harness the power of design sprints to focus their efforts and deliver more appropriate solutions to market sooner.

  • 40 Mins
    Experience Report

    Project delivery is complex and subject to numerous sources of delay and risks. In this talk we explore why software delivery struggles due to technical constraints between a web of teams. Most importantly, what techniques can be applied to simplify delivery and improve time to market. This includes a real world case study where System Thinking techniques are utilized to achieve amazing customer outcomes.