More on principles ...
Earlier I wrote about data management principles and data architecture principles, and I stayed with these principles in the comfortable realm of IM&T - i.e. the area where we have more or less control over what we do. The thing I learned recently is that there are also 'higher' level principles that may be of value to drive the 'lower' level principles on data & architecture that I mentioned earlier.Let me call these higher level principles the Business Principles. These are things based on where our business context drives us and what we want as a company. They are basically the things that link the data architecture to the business.
Usually we get a bit vague when we talk business drivers and objectives. But when doing architecture, they are vital for defining direction. For example - say your business is about differentiating technically. In that case your IT architecture should support this and a complete focus on e.g. operational efficiency and cost is probably the wrong focus. Or say your business is about reacting fast to market changes - in that case you cannot afford projects running for 4 years to deliver large solutions, but you should in fast in a platform that allows for agility and change.
Defining these business principles is a key step towards defining a good architecture, and therefore a necessary step, which is quite often forgotten (especially by IT managers with a focus on costs)
Labels: architecture, principles
posted by Evert Ruijs @ 1:02 PM
0 Comments:
Post a Comment
<< Home