Architecture… the foundation of any IT organization. Unfortunately there is no formal training for such an important role and responsibility. The CIO and Architecture team need to be completely in synch and so they can be tightly alignedÂ with the organization’s needs. A weak architecture strategy can lead to inefficient IT operations. Have you ever heard anyone say. “Tell me who your friends are, and I will tell you who you are”. EXPERIENCE is KEY! This is where “who you know” instead of “what you know” can be an important factor.
If I was to interview an architect for my IT organization, here are some of the characteristics I would deem important and necessary.
Strategic, Informed, capable of understanding business requirements, understands IT Trends, lots of contacts in IT, a visionary and lots of experience…. tons of it, in every aspect of IT.
What I stay away from
A resource whoÂ prefersÂ to develop everything in house and show his or her friend how cool the solution is. My ideal architect, does NOT need to know how to develop code or scripts. Closed minded individuals. Last but not least….(this may upset some people) A small network of peers. EXPERIENCE is key. Who can you turn to to for adviceÂ when you are about to embark on a multi million dollar project to improve your IT and your business?
A well orchestrated infrastructure is key to a successful IT organization. IÂ came across a great article which hilights 9 Signs of Bad IT Architecture. If you have one of these in your organization, perhaps you need to rethink your strategy. Here is a summary of the article / slideshow I came across which outline some key aspects of bad IT Architecture.
Here is the full article I found at the Infoworld Website. http://bit.ly/L9Qqnv