Six Practical, Tactical Tips for the Enterprise Architect

3,060 views

Published on

It takes tactics to realize a strategy. Discover the key steps to enable your enterprise architecture plan.

Published in: Business
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
3,060
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
98
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Six Practical, Tactical Tips for the Enterprise Architect

  1. 1. Six Practical, Tactical Tips for <br />the Enterprise Architect<br />
  2. 2. Enterprise architecture is the business and technology blueprint that details your business entities, the visible properties of those entities, and the relationships between them.<br />Excellent theory.<br />Turning theory into practice requires vision,* but also demands a tactical approach.<br />!<br />*<br />*For more about vision that drives a transformed enterprise architecture practice, see 7 Steps to Transform Your Enterprise Architecture Practice<br />
  3. 3. Did you know? An ever-growing number of enterprise architects are getting down to tactics, as the profession grows.<br />The Association for Open Group Enterprise Architects, for example, counts some 15,000 members in its professional body across 116 different countries. So said Allen Brown, President and CEO of The Open Group, during a panel at The Open Group’s Enterprise Architecture Practitioners Conference last year.<br />!<br />
  4. 4. Six Top Tips for Enterprise Architecture <br />Tip 4: <br />Find Your Best <br />Enterprise Architecture Tools.<br />Tip 5: <br />Avoid the Data Traps.<br />Tip 6: <br />Architect for the <br />Cloud.<br />Tip 1: Create a Common <br />Requirements Vision.<br />Tip 2: Evaluate, evaluate, <br />evaluate.<br />Tip 3:Do a SWOT Analysis.<br />
  5. 5. Tip 1: <br />Create a Common Requirements Vision.<br />A common requirements vision, or CRV, helps define an organization’s purpose, outcomes and business priorities, along with the IT requirements necessary to satisfy the business strategies. <br />A CRV lets enterprise architects capture, document and examine the matrix of relationships among trends, strategies, business processes and IT requirements. <br />
  6. 6. Tip 1: <br />Create a Common Requirements Vision.<br />Take a top-down approach to your CRV. <br />Create a mock-up for, and get approval from, the group of business and IT leaders who help guide IT investment decisions in the company. <br />
  7. 7. Tip 2: Evaluate. Evaluate. And Evaluate.<br />As enterprise architectures are developed, and CRVs are created, enterprise architects will spend a lot of time evaluating current business and IT environments.<br />Be thorough.<br />
  8. 8. Tip 2: Evaluate. Evaluate. And Evaluate.<br />Evaluate your application portfolios as a starting point. <br />Evaluate your software licensing structures. <br />Determine how many licenses you have.<br />Determine which lines of business use them.<br />Determine whether there is duplication.<br />
  9. 9. Tip 2: Evaluate. Evaluate. And Evaluate.<br />At Advanced Micro Devices (AMD), with some 1,500 applications defined in its repository, leadership was focused on understanding the shadow IT pieces of the application portfolio.<br />“We are trying to get to that view, trying to understand the shadow pieces and the cost information associated with them.”<br />!<br />Tannia Dobbins<br />Enterprise Architect with Advanced Micro Devices, “What EAs Encounter During Transformation Initiatives,”<br />PricewaterhouseCoopers Technology Forecast: 2010, Issue 1.<br />
  10. 10. Tip 2: 2. And 2. And 2. Evaluate. Evaluate. And Evaluate.<br />GXS, a B2B services provider, is performing a comprehensive and detailed discovery of technology and evaluating everything as it defines the enterprise architecture scope: <br />“The need for continuous availability of the B2B services GXS provides, the new data center build-out, database replication, shared services, operational metrics and more are included [in the process].”<br />!<br /> John Radko<br />Chief Technology Strategist at GXS, leading the internal enterprise architecture efforts<br />
  11. 11. Tip 3: <br />Do a SWOT Analysis.<br />According to Wikipedia, a SWOT* analysis is a strategic planning method used to evaluate the strengths, weaknesses, opportunities and threats involved in a project or in a business venture. It involves specifying the objective of the business venture or project and identifying the internal and external factors that are favorable and unfavorable to achieve that objective.<br />*stands for Strengths, Weaknesses, Opportunities and Threats.<br />
  12. 12. Tip 3: <br />Do a SWOT Analysis.<br />An analysis of an enterprise architecture initiative might, for example, focus on IT.<br />Strengths: Characteristics of the organization’s IT that give it an advantage over others in the industry.<br />Weaknesses: Characteristics of IT that put the <br />organization at a disadvantage relative to others.<br />Opportunities: Elements that could improve IT.<br />Threats: Elements in the external or internal environment that could cause trouble.<br />
  13. 13. Tip 3: <br />Do a SWOT Analysis.<br />Did you know?<br />The SWOT technique is credited to Albert Humphrey, who led a convention at Stanford University in the 1960s and 1970s using data from Fortune 500 companies.<br />
  14. 14. Tip 3: <br />Do a SWOT Analysis.<br />Forrester Research has suggested that a SWOT analysis will foster tighter and more productive collaboration between enterprise architects and the CIO, enable a clear set of CIO-aligned enterprise architecture goals, and position enterprise architects to become more valued members of the IT organization. <br />Moreover, it will help sharpen the EA initiative.<br />
  15. 15. Tip 3: <br />Do a SWOT Analysis.<br />Specifically, Forrester Research Senior Analyst Jeff Scott, in an article, “How Enterprise Architects Can Gain Influence with the CIO” in PC World, recommends that enterprise architecture teams:<br />“…Architects can perform a SWOT analysis to uncover opportunities for improvement. And once these improvement opportunities are identified, architects can select the high-priority targets by comparing the value of a solution with how it fits into the enterprise architecture’s overall mission and goals. This exercise will help focus the EA [enterprise architect], since not all solutions will be in the enterprise architecture domain and should be passed on to other groups.”<br />
  16. 16. Tip 4: <br />Find Your Best Tools.<br />Did you know? <br />There are plenty of enterprise architecture tools from which to choose. In the most recent enterprise architecture software analysis from Gartner, entitled, “2010 Magic Quadrant for Enterprise Architecture Tools,” 17 vendors were evaluated.<br />
  17. 17. Tip 4: <br />Find Your Best Tools.<br />So, which tool is right for you?Beyond minimum requirements, enterprise architecture tools vendors are ramping up their offerings with more sophisticated capabilities, including future-state analysis, road mapping, presentational aids, dashboard analysis and scenario planning.<br />“We have to consider the yin and the yang. The question is: <br />Do you want something that can be widely used and is simple or more complex yet really powerful?” <br />John RadkoChief Technology Strategist at GXS<br />?<br />
  18. 18. Tip 4: <br />Find Your Best Tools.<br />The minimum requirements of an enterprise architecture tool are:<br /><ul><li>The ability to create or import models and artifacts.
  19. 19. The ability to present repository information to support a variety of stakeholder needs, including displaying it graphically and textually, as well as providing it in executable forms pertinent to the reader.
  20. 20. A robust, yet flexible, repository and metamodels that support often-changing relationships between the objects within and between the various viewpoints or architectures, as well as capturing temporal relationships and changes.
  21. 21. Requisite administrative capabilities to meet diverse needs, such as security, audit/control, collaboration, configuration and versioning, including in multiple environments (for example, development, testing and production).</li></ul>Source: Gartner Research, “2010 Magic Quadrant for Enterprise Architecture Tools,” <br />by Chris Wilson and Julie Short, October 28, 2010<br />
  22. 22. Tip 5: <br />Avoid the Data Traps.<br />Don’t fall victim to the data element bloat, warns Brand Niemann, Senior Enterprise Architect and Data Scientist at the U.S. Environmental Protection Agency.<br />“How many mission-critical data elements are there in your system? Take a close look, and you’ll actually find a tremendous [number] of redundancies,” Niemann says.<br />
  23. 23. Tip 5: <br />Avoid the Data Traps.<br />By introducing an Enterprise Architecture Repository as part of Discover Financial Services’ enterprise architecture effort, the company was able to identify expensive and outdated legacy applications that resulted in application "tuning." This step alone provided $500,000 in processing cost savings, according to InfoWorld’s 2010 Enterprise Architecture awards.<br />
  24. 24. Tip 5: <br />Avoid the Data Traps.<br />GXS Chief Technology Strategist John Radko says businesses need to nurture their rivers of data, and that the data flowing among various business units and even with trading partners should move through the same conceptual channel, or repository, so that it can be viewed, analyzed, secured and governed. The data repository that Radko and his team are defining is critical because it serves as “the lake” that influences and regulates that data, <br />he says.<br />
  25. 25. Tip 5: <br />Avoid the Data Traps.<br />Step by Step - How to Avoid Those Data Traps:<br /><ul><li>Model data from the top down.
  26. 26. Avoid localization of data within business units and lines of business.
  27. 27. Define data with an eye on the broad enterprise.
  28. 28. Take into account security, audit trails, data visibility, access controls.
  29. 29. Don’t forget your business processes when defining data elements. The two are inseparable.
  30. 30. Consider investing in a data repository as part of your enterprise architecture. </li></li></ul><li>Tip 6: <br />Architect for the Cloud.<br />Every enterprise architect should cover emerging states. <br />Translation: Architect your enterprise for cloud computing.<br />By 2012, 20% of companies will own no IT assets at all. (Gartner's “Top Predictions for IT Organizations and Users, 2010 and Beyond: A New Balance”)<br />Worldwide public and private cloud services revenue will exceed $148.8 billion in 2014.<br />(Gartner forecast: “Public Cloud Services, Worldwide and Regions, Industry Sectors, 2009-2014”.<br />Public cloud computing services have topped $16 billion and will reach $55 billion by 2014. <br />(IDC Worldwide and Regional Public IT Cloud Services 2010-2014 forecast)<br />
  31. 31. Tip 6: <br />Architect for the Cloud.<br />The Cloud Is Here.<br />It will fundamentally change your enterprise IT, giving users on-demand access to applications and services, creating new challenges for ensuring reliability and security of your IT infrastructure. It can even enable more nimble creation of new business models and foster greater entrepreneurial spirit within your organization.<br />Are you ready?<br />
  32. 32. Turn Theory into Tactics!<br />To move enterprise architecture from theory to practice …<br />… enterprise architects should start with a focus on:<br /><ul><li>Understanding their current business and technology requirements and goals, and mapping their assets and functions.
  33. 33. Executing a SWOT Analysis will sharpen enterprise architecture’s aim, and more tightly align its efforts with the CIO’s agenda.
  34. 34. Enterprise architects also need to pick the right enterprise architecture tools and be (data) smart. </li></ul>Finally, keep enterprise architecture grounded in the future, and the future is the cloud!<br />!<br />

×