We all love Agile, but how long can it stay relevant when agile coaches say, “All agile transformations fail,” and other coaches nod with a wistful smile? What are IT organizations supposed to do when they need to modernize and “go agile” but they’ve heard horror stories of chaotic, unsuccessful transformations from their peers? No one wants to go back to waterfall, but what in the world WILL we do? For eight months in 2020, a collection of 15 agilists debated and discussed every agile-related topic you can imagine, and over time created a set of new values and principles aligned with the original Agile Manifesto, but evolving it in several important ways. Documented on [Agile2.net](https://agile2.net/), and explained more fully in our book, **Agile 2: The Next Iteration of Agile**, the insights that emerged were complex, sophisticated, nuanced, and based on raw direct experience in organizations. Slowly, with great deliberation, we finessed them into clear statements of what we believe to be needed to ensure the continued relevance and applicability of agile concepts, frameworks, methods, practices, beliefs, and approaches. Agile 2 does not replace the Manifesto; it is an evolution of it. It embraces ideas about leadership, many of which have been articulated by DevOps authors such as Jez Humble and taught by DevOps organizations such as DASA. Agile 2 also emphasizes product design as a major component of product development, and expands on the idea that one cannot operate in a business or tech silo - that one must have a working understanding of the entire capability development and value delivery ecosystem. In this session, you will learn what Agile 2 is all about directly from two of its co-authors. Why is it needed? How did we come up with our new values and principles? What are they anyway? Why are they important? Come and bring your own questions!