Information Technology Reference
In-Depth Information
adoption of the cloud strategy can be successful. The issues encompass vari-
ous areas including internal competencies and experience of the strategy
development as well as cloud delivery teams, organizational change man-
agement, project management, technical solution management, and data
governance, just to name a few. It is therefore imperative that the cloud busi-
ness case and plan consider a holistic view that cuts across people, systems,
architectures and business processes for successful adoption and optimizing
business benefits.
The method we have described in the following is a generic
approach toward adoption of most systems including cloud and
respective organizational requirements. In practice, it is of
course necessary to modify or extend the plan to suit specific
needs. One of the key tasks before applying the model is to produce an
organizations-specific adoption plan. To do so, you need to review vari-
ous steps and building blocks for relevance and fit and adapt them
appropriately to the circumstances of the enterprise. Depending on the
maturity of the enterprise in terms of their business and enterprise
architectures and alignment of current systems adoption processes
with their business model, the cloud adoption plan may involve the fol-
lowing changes:
• Organizations may opt for either an as-is or to-be as the first
approach depending on their level of understanding of cloud
and business and technology maturity. In as-is, first, an assess-
ment of the current state landscape informs the gaps and
opportunities for cloud adoption, whereas in the latter, a target
solution is elaborated and mapped back to current state; gaps
and change requirements are identified and assessed to inform
the realization plans.
• In case of SMEs, it might be more appropriate to use a cutdown
model adjusted to their typically lower resource levels and sys-
tem complexity. The plan adaptation is a function of practical
assessment of resource and competency availability and the
value that can realistically be delivered.
20.3 Deployment Model Scenarios
In the early days of service-oriented architecture (SOA), there was great
debate in the industry about where to begin with SOA and Web Services—
internally within the four walls of your enterprise or externally with
Search WWH ::




Custom Search