Sunday, November 4, 2012

Architecture Implementation

Implementing an architecture is often a very challenging process in companies. Architects know what is the right thing to do, but how to get it implemented is the challenge. The difficulty is convincing business to buy into an idea that will deliver value in the future. Building a business case that shows direct benefits is difficult enough, and convincing finance on risk alone without a user screaming for it is all but impossible.

Architects has to get their hand dirty in order to implement an architecture. The only way is to do projects, lots of projects. The point is to identify the right project, with a strong enough business case and sponsor support, to implement the architecture the business needs.

No business, unless they have very strategically focused CEO, is going to implement a business intelligence system that cost millions to do reporting, just because you say so. It requires a big enough project, with significant user requirements, and a strong business case.

In order to implement the architecture, architects first have to design, and agree, on what is the priority for implementation. The priority is based on several factors: strategic alignment, business impact, cost and architecture dependencies.

In short: design the architecture, prioritise the implementation and select the most appropriate project/s for implementation.

1 comment:

Anonymous said...

Thank you for sharing. Enterprise architecture is crucial for any business.