Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Enterprise Architecture Professionals

Primary Analyst Photo Document Information Rate this Document

June 10, 2009

Case Study: EA Aligns IT With Business' Emergent Strategy

by Gene Leganza

with Alex Cullen, Jeff Scott, Matt Czarnecki

Average:
(3 ratings)

This is an excerpt

Executive Summary

Enterprise architecture (EA) programs are becoming more business focused and helping IT to deliver greater value to business. Business-focused EA teams are developing the "next practices" for interacting with the business, collecting and analyzing data, synthesizing across domains, and communicating the resulting architecture. In this case study, an EA team at an investment bank ran into difficulty with its business areas' ability to describe their business strategy. The EA team took a bottom-up approach to characterize the "emergent strategy" and created an "emergent architecture" to support this strategy. The result? Kudos and buy-in from top-level management — but although the process can be successful, it may be difficult for some firms to adopt. EA teams should add this approach to their arsenal.

TABLE OF CONTENTS

  • Situation: The Top-Down Strategy Isn't Clear Enough To Be Useful
  • Solution: Find The Emergent Strategy, And Define The Enabling Architecture
  • What's Next: Successful Experiment But Hurdles In Taking It To Baked-In Process

RECOMMENDATIONS

  • Don't Expect To Be Handed A Coherent Strategy, But Don't Do Without One
  • Supplemental Material
  • Related Research Documents

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word: