As Agile eats the world, most medium and large organizations are faced with the necessity of an Agile transformation. Surveys show that more than 90% of executives give high priority to becoming agile, yet less than 10% see their own firm as “highly agile.” Implementing Agile is a means, not the end. The goal is to enable the organization to generate instant, frictionless, intimate, incremental, risk-free value at scale, and the financial rewards that flow from that capability, as exemplified by the five largest and fastest-growing firms on the planet. For most, this is a major challenge—one that will involve deep change over many years. If the organization has been traditionally managed, the journey will include radical shifts in attitudes, values, mindsets, ways of thinking and ways of interacting with the world—in effect a change in organizational culture.
Some organizations’ Agile journeys have been spectacularly successful, whereas others have failed and many have stalled. What are the causes of success or failure or stalling? What are the common features of these different journeys? What patterns are emerging? How can failure or stalling be anticipated and prevented?
For those in the midst of an organization’s Agile journey, how do participants communicate simply and clearly where the organization is on its journey? What steps have been accomplished? What steps remain? How can an organization anticipate and avoid failure or stalling?
Many executives who would like to undertake an Agile transformation journey don’t know where to begin or what the journey will look like. Where does one start? What does the journey look like? How long does it take?
The session will show an approach to graphically mapping the Agile journey and provide answers to these questions, at both the organizational and individual level and the relation between the two. The examples of Microsoft and GE will be highlighted.
In the course of the session, participants will graphically represent both their own organization’s Agile journey and their own individual Agile journey and evaluate the relationship between the two.