Developing an IT Strategy: Aligning IT Capabilities with Business Requirements

An IT Strategy is an iterative process to align IT capabilities with the business strategy and requirements. One of the main reasons for developing an Enterprise Architecture with TOGAF 9 is to support the business by providing the fundamental technology and process structure for an IT Strategy. The IT Strategy details the technologies, application and the data foundation needed to deliver the goals of the corporate strategy, while Enterprise Architecture is the bridge between strategy and execution.

Does IT mean Information Technology? Or is it Just a Department?

If we can understand IT (where appropriate) as part of the business of the enterprise, then we are automatically addressing alignment and are neither elevating IT architecture to the ultimate goal of EA nor treating it as a marginally relevant utility. It could be that in the process we discover areas where our methods need to be fleshed out – or simply to incorporate/interoperate with other existing methods for those areas.

SOA is not differentiating, Cloud Computing is

Merely putting SOA into your proposal or as a stated capability is no longer going to be a “deal clincher” or a key “business differentiator”. The counterview I hear practitioners in SOA will say is that SOA is not just the standardized service practices but is also how the services can be identified that are differentiating. But that’s the rub. If SOA treats every requirement or design as a service problem, where is the difference?

1 4 5 6 7