Kanban or Scrum? with Dan Neumann

This week, Dan Neumann, your host, is answering a very common question: Why would an organization use Kanban or Scrum?


In this episode, he explains the benefits of both approaches, describing each of them and identifying which of them is more suitable for an organization.

Key Takeaways

• ● The kind of work an organization is doing will define the methodologies or approaches to take.

  • ○ Scrum is an excellent framework for organizations that are doing complex work, as it is creating software.

  • ○ If you are in conditions of uncertainty, you want to deliver value frequently, and de-risk your approach, a Scrum framework is the most applicable.

  • ○ The Kanban method is more thana board with signs and signals.

  • ○ The Kansan method is a disciplined approach. It includes making status clear, articulating clear policies, set work in process limits, measuring and manage flow, and then make incremental improvements over time.

• ● Scrum or Kanban: A false choice.

  • ○ Both can complement.

• ● Why Scrum?

  • ○ It works!

  • ○ Scrum is clearer than Kanban about rolls, events, and artifacts.

  • ○ Be cautious, there are people using Scrum immaturely and not to its fullest benefit.

  • ○ It is much easier to find employees using the titles in the Scrum framework.

• ● Why Kanban?

  • ○ With Kanban, organizations start where they are.

  • ○ The Kanban method is great for creating transparency and supporting experiments for how you want to improve the flow of work.

  • ○ The Kanban method can be applied at many different levels and related to other groups within the organization.

• ● How long can your organization maintain focus?

  • ○ Kanban fits better for organizations that are doing work that is frequently changing priorities.

  • ○ Scrum looks to support a product goal, and focus is maintained for longer periods (three to four weeks sometimes).

•  

• Want to Learn More or Get in Touch?

• Visit the website and catch up with all the episodes on AgileThought.com!

• Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!