Agility ≠ Speed • Kevlin Henney • YOW! 2019

Discover the truth about agility in software development: it's not about speed, but about navigating uncertainty, building a culture of communication and decentralization, and embracing continuous learning and improvement.

Key takeaways
  • The key to agility is not speed, but rather the ability to navigate uncertainty and change direction when needed.
  • Agility is about building a culture that values communication, decentralization, and diversity of opinion.
  • Decentralization is key to promoting autonomy and reducing risk.
  • The illusion of complete knowledge is a major barrier to agility, and we must be willing to question our assumptions and adapt to new information.
  • Estimation and prioritization can be misleading, and we must consider a more nuanced approach to planning.
  • Iteration and experimentation are essential to continuous learning and improvement.
  • Speed can be a myth, and we must consider the trade-offs between speed and quality in our development processes.
  • Autonomy and self-organization are powerful tools for promoting agility and reducing conflict.
  • The wisdom of the crowds can be harnessed through open communication and diverse perspectives.
  • Agility is not just about technology, but about creating an organizational culture that values learning, adaptation, and collaboration.
  • The PDSA (Plan-Do-Study-Act) cycle is a powerful tool for facilitating continuous improvement and learning.
  • We must be willing to slow down and reflect on our processes and outcomes in order to learn and adapt.
  • The concept of “muda” (waste) is crucial to understanding the importance of reducing inefficiencies and improving flow in development processes.
  • The importance of “jidoka” (autonomous self-stop) in ensuring the quality and reliability of our work.
  • Communication is key to facilitating collaboration, shared understanding, and collective intelligence.