Agile software development is designed to thrive within even the most dynamic business and technical environments. In fact, the name “agile” was chosen because its founders viewed “adaptiveness and response to change” as the most essential concept of the methodology. 
All Agile methodologies include integrated practices and processes that manage evolving requirements to efficiently develop a continuous stream of new software capabilities. However, what Agile does not address are changes related to enterprise support of the Agile process or tasks that fall outside the scope of the project work, including:
- how to effectively manage an organization’s internal personnel so that the appropriate stakeholders are available throughout the course of a project
- how to gather and prioritize the most important features desired by the organization throughout the ongoing development cycle
- how to adjust the notion of needing training in a continuous release environment
- how to ensure customer team members are informed by the full breadth of stakeholders required for enterprise acceptance
- how to secure timely approval of new technologies that a team would like to leverage
- how to address stakeholder discomfort with cultural, business, social or other non-technical changes related to software implementation
Each of these challenges is compounded when organizations operate multiple Agile projects simultaneously. Such unaddressed issues can cause IT projects to ultimately fail, even if executed perfectly within the scope of the development teams and meeting all project acceptance tests. The vast majority  of large-scale IT initiative failures are actually caused by factors other than technology.
Enterprise Change Management (ECM) provides a framework that addresses many of these missing factors. This article focuses on how organizations can leverage ECM practices in conjunction with their Agile development teams to foster IT delivery adoption.
Enterprise Change Management (ECM)
Figure 2 - Typical Stakeholder Gut Reactions to Change Initiatives
John P. Kotter, a world-renowned expert on leadership at the Harvard Business School, views the core pattern associated with successful change as “See-Feel-Change”. To move stakeholders from the type of negative thoughts and feelings depicted in the image above, an ECM program must communicate a vision of the change that is compelling enough to not simply overcome negative preconceptions but also motivate positive participation.
Project and executive managers tend to treat those who will be impacted by software initiatives as if they were Vulcans, not humans. Of course, stakeholders are more like Kirk than Spock. Humans don’t coldly and rationally evaluate information and form impressions based solely upon logic. Instead of withholding judgment on an impending change such as a new software initiative, people tend to make gut-level intuitive leaps that are often negative in nature, and resistant to new evidence to the contrary. This assumes, of course, that those impacted are even cognizant of upcoming changes.
In “Switch: How To Change Things When Change is Hard” , Chip and Dan Heath use the metaphor of “ Rider, Elephant and Path” to describe three primary areas that must be addressed in change management.
- The Rider is our inner Spock. A stakeholder cannot support a change until he or she can understand its purpose and the concrete changes that will likely occur. The type of 50 page technical documents and 100 element flowcharts that developers often create under a “waterfall” approach must be translated into clear, high-level infographics for non-technical stakeholders.
- The Elephant represents our subconscious and emotional levels. ECM influences the elephant through communication that creates positive feelings and mitigates negative emotions such as mistrust, anxiety and anger. For instance, messaging may focus on how the change will solve an existing problem that vexes stakeholders.
- The Path addresses