Agile 2 Is an Improved Agile The Agile movement took us away from big plans, micromanagement, and projects-by-numbers. It shifted the focus to small teams, to incremental deliveries, and to collaboration and self-sufficiency. But it dismissed the importance of leadership, structure, forethought, and individual differences. It defined one-size-fits-all practices, often favoring some styles of work over others. Despite its technical roots, Agile also quickly devalued the importance of engineering; and it did not even mention the importance of information and data - things that are so critical today. These are not small things. A fresh start was needed -- a reboot. A team of fifteen experts in product design, program management, system engineering, leadership, business, human resources, learning theory, and of course Agile and DevOps came together to consider, What about Agile is important? What needs to be updated? and What is not quite right, but needs to be adjusted? The book Agile 2: The Next Iteration of Agile introduces and makes the case for why this approach is needed, explains Agile 2's big ideas, and shows how those ideas play out in an organization. Perfect for project managers of all sorts, team leaders, department heads, executives, and managers in organizations that have attempted to implement Agile, and the individual members of Agile project teams.