This week, Dan Neumann is joined by two AgileThought colleagues, Justin Thatil, the show's cohost, and Lizmeth Rodriguez. They discuss the topic of how to achieve a seamless Value Flow, one of the SAFe principles, and the general importance of flow in a system. These three expert Agilists also assess the differences between Kanban and SAFe, especially regarding their approach to scaling.

 

Key Takeaways

Principles of SAFe:

Make value flow without interruptions.

Value has to move efficiently from start to finish.

What are the differences between Kanban and SAFe?

SAFe is a detailed plan for working with big companies using Agile methods.

Kanban is a simple way to make work run smoothly and always find ways to do things better.

Kanban is not as strict as SAFe.

SAFe and Kanban approach scaling at Agile differently. SAFe is a framework for large-scale Agile adoption, while Kanban is a more flexible methodology that can be adapted to various contexts and scales.

According to SAFe there are 8 flow accelerators:

1. Visualize and limit WIP.

2. Address bottlenecks.

3. Minimize handoffs and dependencies.

4. Get faster feedback.

5. Work in smaller batches.

6. Reduce queue length.

7. Optimize time “in the zone.”

8. Remediate legacy policies and practices.

 

Mentioned in this Episode:

Learn more about Measuring Flow with Flow Metrics

Actionable Agile Metrics for Predictability: An Introduction, Daniel S. Vacanti

The Heart of Business: Leadership Principles for the Next Era of Capitalism, Hubert Joly

 

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 [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!

 

Twitter Mentions