Using Enterprise Architecture to Dliver the Right Solution
This is the another post in my “Today I read …” series where I aim to summarise. or recapitulate, excellent, and educational, articles that I have read.
[Previous: BA Practices in a Virtual World]
Today I read an excellent article on the IIBA site: “How to Use Enterprise Architecture to Deliver the Right Solution“, authored by Sergio Luis Conte.
The reason that I really found value in this article, was that it helped me get a better understanding of Enterprise Architecture, especially from a Business Analysts point-of-view.
Sergio pulls relevant information from the EABOK (Enterprise Architecture Body of Knowledge), the BABOK (Business Analysis Body of Knowledge), along with other relevant sources, to detail:
- What Enterprise Architecture is,
- Why it should be used,
- When it should be used, and
- How it should be used.
Sergio provides a quote from Gartner to answer this one:
a discipline for pro-actively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer decision making toward the evolution of the future state architecture. (Gartner Group 2013)
He goes further by describing how Enterprise Architecture consists of several independent, but cohesive architectures: Business Architecture (BA), Application Architecture (AA), Technology Architecture (TA), Security Architecture (SA), and Information Architecture (IA).
Sergio explains that Enterprise Architecture is a way of thinking about the Business from a system management theory perspective. He also ties this nicely in with information presented in the BABOK (under competencies).
Enterprise Architecture is used when a business needs to transform itself – when a desired future state is recognised.To identify the gap between the current state, and this future state, a gap analysis is performed, and appropriate steps are taken to make the necessary transformations,
This is a repeating cycle. Businesses attempt to adapt to an ever changing environment.
For the “How”,Sergio mentions that there are several models available for working with Enterprise Architecture. The one he concentrates on, though, is “The McKinsey 7S model” that focuses on, and analyses, seven elements – strategy, structure, systems, staff, skills, and shared values.
Sergio explains each of these seven elements in further detail, including listing references for further reading.
All-in-all, a great article that helped me a lot and gave me enough information for further reading.
The full article can be read on the IIBA site (https://www.iiba.org/News-Events/Best-Practices-for-Better-Business-Analysis/BP4BBA/2013/enterprise-architecture-to-deliver-right-solution.aspx) (Note – IIBA membership required.)
If you like this post, feel free to share. If you have comments that you’d like to make, please go ahead and use the comment box below.
Thanks for reading.
Want to learn more?
Below is a selection of resources that I personally feel are relevant to this blog post, and will allow you to get more in-depth knowledge. I do earn a commission if you purchase any of these, and for that I am grateful. Thank you. (Important Disclosure)
Read More …