Here are a couple of questions that on EA from an online forum that I responded to
Is Enterprise Architecture still relevant in the Digital Age?
Let us take the overly simplistic description of EA from Wikipedia “Enterprise architecture (EA) is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a holistic approach at all times, for the successful development and execution of strategy.”
This need for “conducting enterprise analysis, design, planning, and implementation, using a holistic approach” continues to be relevant in the digital age.
A strong EA based approach will guide the development of a strategy and roadmap for realization. More importantly, it will guide the execution of a digital strategy[1] too.
You may be interested in my article: What is Digital Strategy Execution? And what it means to IS Executives
How can I be an expert in enterprise architecture?
Let me change the premise of the question before trying to answer it. One doesn’t become an “expert in enterprise architecture” just like one doesn’t become an “expert in medicine” or “expert in law” or “expert in business”
Building on one of these examples, one becomes proficient in law, and gains expertise in a branch, say patent-law or criminal-law. After a lot of hard work and working in the trenches, one gets recognized as a good lawyer and perhaps an expert in patent filings.
Most Enterprise Architects are generalists in many of the BIDAT EA domains, while some may also be recognized as experts in a domain or sub-domain. For instance, An EA might be recognized as an ‘expert’ in Networking and Infrastructure with a strong background in virtualization and cloud hosting, while his peer in the organization may bring in expertise in transforming HR processes. By complementing their skills, they enhance the practice of EA in their enterprise.
If the question was “How do I learn more about Enterprise Architecture?” I can point you to several books, references and online forums on the topic. (ref: “Enterprise Architecture References”)
No comments:
Post a Comment