This article is the second in a five-part series exploring organizational factors impacting Enterprise Architecture (EA). We will examine the structure of an effective EA practice. Throughout the series, we will examine what EA truly is and, just as importantly, what it should avoid becoming. In this installment, we focus on the structure and organization of an effective EA practice.
Please read our Whitepaper below:
About the Author
Mike Quinlan DBA, MSSM, TOGAF L2, CSSLP
Enterprise Architect
Mike is an Enterprise Architect in Alpha’s Technology Consulting Practice. He has over 30 years of experience, during which he has built his career as a technologist within financial services, spanning securities, banking, credit card, and mortgage servicing industries. Over the years, he has served as Principal Engineer, Director of Architecture, Enterprise Architect, and Chief Architect, leading the design and evolution of complex enterprise platforms.