Evolution of Enterprise Architecture Function

Evolution of Enterprise Architecture Function

The Enterprise Architecture (EA) discipline has evolved over the years. Even definition of EA has evolved over the years, giving us the clue that the role of EA is increasingly recognized as the one which helps organizations holistically respond to the disruption and will lead the change.

If we look at how EA function has matured over the years, most of the organizations starts by documenting their current state IT architecture - this is important because you need to know where do you stand at the moment in order to know how would you reach your target state.

At this level EA function is relatively passive.

You graduate to next level when you take this information and analyse the inefficiencies and gap in your architecture. Be it processes, applications, integration, information ownership or technology landscape. With the ready reference information about your AS IS state. This stage is all about standardization and setting up the governance.

Standardization happens at multiple levels - at architecture, technology & tools. You start with documenting Architecture principles that all your initiatives are going to follow or take into account without any compromise. On technology front, you don't want projects to make decisions in their own silos. You want to offer guidance in the use of technology platforms, so every standard project don't have to reinvent the wheel and over the years you don't run into issues where you have everything under the sun available in your IT stack.

Standardization has to accompany with the control mechanism- there is no point in defining standards and then having no mechanism to ensure that projects are complaint to it.  

If you closely look at first two levels - they are mainly focused around internal to IT. The primary focus is to create foundation on which you want to build upon.

The next level is to bring in synergy/alignment between what business needs are and how IT respond to it. It all starts right at the end of Business strategy definition where business priorities for next few years are articulated. EA team works with the business to decode their vision and start aligning IT strategy according to the new priorities. It is more a proactive step where IT don't need to wait until ideas/initiatives are firmed up at business side and then they are discussed with IT. Instead, EA team work closely with the business to refine their vision and realize it in systems.

The pinnacle of EA function is all about innovation where EA team participate with Business in defining new business models. Where IT acts as an idea factory to provide inputs on how to leverage IT & technology innovation to create new revenue streams, bring in new products, generate insight based on available information. This is the true participation model where we jointly innovate and refine ideas.

The question is at which stage are you operating at the moment? And what are your plans to move up in the value chain and start contributing to top line?

Krishnakumar Srinikethan Gaddam - TOGAF?, PSM, SAFe? 5 Agilist

Senior Enterprise Architect at TSCNET Services GmbH

7 年

Nicely summed up

要查看或添加评论,请登录

Shiv Prakash Ojha的更多文章

  • A 3-Step Guide to Legacy Modernization

    A 3-Step Guide to Legacy Modernization

    In today's rapidly evolving technological landscape, clinging to outdated legacy systems can hinder your business…

    5 条评论
  • Divestiture - Driving Application Decoupling

    Divestiture - Driving Application Decoupling

    Mergers and acquisitions (M&A) are a constant in the dynamic world of business. While much focus has been placed on the…

    2 条评论
  • API Security: 5 lessons from my experiences

    API Security: 5 lessons from my experiences

    API (Application Programming Interface) plays a central role in today’s digitally connected world. A recent Akamai…

    6 条评论
  • How do we address Internal Threat?

    How do we address Internal Threat?

    #SoftwareSecurityMyth - Our application is meant for internal users, they access it from within our company network, it…

    2 条评论
  • Is it possible to Shift Left Security Requirements?

    Is it possible to Shift Left Security Requirements?

    #SoftwareSecurityMyth –Security requirements are Non-Functional requirements and are the responsibility of Architects;…

    1 条评论
  • 10 Lessons from Delivering Technology Transformation Programs

    10 Lessons from Delivering Technology Transformation Programs

    I wrote a blog in 2010 about lessons learnt while working on several back to back technology transformation programs…

    5 条评论
  • Embracing Two-Speed Fulfillment in the Journey to become Digital Service Provider

    Embracing Two-Speed Fulfillment in the Journey to become Digital Service Provider

    As communication service providers (CSPs) are strategically positioning themselves as Digital Service Providers (DSPs)…

  • Business Case for Cloud Adoption

    Business Case for Cloud Adoption

    Recently, we had an honor of hosting Manpreet Singh at our Infosys Jaipur campus. His speech was around Cloud Computing…

    2 条评论
  • Family is new Enterprise

    Family is new Enterprise

    Blurring boundaries between Enterprise & Consumer businesses for Telcos Today, it would be almost impossible to find a…

    1 条评论

社区洞察

其他会员也浏览了