Independent Guidance for Migrating to the Service Oriented Cloud

David Sprott

Subscribe to David Sprott: eMailAlertsEmail Alerts
Get David Sprott: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Cloud Computing, Enterprise Architecture, Philippines, Agile Software Development, SaaS Journal, Infrastructure 2.0 Journal, Enterprise IT: Moving CapEx to OpEx , Mergers & Acquisitions on Ulitzer, Outsourcing on Ulitzer

Blog Feed Post

Transformation to Agile IT Delivery

Because business as usual (BAU) doesn't deliver, we can observe the "initiative count" increasing exponentially

The number one IT issue for all enterprises today is delivery - responding to business demand for change in ever faster timescales, at lower cost. But in the typical large enterprise, IT is widely perceived to be incapable of responding in a reasonable timeframe and cost. There are many, many reasons for this. Existing application portfolios are frequently a complete mess typically resulting from continual compromises made in order to deliver rapid business change, which commonly result in duplication, inconsistency and increased dependencies. Enterprise architecture typically fails to deliver realizable guidance to delivery teams. Delivery projects are commonly driven by narrow focus, exclusively business centric goals. I could go on.

Because business as usual (BAU) doesn't deliver, we can observe the "initiative count" increasing exponentially. Initiatives are top management driven demands for results that are frequently outside of the momentum plan. For example, narrow focused Agile projects; mobile IT and BYOD; SaaS projects; package acquisitions; M&A, BPO, outsourcing and offshoring projects etc.  Or technology focused adventures such as application level modernization. And what usually happens is the initiatives become the new silos, which in turn contribute to the ongoing maintenance and integration nightmare.

Over the past decade most large enterprises have established architecture as a key discipline precisely because of the situation described above. EA in particular was always intended to provide a "city planning" perspective, coordinating across domains to ensure consistent business processes and information and to govern standard infrastructure and shared services where appropriate. In many organizations EA has actually been disestablished because it was perceived as not adding business value. In other organizations EA has minimal influence on delivery programs because of the lack of interest in "doing things right" and the over-riding imperative to deliver as quickly as possible, regardless of downstream consequences.

Recognize the picture? The problem is that for most organizations there is no BAU. So the result is that stand alone initiatives become the only way to get rapid results, but the inevitable outcome is that the ability to change the core business is in steep decline. Short term "project agility" is confused with "ongoing business agility". The way forward is to view the IT Delivery as a Value Chain. You can't focus on just one part of the chain such as Agile projects, you need to see the bigger picture and "manage" the way you respond such that business AND IT goals are achieved.

Read the original blog entry...

More Stories By David Sprott

David Sprott is a consultant, researcher and educator specializing in service oriented architecture, application modernization and cloud computing. Since 1997 David founded and led the well known think tank CBDI Forum providing unique research and guidance around loose coupled architecture, technologies and practices to F5000 companies and governments worldwide. As CEO of Everware-CBDI International a UK based corporation, he directs the global research and international consulting operations of the leading independent advisors on Service Oriented Application Modernization.