Kanban or Scrum? with Dan Neumann

Published: June 3, 2022, noon

b'

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

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.

\\xa0

Key Takeaways

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

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

    • \\u25cb 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.

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

    • \\u25cb 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.

  • \\u25cf Scrum or Kanban: A false choice.

    • \\u25cb Both can complement.

  • \\u25cf Why Scrum?

    • \\u25cb It works!

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

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

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

  • \\u25cf Why Kanban?

    • \\u25cb With Kanban, organizations start where they are.

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

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

  • \\u25cf How long can your organization maintain focus?

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

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

  • \\xa0

  • 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!

'