Abstract
A company is subject to frequent changes driven by changing business requirements and objectives. Such changes must be managed properly and require a corresponding organisational unit. Traditional organisational forms follow a top-down approach—i.e. Enterprise Architecture Management is driven by top management. Recent experiences show that a more collaborative Enterprise Architecture Management approach is required.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Mooney provides several examples and small case studies from his professional experience in [1]. He works as a consultant in the change management area.
- 2.
- 3.
The notion of Managed Evolution is further explained in [4].
- 4.
The decision of the duration of each planning period is done by the organisation. It tends to be a full or a half year. The duration needs to incorporate the ability of the company to adjust to new requirements and objectives.
- 5.
- 6.
The term enterprise architect will be used for referring to an individual, a position or even a group of people throughout this book.
- 7.
- 8.
- 9.
For example in Sect. 4.2.
- 10.
The team was managing business requirements for IT developments and providing training for business people. As they had they expertise on business and software applications, the team got also involved in activities typical to EA.
- 11.
I’ve never been in such an environment. There is a book published by Chris Potts, a consultant in EA: [9]. It is nicely written as a story and explaining the idea that the CEO is the real enterprise architect.
- 12.
- 13.
A fool with a tool is still a fool.
- 14.
I remember one of my bosses that hired me, because she wanted to set up EAM in an organisation. Only 7 months after I started my new position as business architect, she had to resign. She was only focusing on collecting data and creating maps, but did not manage to communicate the benefit towards corporate management.
- 15.
For example reusing a single software service for shipping label creation throughout the application landscape.
- 16.
Wierda, G.: Chess and the Art of Enterprise Architecture, [10].
References
P. Mooney, The Transformation Roadmap, Accelerating Organisation Change (Oak Tree Press, Oxford , 2012)
J. Kotter, Leading Change (Harvard Business Review Press, Brighton, 2012)
T.F. Cawsey, G. Deszca, C. Ingols, Organizational Change, An Action-oriented Toolkit, 3rd edn. (SAGE Publications, New York, 2016)
S. Murer, B. Bonati, Managed Evolution, A Strategy for Very Large Information Systems (Springer, Berlin, Heidelberg, 2011)
M. Dumas, M. La Rosa, J. Mendling, H.A. Reijers, Fundamentals of Business Process Management, 2nd edn. (Springer, Berlin, 2018)
G. Blokdyk, Continuous Process Improvement, A Complete Guide, 2019 edition (5STARCooks, 2019)
M. Op’t Land, E. Proper, M. Waage, J. Cloo, C. Steghuis, Enterprise Architecture, Creating Value by Informed Governance. The Enterprise Engineering Series (Springer, Berlin, London, 2009)
N. Banaeianjahromi, K. Smolander, Lack of communication and collabo-ration in enterprise architecture development. Inf. Syst. Front. 57(1), 3 (2017)
C. Potts, recrEAtion, Realizing the Extraordinary Contribution of Your Enterprise Architects (Technics Publications, LLC, Denville, 2010)
G. Wierda, Chess and the Art of Enterprise Architecture, Making the Right Moves to Manage Business-IT Complexity (R & A, Utrecht, 2015)
S. Bente, U. Bombosch, S. Langade, Collaborative Enterprise Architecture, Enriching EA with Lean, Agile, and Enterprise 2.0 Practices (Elsevier/Morgan Kaufmann, Amsterdam, 2012)
S. Kotusev, Enterprise architecture: a reconceptualization is needed. Pacif. Asia J. Assoc. Inf. Syst. 10, 1–36 (2018)
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2021 The Author(s), under exclusive license to Springer Nature Switzerland AG
About this chapter
Cite this chapter
Jung, J., Fraunholz, B. (2021). Managing Enterprise Architecture. In: Masterclass Enterprise Architecture Management. Springer, Cham. https://doi.org/10.1007/978-3-030-78495-9_5
Download citation
DOI: https://doi.org/10.1007/978-3-030-78495-9_5
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-78494-2
Online ISBN: 978-3-030-78495-9
eBook Packages: Computer ScienceComputer Science (R0)