Keywords: , , , , , , ,

Mark Meyers

Abstract

In the last three years we have seen a significant focus placed on the practice of enterprise architecture, its importance to the strategic forward momentum of an organization, and the need to master the methodology, mechanics, and traceable metrics attached to the program. With books, magazine articles, and white papers highlighting the need to properly structure and invest appropriately in enterprise architecture, fledgling programs with modest budgets struggle to apply these broad but often considered ‘best practice’ recommendations. Depending on corporate culture and tolerance for organizational change, senior management teams may be the toughest to convince of the value of a newer enterprise architecture program when, from their perspective, the wheels of the organization have turned smoothly for years. Lead architects with limited program budgets will need to be creative and extremely careful in their approach to developing an enterprise architecture program, but there are ways to achieve success as a frugal enterprise architect.

ABOUT THE AUTHOR

Mark Meyers has served as Managing Enterprise Architect, Regional Program Manager, and Senior Management Consulting Advisor for multiple Fortune 500 companies in the financial services, technology, public sector, manufacturing, and utility industries. Mark now drives the enterprise architecture program for a Midwestern energy company.

REFERENCES

Abrashoff D. Michael: It‟s Your Ship: Management Techniques from the Best Damn Ship in the Navy. Business Plus (2002).

Burton B.: Gartner Survey Results: Primary 2011 and 2012 Focus Areas for Enterprise Architecture. Gartner Research (2010).

Carnegie D.: How to Win Friends and Influence People. Simon & Schuster, Reissue Edition (2009).

Carnegie Mellon Software Engineering Institute: Glossary of Terms; Enterprise Architecture http://sei.cmu.edu/architecture/start/glossary/ (2011).

Casarella J.: A Toolkit for Enterprise Architects – Bringing Enterprise Architecture to Realization. DCI Enterprise Architectures Conference (2006).

Cullen A. Leganza G.: Enterprise Architecture Governance Provides Traction. Forrester Research: www.forrester.com/rb/Research/ea_governance_provides_trac tion/q/id/41011/t/2 (2007).

Cullen A.: Comparing Enterprise Archtiecture Frameworks. Forrester Research. Presented at the Enterprise Architectures Conference (2006).

Gartner Enterprise Architecture Framework: Evolution 2005: www.gartner.com (2005).

Hunter R.: Balancing Risk and Innovation. Gartner 2010 Symposium/ITxpo. Gartner Research (2010).

Kaplan R.S., Norton D.P.: Mastering the Management System. Harvard Business Review (2008).

Maister D.: The Trusted Advisor. Free Press (2001).

Meehan P.: Highlights from the CIO Track at Symposium/ITxpo. Gartner Research (2010).

Paras G.: The Essentials of IT Governance. DCI Enterprise Architectures Conference (2006).

Robertson B.: Enterprise Architecture Research Index: Integrating Enterprise Architecture with Business Strategy. Gartner Research (2009).

Rollings M.: Be Business Relevant: Make Enterprise Architecture Disappear. The Burton Group (2010).

Ross J., Weill P., Robertson D.C.: Enterprise Architecture as Strategy. Harvard Business School Press (2006).

Scott J.: What‟s in a Name? Forrester Research, Enterprise Architecture Professional‟s Blog: http://blogs.forrester.com/jeff_scott (2010).

Scott V., Vescovi M.: Enterprise Architecture – Architecture Governance. DCI Enterprise Architectures Conference (2006).

Sessions R.: Simple Architectures for Complex Enterprises. Microsoft Press (2008).

Short J., Burke B.: Determining the Right Size for your Enterprise Architecture Team. Gartner Research (2010).

TOGAF® Version 9: www.opengroup.org/togaf (2009). The Zachman Institute for Framework Architecture (ZIFA)™: www.zachmaninternational.com (2008).

Van den Berg M., Van Steenbergen M.: Building an Enterprise Architecture Practice :Tools, Tips, Best Practices, Ready-to- Use Insights. Springer (2010).

Zink, G.: How to Restart an Enterprise Architecture Program after Initial Failure. Journal of Enterprise Architecture. Volume 5, Number 2 (2009).

Journal of Enterprise Architecture

Leave a Comment