For Enterprise Architecture Professionals

Primary Analyst Photo	Document Information	Rate this Document
	October 25, 2007 Best Practices: Architecture Review Transparency, Consistency, And Project Governance Alignment Are Key by Larry Fulton with Gene Leganza, David D'Silva	Average: 9  (11 ratings)

This is an excerpt

Executive Summary

Enterprise architecture (EA) professionals must achieve high levels of technical consistency across IT projects with limited resources and often with limited authority. Many EA groups implement some variation of an architecture review as the means to drive architectural assessment and recommendations into individual projects. To uncover architecture review best practices, Forrester spoke with architects and EA managers at 15 organizations with existing architecture review programs. Our research uncovered best practices in four areas — communications, use of authority, review program structure, and review process artifacts. Programs with strong executive support and multistage review processes are the most successful, but we found that application of these best practices can improve the effectiveness of any architecture review program.

TABLE OF CONTENTS

• Why Do Organizations Do Architecture Reviews?
• Architecture Review Best Demonstrated Practices
• Best Practice No. 1: Communicate Regularly With All Stakeholders
• Best Practice No. 2: Use A Mix Of Formal And Informal Authority
• Best Practice No. 3: Tie Your Process To Project Phases
• Best Practice No. 4: Standardize Process Artifacts
• Forrester's Architecture Review Next Practices
• Identifying Your Challenges
• Case Studies
• 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.