"Most enterprise architecture teams do really bad jobs of explaining value of enterprise architecture to the business. " (Anne Lapkin)
She points out that following points are required for enterprise architects to communicate the value of EA.
- To understand your value prepositioning in terms of what you are delivering to your business.
- To set up a formal communications discipline to be able to communicate that value to the business and to your other stakeholders.
- To put in place some concrete measurements so that you can actually demonstrate that you are delivering value to your business.
One of well known reason of IT Project failure is lack of communication between business people and IT people. Enterprise architecuture (EA) solve this problem analyzing an enterprise from the coordinated views of the entire enterprise. Also, EA help to improve project-planning, dicision-maiking, risk-management, and etc. Well, is it too abstract? Say it is true, how much it is worth? Even only IT systems cost too much for many companies; do EA projects deserve additional investment?
It depends. EA gives us comprehensive view of current and future enterprise state from a view point of unique combination of strategy, business, and technology. On the other hand, creating an EA can consumes a lot of time and money. Thus, if the benefits from creating EA will not outweigh the cost, a company should not invest on the project. However, in some circumstances, creating an EA project will provide long term benefit to the company. Let's see some examples.
InfoWorld's Enterprise Architecture Awards is a showcase of successful EA projects.
- The 2011 Enterprise Architecture Awards
- 6 projects are awarded: American Express, Bayer Healthcare, First Data, Singapore Ministry of Education, Procter & Gamble, USAA
- The 2010 Enterprise Architecture Awards
- 5 projects are awarded: Aetna, Barclay's Bank, Discover Financial Services, Skandia UK & International, Wells Fargo
These cases show that EA actually provide values for some projects, and its impact could be huge. Of course, these projects are the most successful cases and the value of EA varies by the project. The important thing is that enterprise architects need to understand the value of EA for each project from the aspect of business (not only in terms of IT), and tell their clients its value. These best practices above would help to identify the value of EA.
No comments:
Post a Comment