Thursday, March 31, 2011

Thoughts on Enterprise Architecture

In running a successful business that relies on delivery of its IT platform, that business must ensure that its IT is well aligned with its business initiatives. Such organizations must invest in putting together an enterprise architecture (EA) team. Responsibilities of such a team would be to ensure that business requirements are well understood by its technology leaders and this team should be able to negotiate the scope with the business based on technical feasibility and existing solutions.

When adopting new solutions, enterprise architects must evaluate existing technical assets within their organization to avoid redundancy. They must analyze the impact of adopting a solution to the overall enterprise and not just to address an immediate need.

EAs should work with release management and various other architects to plan out the releases that need to occur to ensure proper governance and alignment with the business model. Timely delivery of a solution to business is a critical parameter in considering the adoption of that solution.

When adopting new technological solutions or change in an existing approach, EAs must be cognizant of the total cost of ownership (TCO) of that solution. A roadmap must be developed which addresses current state, anticipated user growth and the expansion in technical platform. This roadmap will be one of many inputs in determining the TCO along with the licensing, maintenance costs and the costs of moving to newer versions of the product.

Enterprise Architects are involved right from understanding business initiatives to ensuring those initiatives are well understood by IT and delivered within the scope and architectural guidelines agreed upon by different stake holders of the project. The diagram on the right shows the role of EA within the organization throughout the different phases of the project.


0 comments:

Post a Comment