Enterprise Architecture

Enterprise Architecture

An Enterprise Architecture (EA) is a blueprint that defines the operations and structure of an organization. The idea behind having an EA in place is to be able to analyze the organizational resources and objectives in a better and organized way.

Forester Definition

“EA is a planning, governance, and innovation function. It is an essential function for improving IT effectiveness and efficiency”

Gartner’s Definition

"EA" is the process of translating business vision and strategy into effective plans for enterprise change’

The largely accepted view of EA comprises of 4  business perspectives. See diagram below.

Business Architecture (Business)

Describes the functional structure of the organization in terms of what the organization does (Business Services) and how it executes its services (Business Processes). The Business Architecture gives you a good idea of how the various business processes are interlinked and inter-weaved in certain instances.

Information Architecture (Information)

Refers to the organization of enterprise data. Describes how information is stored and also gives a good understanding on the flow of information.

IT Applications Architecture (Applications)

Describes the suite of IT applications and tools used by the organization to either gain business competitiveness or to solve business problems. App Architects need to unsure that they design AA to be scalable, reliable, manageable, and available. Also an important consideration would be look at the ease with which applications can be integrated with new applications and external environments.

IT Infrastructure Architecture (Technology)

Infrastructure Architecture refers to the design of the support software and hardware required to keep IT application available for use.  

Why Indian Software Vendors score low on keeping Promises

Do Indian IT Vendors Lie to their Customers?

Well if you think about it. “Lying” would be a rather strong word. 

However, there is a common mistake that most Indian IT Vendors do commit. Most vendors end up over-committing during the customer acquisition phase and fail to deliver on their promises at the time of implementation. In short, these companies “Over-Promise and Under-Deliver”. This leads to dis-satisfied customers and to the loss of future/repeat business. Considering the fact that most Indian IT Companies get more than 90% of their revenues through repeat business (Wipro 98%, TCS 95%, Infosys 97%) these companies should make sure that they promise only what they can actually deliver.

    
So why does this happen and what can IT companies do about it? 

The primary cause of such failures is poor communication between the sales and implementation teams. The Business Development Teams over-commit during sales interactions without adequate consultation with the Implementation Teams. To avoid such issues Sales Executives should ensure they get approvals from implementation experts before making any commitments to prospective customers. It would also be a good idea to groom professionals with a blend of IT Sales and Implementation experience and have them interface between Sales and Implementation Teams to ensure better coordination and flow of information.