Developing the 'as is' and 'to be' Technology roadmaps is core to our delivery and methodology. For Cloud adoption to be successful there is a need to understand the interdependence of the business requirements, the technology stack and the low level components. The journey to the Cloud comprises of the following components:

​

​Understanding Business requirements

• What are the priorities for the IT service?

• What is the business demand for new ways of working and mobility?

• What are the business constraints?

• What is the appetite for change?

Determining direction

• What are the core design principles?

• What are the core policies?

• Where does the IT function want to be?

Capture 'as is' architecture

• Defining the as is components of the IT estate.

• What is serviceable life of the core components? 

Identifying opportunities

• Defining the optimal point of change

• Identifying the risks and issues of each components

Develop the 'to be' architecture

• Develop 'to be' architecture

• Defining the 'to be' technology stack

• Defining the components for change

• Defining the readiness criteria

• Defining the interdependencies

Develop strategic roadmap

• Define the sequence of change

• Define the timeframes

• Defines the components to be decommissioned

• Defined the components to be upgraded or migrated