Sentia’s cloud transformation model for successful deployment and improvement projects

Sentia’s cloud transformation model for successful deployment and improvement projects

Emro Thierry

Emro Thierry

Organizations rely on Sentia to guide them through deployment and improvement projects, shaping application landscapes in the cloud. With over 15+ years of experience in migrations and transformations, we’ve secured our learnings in a model to ensure our customers of a structured migration to the cloud. Sentia’s flexible cloud transformation model can be scoped to fit the demands of any project.

Our cloud transformation model consists of the following five phases:

  1. Discover
  2. Define
  3. Design
  4. Develop
  5. Deploy

As all phases start with a ‘D’, we call it the 5D model. Each phase has it’s own set of tools, so you can visualize them as toolboxes.

Sentia fits the model to a project and determines which toolboxes and tools apply. So when customers want to implement Sentia’s design themselves for instance, we only collaborate on the first three phases and talk about a ‘3D model’. Or, in case of an improvement cycle, less research is required as those details are already known.

During the different stages, people from the customer’s organization and Sentia closely collaborate. Think about disciplines or roles like management, project managers, project consultants, project engineers and architects.

In this article we’ll take a look at the different phases and explain in general terms what to expect.

Sentia 5D Model

Discover (current state)

In the journey to the cloud, we first need to understand the customer’s goals and expectations, the current state and maturity of their organization. Therefore, a meeting or ‘get-together’ is planned where the customer and Sentia get to know each other and Sentia’s approach are illustrated.

After the desired outcome is agreed upon by both Sentia and the customer, the next step is to ‘scan’ and map the customer landscape. Each application component is evaluated for migration to the cloud. To have a good understanding of the different technical components, it is important to have people present that have the required technical and functional knowledge.

Define (future state)

In this stage we create a plan to get from the current situation (as-is) to the desired future state (to-be), by identifying where the current challenges or ‘gaps’ are. The outcome is a document called a Gap Analysis report.

Examples of alignment between Sentia and the customer in this phase are mapping of short- and long-term objectives and describing key processes.

The report is written in such a way that it is aligned towards the business-, privacy-, and security requirements of the different workloads.

Finally, the transition approach is discussed and determined with the client. For example, a big-bang migration or a phased migration approach.

Design (plan)

This phase is all about practicality. In this stage the high-level infrastructure designs are delivered and validated with the customer. Other examples are detailed infrastructure designs for the various applications migrating to Azure.

The actions that will be performed are documented. The scope of the planned work is described and formalized in a document which is called the Statement of Work.

We clarify the responsibilities for each application and formaly divide responsibilities between Sentia and the customer.

Develop (build)

During the development phase the deployment of cloud components is prepared.
Sometimes, an application requires modifications to be ‘cloud-ready’. Refactoring or redesigning of applications is done during this phase.

Required knowledge transfers are identified in consultation with the customer. Other collaborations with the customer in this stage consist of developing a test plan for the validation of the requirements plus implementing support processes and tools.

Deploy (deliver)

The final stage is the actual deployment of the cloud components. This is a structured process during which both functional and technical tests are performed to ensure the desired outcome. Knowledge sharing sessions are planned to transfer the necessary know-how of the deployed cloud environments to the customer.

During this phase acceptance tests take place, and implemented workflows are reviewed.

Continuous improvements

As mentioned in the introduction, the 5D approach is an iterative process. It is ordinary to work through multiple cycles, depending on the workloads of the customer. When a cycle is completed the cloud journey is evaluated and a new cycle is started, taking into consideration past experiences and possibe improvements based on the previous cycle(s).

Contact Us

Are you interested in a successful move to the cloud? Contact us to accompany you with our proven 5D model.