For Enterprise Architecture Professionals

Primary Analyst Photo	Document Information	Rate this Document
	July 28, 2010 Best Practices: Starting Or Restarting An EA Effort by Gene Leganza with Jeff Scott, Mimi An	Average: 7  (2 ratings)

This is an excerpt

Executive Summary

Enterprise architecture (EA) continues to gain recognition as a key practice for maximizing the impact of business' use of technology. An effective EA practice can eliminate business-IT alignment problems and help lead an enterprise to advanced levels of collaboration and innovation. And yet many EA programs crash and burn due to the perception that they lack value. Why? Incorrect EA scope, inappropriate EA priorities, lack of visibility of EA deliverables, and lack of organizational maturity are among the most common problems, to name a few. EA value is very real, but leaders of new EA programs must begin their programs with a carefully planned agenda, and leaders of ongoing programs must regularly reassess their environments to ensure traction and success.

TABLE OF CONTENTS

• EA Efforts Must Target Value, Balance, And Organizational Development
• Base EA's Agenda On Goals And Its Approach On Organizational Readiness
• Best Practice No. 1: Focus Intensely On Clearly Defined Goals
• Best Practice No. 2: Base EA Goals On What Matters To The Business — Now
• Best Practice No. 3: Create An EA Practice Effective For Your Needs And Culture
• Best Practice No. 4: Map The App Strategy To Business Goals And Strategy
• Supplemental Material
• Related Research Documents

This is an excerpt