Information Technology Reference
In-Depth Information
services; hence, verifying service integration and interoperability is an
important task.
The realization plan will be articulated as an overall cloud adoption strat-
egy. The merits of different strategic approaches characterized by pace and
scope of change/adoption need to be balanced against business constraints
such as funding and resource concerns, technology maturity, existing busi-
ness capabilities, and opportunity costs. The organization may opt for
phased and incremental introduction of cloud or a big bang approach. Cloud
computing requires a different strategy to the upgrade of existing IT infra-
structure. Formulation of an appropriate strategic approach for this will rely
on careful analysis of risks and change requirements.
20.4.3.1 Fit-Gap Analysis
The fit-gap analysis involves linking the as-is and to-be models for busi-
ness, information system, and IT architectures and compares, contrasts, and
rationalizes the trade-offs and interdependencies of the activities to validate
the cloud requirement specification (within broader IS/IT portfolio) for orga-
nization, business, and technical perspectives. Logically grouping and orga-
nizing activities into program and project work packages will feed into the
realization and adoption plans and requirements.
Fit-gap analysis is widely used in many problem-solving-based methods
and is concerned with validating the issues, solutions, plans, etc. The pri-
mary goal at this stage is to highlight any overlaps or shortfalls between
the as-is and to-be states. It concentrates on the evaluation of gaps, includ-
ing further fine-tuning of priorities to consolidate, integrate, and analyze the
information to determine the best way to contribute to cloud implementation
and transition plans.
There are different categories of gaps to consider relating to busi-
ness, systems, technologies, and data. Various techniques could be used
in this exercise such as creating a simple gap matrix that lists as-is and
to-be components in columns and rows with respective gaps in the inter-
section. Similarly, to consolidate gaps and assess potential solutions and
dependencies, a gaps-solution dependency table will be an easy technique
to use. This can serve as a planning tool toward creating project work
packages and initiatives.
20.4.3.2 Change Management
Adopting cloud computing will inevitably require change that cuts across
the enterprise both in terms of understanding the cloud and its value
proposition, and opportunities and different ways it affects the busi-
ness from new ways to engage with the old and new business applica-
tions, possible changes to the current processes, new data related policies,
the new operating model that uses “services” as the key organizational
Search WWH ::




Custom Search