Tag Application Development

Implementing Agile: Five Warning Signs for CIOs

So much has been written on Agile Development, its methods, practices and benefits to a software development team.  If you are not fielding calls from vendors wishing to present to you on Agile/Lean methods, perhaps you are already implementing Agile within your organization.

As with most IT methodologies, there have been a great many passionate and alternative views expressed, ranging from the appropriate levels of dogma, to the historical influences of other methodologies to the “post Agile movement” and what that might mean to you.

It seems to me that, in addition to all the constructive discussion of the benefits of this particular methodology, there is another, equally important set of issues to consider when an organization begins to move from the books and presentations into the real world of processes managed by humans.

Following are a few warning signs that might be helpful to watch for as you begin planning your move to Agile.  Note that although this post concerns Agile implementations, the warning signs might apply to just about any new process methodology within IT.

Infrastructure vs Development

The majority of IT leaders will at some point find themselves in the midst of a conflict between the needs of their business partners and development teams, and the real-world requirements of managing a large systems infrastructure.  The conflicting goals of these groups may have caused simmering frustration just below the surface for some time, then bubbling up with new pressures on software development timelines (go faster!), budget pressures or even the recognition that there is now real competition for internal enterprise infrastructure in cloud computing vendors.

For presentation sake I am combining the Development and Business views, which may include the following:

Infrastructure View:

  • Standardization lowers organizational costs.
  • Control of infrastructure offerings enables a reduction in differentiation, and will increase availability.
  • Infrastructure managers are graded/incentivized in large part on availability and managing costs, rather than on speed-to-market.
  • When developers are allowed to dictate environmental specs, organizational resources may be wasted.
  • There is theoretical potential for cost savings in the management of a large-scale environment serving many internal customers.
  • It is inherently difficult to itemize cost structures for a specific dev/prod environment within a large, distributed enterprise.