This week, Justin Thatil is joined by two of his Agile colleagues, Mike Guiler and Mariano Oliveti, to discuss the tiredness and frustration that can sometimes be caused by following the Agile process. Some organizations can even be convinced that Agile did not work for them; how can this wound be healed?

Key Takeaways

• Some organizations are sure that Agile didn’t work for them.

  • Sometimes, these organizations tried some Agile ways but never started from the beginning.

  • Was “moving faster” all the organization wanted? If you don’t adapt the values and behaviors, Agile will not be guaranteed to speed up the process. First, the organization needs to change its culture.

  • These organizations might need to consider that Agile is a process, a hard process.

  • Today’s transformations are different from what they were ten years ago.

• Benefits of Agile:

  • Many organizations need help with accountability, while Agile proposes an excellent method to ensure it.

  • Agile is a way of approaching organizations to figure out what they can do for them based on their current needs.

  • Agile is the approach that assists an organization in transforming its culture into a long-lasting, durable one with self-managing teams that achieve the desired outcomes.

• Doing Agile vs. Being Agile:

  • Doing Agile is about going through the motions and checking the boxes, but, for being Agile, it is critical to change the culture.

  • There has to be a need for change in the Organization, otherwise, Agile would not work.

Mentioned in this Episode:

The Five Dysfunctions of a Team: A Leadership Fable, by Patrick Lencioni

Overcoming the Five Dysfunctions of a Team: A Field Guide for Leaders, Managers, and Facilitators, by Patrick Lencioni

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!